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 script uses "schnitzler/mysqldump" image in order to create myqldump from Azure Database for MySQL however this image uses MariaDB Ver 10.17 Distrib 10.3.15-MariaDB, for Linux (x86_64) under the hood.
Due to this reason, there may be some problems during restoring DB from the generated dump file such as restoring generated column. MySQL 8.x doesn't allow input for generated column except DEFAULT. However, MariaDB mysqldump prepares INSERT statements with data. Then, we face the the following error.
ERROR 3105 (HY000) at line XXX: The value specified for generated column 'XXX' in table 'XXX' is not allowed.
Maybe, it would be good to mention these details.
The text was updated successfully, but these errors were encountered:
serefacet
changed the title
MariaDB mysqldump is not fully compatible while restoring
MariaDB mysqldump is not fully compatible with Azure Database for MySQL while restoring
Apr 26, 2022
serefacet
changed the title
MariaDB mysqldump is not fully compatible with Azure Database for MySQL while restoring
MariaDB mysqldump file is not fully compatible with Azure Database for MySQL while restoring
Apr 26, 2022
Hey team,
The script uses "schnitzler/mysqldump" image in order to create myqldump from Azure Database for MySQL however this image uses MariaDB
Ver 10.17 Distrib 10.3.15-MariaDB, for Linux (x86_64)
under the hood.Due to this reason, there may be some problems during restoring DB from the generated dump file such as restoring generated column. MySQL 8.x doesn't allow input for generated column except DEFAULT. However, MariaDB mysqldump prepares INSERT statements with data. Then, we face the the following error.
Maybe, it would be good to mention these details.
The text was updated successfully, but these errors were encountered: