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
Do not rewrite last_insert_id
function calls with arguments.
#12997
Do not rewrite last_insert_id
function calls with arguments.
#12997
Conversation
Signed-off-by: Arthur Schreiber <arthurschreiber@github.com>
Review ChecklistHello reviewers! 👋 Please follow this checklist when reviewing this Pull Request. General
If a new flag is being introduced:
If a workflow is added or modified:
Bug fixes
Non-trivial changes
New/Existing features
Backward compatibility
|
@arthurschreiber Can you also write up an issue for this specific regression? |
Earlier we were writing the error in the rewrite struct |
@harshit-gangal Can you elaborate on that? I'm not sure I understand what is missing here. 😞 I tested the fix against our codebase and it seems to be working as expected? |
Replaced by #13026 |
Description
With Vitess v16, the rewriting behaviour of
last_insert_id
and other function calls became more strict. It explicitly returns an error now whenlast_insert_id
is called with an argument, whereas before it would just not perform any rewriting and pass the function call to MySQL as-is.This change restores the previous behaviour of not rewriting
last_insert_id
funciton calls that have arguments.Related Issue(s)
N/A
Checklist
Deployment Notes
N/A