| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Jean-Pierre Pelletier <pelletier_32(at)sympatico(dot)ca> |
| Cc: | Kris Jurka <books(at)ejurka(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: setObject on PGInterval throws "Unknown Type null" |
| Date: | 2005-01-26 21:19:46 |
| Message-ID: | 41F80972.2010308@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Jean-Pierre Pelletier wrote:
> The advantage of overloaded versions of setObject over new method names
> was to
> provide backward compatibility for setObject(i,x)
> i.e. no need to recode setObject(i,x) to setObject(i,x,Types.someType)
> because setObject(i,x) is now broken with null objects.
How is this backwards-compatible? Without recompilation, adding extra
methods doesn't do anything. With recompilation, you need to add a cast
to PGStatement to see the new methods. If you're changing the code
anyway, why not just change to the typed setObject() variant?
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2005-01-27 11:30:29 | Re: Documentation for jdbc escapes |
| Previous Message | Jean-Pierre Pelletier | 2005-01-26 21:03:08 | Re: setObject on PGInterval throws "Unknown Type null" |