Re: Patch for Statement.getGeneratedKeys()
От | Kris Jurka |
---|---|
Тема | Re: Patch for Statement.getGeneratedKeys() |
Дата | |
Msg-id | Pine.BSO.4.64.0801110022310.3943@leary.csoft.net обсуждение исходный текст |
Ответ на | Re: Patch for Statement.getGeneratedKeys() (Ken Johanson <pg-user@kensystem.com>) |
Ответы |
Re: Patch for Statement.getGeneratedKeys()
|
Список | pgsql-jdbc |
On Wed, 9 Jan 2008, Ken Johanson wrote: >> the requirement that a query uses a completely qualified name >> database.schema.table is quite onerous. >> > > What are your thoughts on this? Should it be possible/safe going forward to > not supply the fully qualified table in the case of: > > Statement.executeUpdate(String sql, int columnIndexes[]) > > If you can recommend a simpler strategy I will try it. If we can avoid the > round trip also that would be great. > Writing "RETURNING *" will return more data than you need, but it has the plus of not requiring you to know anything about the underlying table columns. Once the full result is returned you would need to strip out only the parts specified in columnIndexes and either create a new ResultSet or a wrapper around the returned ResultSet. Kris Jurka
В списке pgsql-jdbc по дате отправления: