From: | "Michael Paesold" <mpaesold(at)gmx(dot)at> |
---|---|
To: | "Dave Cramer" <Dave(at)micro-automation(dot)net> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Implementing JDBC3 methods (Was: JDBC and fetching the OID of an insert) |
Date: | 2002-09-18 14:58:13 |
Message-ID: | 024b01c25f23$d13a7b00$4201a8c0@beeblebrox |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Dave,
So do you think it would be a very bad idea to implement the new methods in
JDBC3 in a way that depends on OID's? Is there any other way to get the
information about the just inserted generated keys from the backend?
Michael
Dave Cramer wrote:
> Michael,
>
> Well, the method in the driver will work for you.
>
> dave
> On Wed, 2002-09-18 at 10:21, Michael Paesold wrote:
> > Dave Cramer wrote:
> >
> > > There is or was actually a method in the driver ResultSet.getLastOID
> > > which allowed you to do this.You will have to cast the resultset into
a
> > > AbstractJdbc(x)ResultSet, where x is the version; but Daryl's way is
> > > much better since oid's can wrap, and there is a possiblity that they
> > > don't exist ( you can turn them off in postgres).
> > >
> > > Dave
> >
> > I don't really care that oid's can wrap. I don't need them as sequences.
> > Instead I was just looking for the easiest way to get a reference to the
row
> > I just inserted.
> >
> > So my considerations about getGeneratedKeys() would only work if oid's
are
> > not turned off -- very bad for a driver...
> >
> > Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-09-18 16:30:08 | Re: NOTICE causing SQLException |
Previous Message | Kevin Schmidt | 2002-09-18 14:51:48 | setBoolean with BIT column |