To: Alvaro Sanchez-Mariscal <mariscal@javahispano.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Unrecognized node type 
In-reply-to: <1088582895.31782.58.camel@mariscal> 
References: <1087916170.2821.23.camel@mariscal>
 <1624.1088525897@sss.pgh.pa.us>
	<1088582895.31782.58.camel@mariscal>
Comments: In-reply-to Alvaro Sanchez-Mariscal <mariscal@javahispano.org>
	message dated "Wed, 30 Jun 2004 10:08:15 +0200"
Date: Wed, 30 Jun 2004 09:55:42 -0400
Message-ID: <8188.1088603742@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Alvaro Sanchez-Mariscal <mariscal@javahispano.org> writes:
>> I suppose there's some other factor involved in the problem that
>> you didn't show us.

> But... what? :-S

If I knew, I could've reproduced the problem ...

>> As far as finding the bug, you need to provide a complete,
>> self-contained test case.

> Can you be more explicit?

Preferably, send an SQL script that will trigger the failure starting
from an empty database.  You can probably make one by stripping down
your existing dump script.  (I don't care whether you try to minimize
the size of the example; but you'll want to take out your actual data
as well as anything else you deem private.)

>> 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...

This is odd.  I suspect that it would be appropriate to ask the JDBC
people to see if they can fix it.  The driver itself ought to be aware
that "no default" is the same as "default null", but apparently it is
not.  (For that matter, whatever part of the EJB code is breaking ought
to know that, because for sure it is SQL-standard behavior.  But the
JDBC people might be more responsive to a bug report.)

			regards, tom lane