diff options
| author | Sergei Golubchik <serg@mariadb.org> | 2023-05-03 15:37:05 +0200 |
|---|---|---|
| committer | Sergei Golubchik <serg@mariadb.org> | 2023-05-04 16:07:39 +0200 |
| commit | 4d6e458f9f3956931b7c4c093fb9a0775faa9931 (patch) | |
| tree | 03e5a02320a7cdf13e4ad03bab8825d98c8eab5a /strings/latin2.def | |
| parent | f5e7c56e3254271a434253ae1367a7be7c429f94 (diff) | |
| download | mariadb-git-4d6e458f9f3956931b7c4c093fb9a0775faa9931.tar.gz | |
MDEV-31164 default current_timestamp() not working when used INSERT ON DUPLICATE KEY in some cases
select_insert::store_values() must reset
has_value_set bitmap before every row, just like mysql_insert() does.
because ON DUPLICATE KEY UPDATE and triggers modify it
Diffstat (limited to 'strings/latin2.def')
0 files changed, 0 insertions, 0 deletions