Skip to content
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.

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

executeUpdate with RETURN_GENERATED_KEYS should return update count instead of -1 [JDBC351] #393

Closed
firebird-automations opened this issue Apr 28, 2014 · 6 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

executeUpdate with RETURN_GENERATED_KEYS should return update count instead of -1

See test org.firebirdsql.jdbc.TestFBStatementGeneratedKeys#⁠testExecuteUpdate_INSERT_returnGeneratedKeys_withReturning() (and other testExecuteUpdate_* tests)

Commits: 6d073cd

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

description: executeUpdate with RETURN_GENERATED_KEYS should return update count instead of -1

See test org.firebirdsql.jdbc.TestFBStatementGeneratedKeys#⁠testExecuteUpdate_INSERT_returnGeneratedKeys_withReturning()

=>

executeUpdate with RETURN_GENERATED_KEYS should return update count instead of -1

See test org.firebirdsql.jdbc.TestFBStatementGeneratedKeys#⁠testExecuteUpdate_INSERT_returnGeneratedKeys_withReturning() (and other testExecuteUpdate_* tests)

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Fixed in trunk with new handling of return generated keys. Needs additional test coverage.

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 3.0 [ 10440 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Added extra assertions

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment