Re: JDBC 3.0 support?
От | Dave Cramer |
---|---|
Тема | Re: JDBC 3.0 support? |
Дата | |
Msg-id | 1052300635.14269.142.camel@inspiron.cramers обсуждение исходный текст |
Ответ на | Re: JDBC 3.0 support? (Hanasaki JiJi <hanasaki@hanaden.com>) |
Список | pgsql-jdbc |
INSERT .... RETURNING will work here, but in the meantime select nextval('sequence_name'); insert into (id,....) values ( result from above, ....) continue working Dave On Tue, 2003-05-06 at 23:13, Hanasaki JiJi wrote: > Any suggestions for architecture/implemenation in the following situation:? > - insert a new row > - primary key is an autoinc / sequence column > - no other column is sure to be unique > - need to continue working with the data of the row > after the insert and possibly do an update > > Barry Lind wrote: > > Hanasaki, > > > > The driver is already 3.0 compliant for that. It correctly returns > > false to DatabaseMetaData.supportsGetGeneratedKeys() indicating that > > postgresql does not support this functionality. This isn't likely to > > change unless some significant new functionality is introduced in the > > server to do this. There isn't really anything the driver can do here > > since the functionality doesn't exist in the database to automatically > > return this information. > > > > thanks, > > --Barry > > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster -- Dave Cramer <Dave@micro-automation.net>
В списке pgsql-jdbc по дате отправления: