Bug #108419 Contribution: Recognize \"ON DUPLICATE KEY UPDATE\" in \"INSERT SET\" State ...
Submitted: 7 Sep 2022 18:13 Modified: 21 Dec 2022 15:21
Reporter: OCA Admin (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: CPU Architecture:Any
Tags: Contribution

[7 Sep 2022 18:13] OCA Admin 
Description:
This bug tracks a contribution by Yamasaki Tadashi (Github user: tadashiya) as described in http://github.com/mysql/mysql-connector-j/pull/84

How to repeat:
See description

Suggested fix:
See contribution code attached
[7 Sep 2022 18:13] OCA Admin 
Contribution submitted via Github - Recognize "ON DUPLICATE KEY UPDATE" in "INSERT SET" Statement 
(*) Contribution by Yamasaki Tadashi (Github tadashiya, mysql-connector-j/pull/84#issuecomment-1239554198): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

Contribution: git_patch_1046023340.txt (text/plain), 3.16 KiB.
[8 Sep 2022 7:38] MySQL Verification Team 
Hello,

Thank you for the report and contribution.

Regards,
Ashwini Patil
[20 Sep 2022 22:30] Filipe Silva 
Duplicated by Bug#108379
[21 Dec 2022 15:21] Daniel So 
Posted by developer:
 
Added the following entry to the Connector/J 8.0.32 changelog: 

"When Connector/J looked for the presence of the ON DUPLICATE KEY UPDATE clause in prepared statements, it neglected the cases where the VALUES function was used without the VALUE(S) clause in INSERT statements. As a result, some statements that actually had the ON DUPLICATE KEY UPDATE clause were not caught, resulting in incorrect information for generated keys. Thanks to Yamasaki Tadashi for contributing to the fix."