Compliance problem related to prepared statement and generated keys
-------------------------------------------------------------------
Key: SEQUOIA-876
URL: https://forge.continuent.org/jira/browse/SEQUOIA-876
Project: Sequoia
Type: Bug
Components: JDBC Driver
Versions: Sequoia 3.0 beta1, Sequoia 2.10.3
Reporter: Stephane Giron
Assigned to: Stephane Giron
Fix For: Sequoia 2.10.4, Sequoia 3.0 beta 2
- PreparedStatement.execute() when preparedStatement instance was created with
RETURN_GENERATED_KEYS do not return generated keys as expected
- connection.prepareStatement(SQL, autoGeneratedKeys) does not take into
account the autoGeneratedKeys parameter and the created preparedStatement was
always created with RETURN_GENERATED_KEYS.
- connection.prepareStatement(String sql, int resultSetType, int
resultSetConcurrency, int resultSetHoldability) was always creating
PreparedStatement with RETURN_GENERATED_KEYS.
- Some database drivers return generated keys, even when not precised with
RETURN_GENERATED_KEYS. An improvement would be to add an option of the url so
that this behavior can be simulated when using SEQUOIA driver.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
