X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2A9EBD1B198 for ; Wed, 30 Jun 2004 05:08:31 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 03804-10 for ; Wed, 30 Jun 2004 08:08:29 +0000 (GMT) Received: from mailer.ipsoluciones.com (unknown [213.0.106.89]) by svr1.postgresql.org (Postfix) with ESMTP id 9FF87D1B184 for ; Wed, 30 Jun 2004 05:08:26 -0300 (ADT) Received: from [192.168.2.140] ([192.168.2.140]) by mailer.ipsoluciones.com (8.12.10/8.12.10) with ESMTP id i5U86Xkv029492; Wed, 30 Jun 2004 10:06:34 +0200 Subject: Re: Unrecognized node type From: Alvaro Sanchez-Mariscal To: Tom Lane Cc: pgsql-sql@postgresql.org In-Reply-To: <1624.1088525897@sss.pgh.pa.us> References: <1087916170.2821.23.camel@mariscal> <1624.1088525897@sss.pgh.pa.us> Content-Type: text/plain; charset=iso-8859-15 Organization: javaHispano Message-Id: <1088582895.31782.58.camel@mariscal> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 30 Jun 2004 10:08:15 +0200 Content-Transfer-Encoding: 8bit X-IPSoluciones-MailScanner-Information: Please contact the ISP for more information X-IPSoluciones-MailScanner: Found to be clean X-IPSoluciones-MailScanner-SpamCheck: no es spam, SpamAssassin (puntuación=-4.9, requerido 5, BAYES_00 -4.90) X-Virus-Scanned: by amavisd-new at hub.org X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char F3 hex) in message header 'X-IPSoluciones-MailScanner-SpamCheck' X-IPSoluciones-MailScanner-SpamCheck: ...am, \n\tSpamAssassin (puntuaci\363n=-4.9, requeri... ^ X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200407/11 X-Sequence-Number: 18263 > I suppose there's some other factor involved in the problem that > you didn't show us. But... what? :-S > As far as finding the bug, you need to provide a complete, > self-contained test case. Can you be more explicit? > As far as loading the schema, how about just removing the DEFAULT > clauses? "default null" is the default behavior anyway. I tried this, but then EJB's doesn't work... Thanks. -- Álvaro Sánchez-Mariscal Arnaiz | Departamento de Comunicación mariscal@javahispano.org | javaHispano javaHispano. Una Comunidad al Servicio de Todos www.javaHispano.org