Bug #104211 | ON DUPLICATE KEY UPDATE and table alias for new VALUES function replacement | ||
---|---|---|---|
Submitted: | 5 Jul 2021 20:54 | Modified: | 7 Jul 2021 13:19 |
Reporter: | Roman Roman | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Parser | Severity: | S3 (Non-critical) |
Version: | 8.0.x | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[5 Jul 2021 20:54]
Roman Roman
[6 Jul 2021 11:42]
MySQL Verification Team
Hi Mr. Roman, Thank you for your bug report. However, your report is not totally clear to us. Would you be so kind and to quote from latest release of our Reference Manual for 8.0, that syntax that you are trying to use should be working. Thank you in advance.
[7 Jul 2021 11:46]
Roman Roman
I don't understand how to replace "`-uni_works`" in expression with aliase or use it without aliase. I think use full db_name.table_name every time in ON DUPLICATE KEY UPDATE every time is not very interesting.
[7 Jul 2021 13:19]
MySQL Verification Team
Hi Mr. Roman Roman, You have not replied at all to our last comment. Next, you are asking us questions on how to change your SQL statements, which is not part of the bug reporting process. Not a bug.
[7 Jul 2021 19:02]
Roy Lyseng
You can name the columns in the VALUES clause, as in: INSERT INTO t(id, title) VALUES(-1,'Test') AS v(a,b) ON DUPLICATE KEY UPDATE title=CONCAT(title,v.b); This way, it is easy to obtain non-ambiguous column names. Without explicit names, the columns are called column_0, column_1, etc...
[8 Jul 2021 11:35]
MySQL Verification Team
Thanks a lot, Roy ....