-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
VALUES not accessible by variable name in ON DUPLICATE KEY UPDATE #1225
Comments
@Hydrocharged got a ETA on this one? |
What would you say the priority is for it? |
It's bug in my view, since it renders the most common use-case for the feature not really usable... unless I am missing some way of accessing the values tuple by name? |
Daylon, just fix this.
…On Fri, Jan 22, 2021 at 8:55 AM Oscar Batori ***@***.***> wrote:
It's bug in my view, since it renders the most common use-case for the
feature not really usable... unless I am missing some way of accessing the
values tuple by name?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1225 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJAR3B7UMYXKGZCLG6DDADS3GUY7ANCNFSM4WGJDFUQ>
.
|
@oscarbatori dolthub/go-mysql-server#273 |
@Hydrocharged so to be clear we do support the I agree with the linked issue that this is recently deprecated enough such that we should support it. In particular we are using it via clients that generate SQL in the legacy syntax. |
Yes, the referenced PR is adding the functionality. |
It seems that although we support
ON DUPLICATE KEY UPDATE
, we do not provide access to theVALUES
by variable which is normally how that statement is used:The text was updated successfully, but these errors were encountered: