| From: | "Chris Gamache" <cgamache(at)gmail(dot)com> |
|---|---|
| To: | "Kris Jurka" <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: stringtype=unspecified problem |
| Date: | 2007-02-15 14:12:53 |
| Message-ID: | 9cc55f600702150612p72490c3by95f5998541cf9932@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 2/14/07, Kris Jurka <books(at)ejurka(dot)com> wrote:
> Here you're explicitly saying that it is a VARCHAR, not that you have a
> String that you're not sure what the real type is. It would be possible
> to adjust setNull to check the stringtype setting and use Oid.UNSPECIFIED
> here, but I'm not sure that would be correct.
We've been batting this around in the office as well. I wish I knew
what the absolute correct behavior would be in this situation.
An observation that might be insightful is if I can figure out how
setString(1,null);
differs from
setNull(1,java.sql.Types.VARCHAR);
...
When connected using stringtype=unspecified it would seem to me that
the two should behave the same way. What do you think?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2007-02-15 16:40:01 | Re: stringtype=unspecified problem |
| Previous Message | Albe Laurenz | 2007-02-15 11:16:14 | Re: Synthesize support for Statement.getGeneratedKeys()? |