Page MenuHomePhabricator

[keyserver] Use VALUE instead of VALUES in DUPLICATE KEY UPDATE on MariaDB
ClosedPublic

Authored by ashoat on Jul 13 2022, 4:27 PM.
Tags
None
Referenced Files
F3373700: D4528.diff
Tue, Nov 26, 11:05 AM
Unknown Object (File)
Fri, Nov 8, 9:28 AM
Unknown Object (File)
Fri, Nov 8, 7:35 AM
Unknown Object (File)
Thu, Nov 7, 11:24 PM
Unknown Object (File)
Thu, Nov 7, 11:20 PM
Unknown Object (File)
Sat, Nov 2, 6:32 PM
Unknown Object (File)
Sat, Nov 2, 6:32 PM
Unknown Object (File)
Sat, Nov 2, 6:31 PM

Details

Summary

See here – MariaDB 10.3.3 and higher require this change.

Depends on D4522

Test Plan

I ran the web application and clicked around a bunch. Full test plan will come later

Diff Detail

Repository
rCOMM Comm
Branch
ashoat/mariadb
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

In retrospect, it's not clear if this is necessary. From the docs:

The VALUES() function can still be used even from MariaDB 10.3.3, but only in INSERT ... ON DUPLICATE KEY UPDATE statements; it's a syntax error otherwise.

The diff is already out, but I'm still leaning towards abandoning it in order to simplify the code. Curious for other people's thoughts.

The diff is already out, but I'm still leaning towards abandoning it in order to simplify the code.

Don't feel strongly. It does mean we have more branching, but I think this is fine since we don't plan on supporting MySQL and MariaDB indefinitely.

Accepting because it looks fine, up to you

This revision is now accepted and ready to land.Jul 17 2022, 1:00 PM

Decided to leave this in. Branching indeed will be remove once MySQL is deprecated, and since we're using MariaDB going forward it's probably best to have the modern syntax