You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following code yields a different result when used with the mysql instead of the sqlite driver.
Instead of using ON CONFLICT DO NOTHING RETURNING `id`,`id`;, this driver should do a ON CONFLICT DO UPDATE SET `id`=`id` RETURNING `id`,`id`; just as the mysql driver does.
Output when using sqlite:
2023/01/25 00:34:39 User #0: Peter1, country: New Zealand
2023/01/25 00:34:39 User #1: Peter2, country: [EMPTY]
(Correct) output when using mysql:
2023/01/25 00:34:39 User #0: Peter1, country: New Zealand
2023/01/25 00:34:39 User #1: Peter2, country: Germany
The following code yields a different result when used with the mysql instead of the sqlite driver.
Instead of using
ON CONFLICT DO NOTHING RETURNING `id`,`id`;
, this driver should do aON CONFLICT DO UPDATE SET `id`=`id` RETURNING `id`,`id`;
just as the mysql driver does.Output when using sqlite:
(Correct) output when using mysql:
The text was updated successfully, but these errors were encountered: