From: | Hunter Hillegas <lists(at)lastonepicked(dot)com> |
---|---|
To: | Postgre JDBC <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | FW: [JBoss-user] Postgres woes: solution |
Date: | 2001-05-11 15:20:16 |
Message-ID: | B721513F.163D3%lists@lastonepicked.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Is this a bug or is this per the spec?
This was from the JBoss list.
------ Forwarded Message
From: "Jim Downing" <jimdowning(at)pobox(dot)com>
Reply-To: jboss-user(at)lists(dot)sourceforge(dot)net
Date: Fri, 11 May 2001 10:47:25 +0100
To: <jboss-user(at)lists(dot)sourceforge(dot)net>
Subject: Re: [JBoss-user] Postgres woes: solution
I found the solution to my problem. It raises a minor database portability
issue.
The root of the problem turned out to be a NullPointerException that the
PGSQL driver threw in ejbStore. It turns out that although Oracle is OK
with:
PreparedStatement.setObject(x, null, Types.TYPE);
PostgreSQL isn't. PreparedStatement.setNull(x, Types.TYPE); seems to work
in both.
Hope this is useful to someone,
jim
------ End of Forwarded Message
From | Date | Subject | |
---|---|---|---|
Next Message | Olivier Denier | 2001-05-11 16:16:27 | moveToInsertRow() : Method Not Implemented |
Previous Message | Olivier Denier | 2001-05-11 13:35:59 | moveToInsertRow() : Method Not Implemented |