Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)? - Mailing list pgsql-jdbc

From aaabdallah@gmail.com
Subject Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Date
Msg-id 1172823764.106772.94010@v33g2000cwv.googlegroups.com
Whole thread Raw
In response to Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?  ("Heiko W.Rupp" <heiko.rupp@redhat.com>)
List pgsql-jdbc
Wait, Heiko, I hope you get this message before you spend your time on
this!

First of all, I confirmed what Dave said: the Oracle Toplink package
was indeed sending every single NULL with an SQL type of VARCHAR. I
downloaded the postgresql JDBC source code and slowly traced what was
going on, and put in the necessary printlns to see what was being
sent. Garbage in, garbage out.

The good news: the latest version of the Toplink package solves it: it
correctly switches the type of the NULL based on the real type of the
field.

I thank you very much for attempting to help me, and I hope your
problem also gets solved similarly thru an upgrade. It is frustrating
building off of buggy software, but on the other hand, these are
enormously useful packages that people are putting out for free, so I
can't complain. Just gotta try and get some uninterrupted sleep now...

-A


pgsql-jdbc by date:

Previous
From: "Heiko W.Rupp"
Date:
Subject: Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)?
Next
From: Alex Malone
Date:
Subject: TimestampUtils.toString() speedup