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

RETURNING does not trigger ExecuteListener.resultStart() and similar events #8942

Closed
lukaseder opened this issue Jul 15, 2019 · 2 comments
Closed

Comments

@lukaseder
Copy link
Member

Related to #8938, there are some dialects where, when using RETURNING explicitly, or implicitly, no ExecuteListener.resultStart() and similar events are triggered, as the Statement.getGeneratedKeys() result set is not consumed using a Cursor.

Affected dialects are:

  • Derby
  • H2
  • Informix
  • Ingres
  • MariaDB
  • MemSQL
  • MySQL
  • Redshift
  • SQL Server
  • Sybase ASE
@lukaseder
Copy link
Member Author

Like #8938, this is postponed to 3.13 as it is a very delicate change, and we want to release 3.12 soon.

@lukaseder
Copy link
Member Author

Duplicate of #14306

@lukaseder lukaseder marked this as a duplicate of #14306 May 24, 2023
3.19 Other improvements automation moved this from To do to Done May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

1 participant