MySQL

Known issues when migrating data from MySQL.

This page documents known issues you may encounter and suggested workarounds when migrating data from MySQL to YugabyteDB.

Contents

Approaching MAX/MIN double precision values are not exported

GitHub: Issue #188

Description: Exporting double precision values near MAX/MIN value may result in an out of range error. This is due to the difference in maximum supported precision values between the two databases. While MySQL supports up to 17 precision values, YugabyteDB supports up to 15.


Functional/Expression indexes fail to migrate

GitHub: Issue #579

Description: If your schema contains Functional/Expression indexes in MYSQL, the index creation fails with a syntax error during migration and doesn't get migrated.

Workaround: Manual intervention needed. You have to remove the back-ticks (``) from the exported schema files.

Example

An example schema on the source MySQL database is as follows:

CREATE INDEX exp_ind ON exp_index_test((year(`to_date`)));

The exported schema is as follows:

CREATE INDEX exp_ind ON exp_index_test ((extract(year from date(`to_date`))));

Suggested change to the schema is to remove the back-ticks as follows:

CREATE INDEX exp_ind ON exp_index_test ((extract(year from date(to_date))));

Exporting data from MySQL when table names include quotes

GitHub: Issue #320

Description: When exporting a schema from MySQL that includes a table name that has quotes, the table is exported with the table name converted to lowercase and without the quotes, resulting in an error.

Workaround: Manual intervention needed. You have to rename the table in MySQL and then export and import the data followed by renaming the table in YugabyteDB.

Example tables for source MySQL database is as follows:

show tables;
+----------------------+
| Tables_in_pk_missing |
+----------------------+
| "test_data_COPY"     |
| TEST_DATA            |
+----------------------+

The exported schema is as follows:

CREATE TABLE test_data_copy (
   id serial,
   first_name varchar(50),
   last_name varchar(50),
   email varchar(50),
   gender varchar(50),
   ip_address varchar(20),
   PRIMARY KEY (id)
) ;

Error when exporting data is as follows:

DBD::mysql::st execute failed: Table 'pk_missing.test_data_COPY' doesn't exist at /usr/local/share/perl5/Ora2Pg.pm line 14247.
DBD::mysql::st execute failed: Table 'pk_missing.test_data_COPY' doesn't exist at /usr/local/share/perl5/Ora2Pg.pm line 14247.

Suggested workaround is as follows:

  1. In MySQL, rename the table using a name without quotes using the following command:

    Alter table `"test_data_COPY"` rename test_data_COPY2;
    
  2. Export and import the data.

  3. In YugabyteDB, rename the table to include the quotes using the following command:

    Alter table test_data_copy2 rename to "test_data_COPY";
    

Spatial datatype migration is not yet supported

GitHub: Issue #137

Description: If your MYSQL schema contains spatial datatypes, the migration will not complete as this migration type is not yet supported by YugabyteDB Voyager. Supporting spatial datatypes will require extra dependencies such as PostGIS to be installed.

Workaround : None. A workaround is currently being explored.

Example

An example schema on the source database is as follows:

CREATE TABLE address (
  address_id int,
  add point,
  location GEOMETRY NOT NULL
);

Incorrect parsing of views involving functions without alias

GitHub: Issue #689

Description: If a view contains a function in its definition in a SELECT statement without any ALIAS, an alias corresponding to the function is appended to the schema. This results in an invalid schema.

Workaround: Remove or change the alias to a valid value.

Example

An example schema on the source database is as follows:

CREATE OR REPLACE VIEW v1 AS SELECT foo(id) FROM bar;

The exported schema is as follows:

CREATE OR REPLACE VIEW v1 AS SELECT foo(bar.id) AS foo(id) FROM bar;

Choose one from the following suggested changes to the schema.

  • Remove the alias as follows:

    CREATE OR REPLACE VIEW v1 AS SELECT foo(bar.id) FROM bar;
    
  • Change the alias as follows:

    CREATE OR REPLACE VIEW v1 AS SELECT foo(bar.id) AS foo FROM bar;
    

Datatype mismatch in objects causing issues

GitHub: Issue #690

Description: If you have an object which references a table column whose datatype has been mapped to something else, there may be datatype mismatch issues on the target YugabyteDB database.

Workaround: Type cast the reference to match the table column.

Example

In the following example, the table column type int is mapped to bigint and causes issues when referenced in the view via the function, because the function parameter remains as int type.

/* Table definition */
DROP TABLE IF EXISTS bar;
CREATE TABLE bar(
id int,
p_name varchar(10)
);

/* Function definition */
DROP FUNCTION IF EXISTS foo;
delimiter //
CREATE FUNCTION foo (p_id int)
RETURNS varchar(20)
READS SQL DATA
  BEGIN
    RETURN (SELECT p_name FROM bar WHERE p_id=id);
  END//
delimiter ;

/* View definition */
CREATE OR REPLACE VIEW v2 AS SELECT foo(id) AS p_name FROM bar;

The exported schema is as follows:

/* Table definition */
CREATE TABLE bar(
id bigint,
p_name varchar(10)
);

/* Function definition */
CREATE OR REPLACE FUNCTION foo (p_id integer) RETURNS varchar AS $body$
  BEGIN
    RETURN(SELECT p_name FROM bar WHERE p_id=id);
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

/* View definition */
CREATE OR REPLACE VIEW v1 AS SELECT foo(bar.id) AS p_name FROM bar;

Suggested change is to type cast the reference to match the table column as follows:

CREATE OR REPLACE VIEW v1 AS SELECT foo(bar.id::int) AS p_name FROM bar;

drop temporary table statements are not supported

GitHub: Issue #705

Description: If you have a temporary table defined in a function or stored procedure in MySQL and you have a drop temporary table statement associated with it, the schema gets exported as is, which is an invalid syntax in YugabyteDB.

Workaround: Manually remove the temporary clause from the drop statement.

Example

An example schema on the source database is as follows:

/* procedure definition */
delimiter //
CREATE PROCEDURE foo(p_id int)
deterministic
  BEGIN
    DROP TEMPORARY TABLE IF EXISTS temp;
    CREATE TEMPORARY TABLE temp(id int, name text);
    INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
    SELECT name FROM temp;
  END//
delimiter;

The exported schema is as follows:

CREATE OR REPLACE PROCEDURE foo (p_id integer) AS $body$
  BEGIN
    DROP TEMPORARY TABLE IF EXISTS temp;
    CREATE TEMPORARY TABLE temp(id int, name text);
    INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
    SELECT name FROM temp;
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

Suggested change to the schema is to remove the temporary clause from the drop statement as follows:

CREATE OR REPLACE PROCEDURE foo (p_id integer) AS $body$
  BEGIN
    DROP TABLE IF EXISTS temp;
    CREATE TEMPORARY TABLE temp(id int, name text);
    INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
    SELECT name FROM temp;
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

Key defined for a table in functions/procedures cause issues

GitHub: Issue #707

Description: If you have a basic key defined for a table in a function/procedure, the schema is exported as is, and causes issues because using a key in YugabyteDB is an invalid syntax.

Workaround: Manually remove the key from the exported schema, or create an index.

Example

An example schema on the source database is as follows:

/* function definition */

delimiter //
CREATE FUNCTION foo (p_id int)
RETURNS varchar(20)
READS SQL DATA
  BEGIN
    CREATE TEMPORARY TABLE temp(id int, name text,key(id));
    INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
    RETURN (SELECT name FROM temp);
  END//

The exported schema is as follows:

CREATE OR REPLACE FUNCTION foo (p_id integer) RETURNS varchar AS $body$
  BEGIN
    CREATE TEMPORARY TABLE temp(id int, name text,key(id));
    INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
    RETURN (SELECT name FROM temp);
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

Choose one from the following suggested changes to the schema.

  • Remove the key from the schema as follows:

    CREATE OR REPLACE FUNCTION foo (p_id integer) RETURNS varchar AS $body$
      BEGIN
        CREATE TEMPORARY TABLE temp(id int, name text);
        INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
        RETURN (SELECT name FROM temp);
      END;
    $body$
    LANGUAGE PLPGSQL
    SECURITY DEFINER
    ;
    
  • Create an index manually as follows:

    CREATE OR REPLACE FUNCTION foo (p_id integer) RETURNS varchar AS $body$
      BEGIN
        CREATE TEMPORARY TABLE temp(id int, name text);
        CREATE INDEX index_as_key ON temp(id);
        INSERT INTO temp(id,name) SELECT id,p_name FROM bar WHERE p_id=id;
        RETURN (SELECT name FROM temp);
      END;
    $body$
    LANGUAGE PLPGSQL
    SECURITY DEFINER
    ;
    

Multiple declarations of variables in functions

GitHub: Issue #708

Description: If you re-initializate a variable in a function in MySQL using the set statement, the variable is declared twice with different datatypes in the exported schema.

Workaround: Manually remove the extra declaration of the variable from the exported schema file.

Example

An example declaration of the variable in the schema is as follows:

/* function definition */
delimiter //
CREATE FUNCTION xyz()
RETURNS VARCHAR(10)
READS SQL DATA
  BEGIN
    DECLARE max_date date;
    SET max_date=(SELECT CURRENT_DATE());
    SET @max_date=max_date;
    RETURN max_date;
  END //
delimiter;

The exported schema is as follows:

CREATE OR REPLACE FUNCTION xyz () RETURNS varchar AS $body$
DECLARE
max_date timestamp;max_date date;
  BEGIN
    max_date = (SELECT CURRENT_DATE
    );
    max_date:=max_date;
    RETURN max_date;
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

Suggested change to the schema is to remove the extra declaration of the variable as follows:

CREATE OR REPLACE FUNCTION xyz () RETURNS varchar AS $body$
DECLARE
max_date timestamp;
  BEGIN
    max_date = (SELECT CURRENT_DATE
    );
    max_date:=max_date;
    RETURN max_date;
  END;
$body$
LANGUAGE PLPGSQL
SECURITY DEFINER
;

Exporting text type columns with default value

GitHub: Issue #621

Description: If you have a default value for text type columns in MYSQL, it does not export properly and fails during import.

Workaround: Manually remove the extra encoding DDLs from the exported files.

Example

An example schema on the source database is as follows:

CREATE TABLE text_types (
    id int,
    tt TINYTEXT DEFAULT ('c'),
    te TEXT DEFAULT ('abc'),
    mt MEDIUMTEXT DEFAULT ('abc'),
    lt LONGTEXT DEFAULT ('abc')
);

The exported schema is as follows:

CREATE TABLE text_types (
    id bigint,
	  tt text DEFAULT _utf8mb4\'c\',
    te text DEFAULT _utf8mb4\'abc\',
    mt text DEFAULT _utf8mb4\'abc\',
    lt text DEFAULT _utf8mb4\'abc\'
) ;

Suggested changes to the schema is to remove the encoding as follows:

CREATE TABLE text_types (
    id bigint,
    tt text DEFAULT 'c',
    te text DEFAULT 'abc',
    mt text DEFAULT 'abc',
    lt text DEFAULT 'abc'
) ;