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: Peter Brawley
Date: March 22, 2021 10:56AM

Please give an example of a case not covered by the docs you cited?

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

749

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

383

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

393

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

470

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

425

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

364

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

393

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.