| From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
|---|---|
| To: | "Oliver Jowett" <oliver(at)opencloud(dot)com>, "Kris Jurka" <books(at)ejurka(dot)com> |
| Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: tightening up on use of oid 0 |
| Date: | 2004-10-13 10:53:41 |
| Message-ID: | 001901c4b112$e9c38890$7201a8c0@mst1x5r347kymb |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi,
For my part, I've never used any of those calls.
FWIW, I always use reference objects such as "Integer" as opposed to "int"
so I've never done it that way. All calls to setObject or set<Anything>
would always use a variable which is typed (and may be null) my assumption
is that I avoid all such ambiguities that way.
regards
iain
> Kris Jurka wrote:
> General question for the list: how much code is out there that performs
> one of these (equivalent) calls?
>
> PreparedStatement.setObject(i, null);
> PreparedStatement.setObject(i, null, Types.OTHER);
> PreparedStatement.setNull(i, Types.OTHER);
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tornroth, Phill | 2004-10-13 15:04:29 | FW: Question about the postgres resultset implementation |
| Previous Message | Oliver Jowett | 2004-10-13 09:28:55 | Re: tightening up on use of oid 0 |