Skip to content

jdbc: Support Connection.prepareStatement(sql, Statement.NO_GENERATED_KEYS) #78

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
Totktonada opened this issue Nov 1, 2018 · 0 comments
Closed

jdbc: Support Connection.prepareStatement(sql, Statement.NO_GENERATED_KEYS) #78

Totktonada opened this issue Nov 1, 2018 · 0 comments
Assignees
@nicktorwald
Labels
bug Something isn't working jdbc
Milestone
JDBC MVP

Comments

@Totktonada
Copy link
Member

We should not raise SQLFeatureNotSupportedException is the case of the 2nd parameter is Statement.NO_GENERATED_KEYS.
@Totktonada Totktonada added bug Something isn't working jdbc labels Nov 1, 2018
@Totktonada Totktonada added this to the JDBC MVP milestone Nov 1, 2018
nicktorwald added a commit that referenced this issue Apr 9, 2019
@nicktorwald
Support Statement.NO_GENERATED_KEYS option
5bb31fa 
Add a proper behaviour when Connection.prepareStatement,
Statement.execute, and Statement.executeUpdate are called with the
Statement.NO_GENERATED_KEYS flag.

Return an empty generated keys when the Statement.NO_GENERATED_KEYS is
set as a special case of a generated keys absence.

Fixes: #78
nicktorwald added a commit that referenced this issue Apr 9, 2019
@nicktorwald
Support Statement.NO_GENERATED_KEYS option
566bde1 
Add a proper behaviour when Connection.prepareStatement,
Statement.execute, and Statement.executeUpdate are called with the
Statement.NO_GENERATED_KEYS flag.

Return an empty generated keys when the Statement.NO_GENERATED_KEYS is
set as a special case of a generated keys absence.

Fixes: #78
@nicktorwald nicktorwald mentioned this issue Apr 9, 2019
Closed
@nicktorwald nicktorwald self-assigned this Apr 9, 2019
nicktorwald added a commit that referenced this issue Apr 17, 2019
@nicktorwald
Support Statement.NO_GENERATED_KEYS option
b27f5a0 
Add a proper behaviour when Connection.prepareStatement,
Statement.execute, and Statement.executeUpdate are called with the
Statement.NO_GENERATED_KEYS flag.

Return an empty generated keys when the Statement.NO_GENERATED_KEYS is
set as a special case of a generated keys absence.

Fixes: #78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nicktorwald nicktorwald

Labels
bug Something isn't working jdbc
Projects
None yet
Milestone
JDBC MVP
Development

Successfully merging a pull request may close this issue.

Support Statement.NO_GENERATED_KEYS option tarantool/tarantool-java
2 participants
@Totktonada @nicktorwald