Support last insert id variable @@identity like function LAST_INSERT_ID() #2016
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
test this please |
|
ok to test |
|
Automated message: PR pending admin approval for build testing |
|
Thank you @ahaha-zhang |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Rene:
I noticed that proxysql has supported to return the correct last_insert_id directly when clients execute built-in function last_insert_id() .#1421.
Thus, there is a consistent behavior between "select @@identity" and "select last_insert_is()" in MySQL. Supporting last-insert-id variable @@identity like function LAST_INSERT_ID() is more applicable and consistent for connection drivers.