From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Inserting "null" not working (Sun App Server, Postgres, EJB3)? |
Date: | 2007-03-08 17:39:29 |
Message-ID: | 23136D2B-ED79-494C-93CB-72F1E746DEB2@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
This is in the code now.
Dave
On 8-Mar-07, at 11:06 AM, Heiko W.Rupp wrote:
>
> Am 02.03.2007 um 02:41 schrieb Dave Cramer:
>
>> Ok, looking at the code in the driver we should be doing the right
>> thing.
>>
>> setObject(n,null) will set the Oid to UNSPECIFIED
>>
>> Any chance we can get a test case to see how this fails ?
>
> Will this be in the PostgreSQL 8.2.4 release?
>
> Again: I could test it with our code, but it's not so easy for me
> to submit a testcase right now.
>
> Heiko
>
> --
> Heiko W.Rupp
> heiko(dot)rupp(at)redhat(dot)com, http://www.dpunkt.de/buch/3-89864-429-4.html
>
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gary Greenberg | 2007-03-09 03:49:52 | Error while retrieving generated keys |
Previous Message | Giuseppe Sacco | 2007-03-08 17:04:24 | [OT] Re: Transaction atomicity |