MySQL :: Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

New Topic

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

Posted by: Jon Stephens
Date: March 27, 2021 10:42AM

Yes, please submit this to bugs.mysql.com using the category MySQL Server: Documentation.

Thanks!

Jon Stephens
MySQL Documentation Team @ Oracle

MySQL Dev Zone
MySQL Server Documentation
Oracle

Navigate: Previous Message• Next Message

Options: Reply• Quote

Subject

Views

Written By

Posted

Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

1069

Jens Hatlak

November 10, 2020 08:57AM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

611

Peter Brawley

March 22, 2021 10:56AM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

592

Jens Hatlak

March 22, 2021 01:00PM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

718

Peter Brawley

March 22, 2021 01:59PM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

623

Jens Hatlak

March 26, 2021 06:30AM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

546

Peter Brawley

March 26, 2021 01:31PM

Re: Suggested replacement for use of deprecated VALUES() to access new row values in INSERT ... SELECT ... ON DUPLICATE KEY UPDATE statements

594

Jon Stephens

March 27, 2021 10:42AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.