Synthesize support for Statement.getGeneratedKeys()?
От | Ken Johanson |
---|---|
Тема | Synthesize support for Statement.getGeneratedKeys()? |
Дата | |
Msg-id | 4580E681.3080106@kensystem.com обсуждение исходный текст |
Ответы |
Re: Synthesize support for Statement.getGeneratedKeys()?
Re: Synthesize support for Statement.getGeneratedKeys()? Re: Synthesize support for Statement.getGeneratedKeys()? Re: Synthesize support for Statement.getGeneratedKeys()? |
Список | pgsql-jdbc |
Hello, I've just come to realize that Statement.getGeneratedKeys() is not supported in the current PG and/or JDBC driver. Does someone know if this is a limitation of PG, or its protocol, or just not yet implemented in the JDBC driver? I'm just wondering where, if at all (if I have enough brain cells that is :), I could try to offer a patch or ideas.. Then question 2; I did see a discussion where it was suggested that we could get roughly the same effect by issuing a SELECT currval('<sequence-name>'); after the DML... http://archives.postgresql.org/pgsql-jdbc/2005-10/msg00035.php Would it then be feasible internal to the JDBC driver to (create an option that would enable) always implicitly append that query to the (String)sql arg of Statment.executeUpdate(String sql, String[] columnNames)? I mean, just internally attempt to create the same behavior as what this method should be doing? Question 3 is, it seems like option two would only return the last created key, not set of keys, in the case where multiple rows were inserted.. is this accurate? Unfortunately if I cant find a way to make my target-app work with PG (without adding PG-specific modifications for getting keys), I'm probably not going to be able to make the switch to PG unfortunately - the code I'm working with makes really, really extensive use of retrieved keys.. Thank you, Ken
В списке pgsql-jdbc по дате отправления: