summaryrefslogtreecommitdiff
path: root/mysql-test/main/ddl_i18n_koi8r.result
diff options
context:
space:
mode:
authorVicențiu Ciorbaru <vicentiu@mariadb.org>2020-10-15 18:02:24 +0300
committerVicențiu Ciorbaru <vicentiu@mariadb.org>2020-10-28 11:38:14 +0200
commitf6549e95448e5cce52336361f5a59d1edcdac46a (patch)
treebd1d306e99911ed3bbddf139e8ed464bc4f3d196 /mysql-test/main/ddl_i18n_koi8r.result
parent85c686e2d1576b0be6daf11849167bb1c38e3603 (diff)
downloadmariadb-git-f6549e95448e5cce52336361f5a59d1edcdac46a.tar.gz
MDEV-18323 Convert MySQL JSON type to MariaDB TEXT in mysql_upgrade
This patch solves two key problems. 1. There is a type number clash between MySQL and MariaDB. The number 245, used for MariaDB Virtual Fields is the same as MySQL's JSON. This leads to corrupt FRM errors if unhandled. The code properly checks frm table version number and if it matches 5.7+ (until 10.0+) it will assume it is dealing with a MySQL table with the JSON datatype. 2. MySQL JSON datatype uses a proprietary format to pack JSON data. The patch introduces a datatype plugin which parses the format and convers it to its string representation. The intended conversion path is to only use the JSON datatype within ALTER TABLE <table> FORCE, to force a table recreate. This happens during mysql_upgrade or via a direct ALTER TABLE <table> FORCE.
Diffstat (limited to 'mysql-test/main/ddl_i18n_koi8r.result')
0 files changed, 0 insertions, 0 deletions