From: | Hanasaki JiJi <hanasaki(at)hanaden(dot)com> |
---|---|
To: | |
Cc: | PostgreSQL JDBC - LIST <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC 3.0 support? |
Date: | 2003-05-07 03:13:41 |
Message-ID: | 3EB879E5.5000207@hanaden.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-05-07 04:27:12 | Re: JDBC 3.0 support? |
Previous Message | Barry Lind | 2003-05-07 03:04:09 | Re: Memroy leak with jdbc |