On Wed, Jul 20, 2011 at 7:18 AM, Shantanu Kumar
wrote:
> JDBC Batch-insert is not supposed to return a list of generated keys.
There may be multiple autogenerated keys in a single row - not common,
I suspect, but possible. So normally with c.j.j, you'll get back a
sequence with a single generated
On Jul 20, 4:15 pm, Mark Nutter wrote:
> > * Add support for databases that cannot return generated keys (e.g., HSQLDB)
> > - insert operations silently return the insert counts instead of
> > generated keys
> > - it is the user's responsibility to handle this if you're using
> > such a databa
On Wed, Jul 20, 2011 at 7:15 AM, Mark Nutter wrote:
>> * Add support for databases that cannot return generated keys (e.g., HSQLDB)
>> - insert operations silently return the insert counts instead of
>> generated keys
>> - it is the user's responsibility to handle this if you're using
>> such a
> * Add support for databases that cannot return generated keys (e.g., HSQLDB)
> - insert operations silently return the insert counts instead of
> generated keys
> - it is the user's responsibility to handle this if you're using
> such a database!
If I'm understanding this correctly, this means
Changes in 0.0.5:
* Add prepare-statement function to ease creation of PreparedStatement
with common options:
- see docstring for details
* with-query-results now allows the SQL/params vector to be:
- a PreparedStatement object, followed by any parameters the SQL needs
- a SQL query string,
