Implementing JDBC3 methods (Was: JDBC and fetching the OID of an insert)
От | Michael Paesold |
---|---|
Тема | Implementing JDBC3 methods (Was: JDBC and fetching the OID of an insert) |
Дата | |
Msg-id | 024b01c25f23$d13a7b00$4201a8c0@beeblebrox обсуждение исходный текст |
Ответ на | JDBC API Tests (Al Sutton <al@alsutton.com>) |
Ответы |
Re: Implementing JDBC3 methods (Was: JDBC and fetching the
|
Список | 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
В списке pgsql-jdbc по дате отправления: