Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Strucure Sync Tool And Mysql 5.1

forums forums SQLyog SQLyog: Bugs / Feature Requests Strucure Sync Tool And Mysql 5.1

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #9398
      peterlaursen
      Participant

      You will probably get across this yourself, but nevertheless I write it here too!

      I tried the structure sync tool with MySQL 5.1 and this 5.1 database

      Code:
      CREATE TABLE employees (
        id INT NOT NULL,
        fname VARCHAR(30),
        lname VARCHAR(30),
        hired DATE NOT NULL DEFAULT '1970-01-01',
        separated DATE NOT NULL DEFAULT '9999-12-31',
        job_code INT,
        store_id INT
      )
      PARTITION BY LIST(store_id) (
        PARTITION pNorth VALUES IN (3,5,6,9,17),
        PARTITION pEast VALUES IN (1,2,10,11,19,20),
        PARTITION pWest VALUES IN (4,12,13,14,18),
        PARTITION pCentral VALUES IN (7,8,15,16)
      );

      and an identical 5.0 database except that there are no partitions here.

      Structure sync 5.0 > 5.1 generates:

      /* Alter table in Second database */

      alter table `test2`.`employees` type=MyISAM;

      That works … however as a result of executing this partitions are remomed from the table. That should be optional I think! Or some warning should be displayed.

      Structure sync 5.1 > 5.0 generates:

      /* Alter table in First database */

      alter table `test2`.`employees` type=PARTITION;

      That is invalid of course and returns:

      “Error Code : 1286

      Unknown table engine 'PARTITION'”

    • #20010
      Ritesh
      Member

      Complete support for 5.1 and partition table related issues will be provided in v5.1.

    • #20011
      peterlaursen
      Participant

      There is a brandnew MySQL Administrator (1.1.6) being uploaded to FTP-mirrors right now. It does the same – mismatches engine type with PARTITION keyword.

Viewing 2 reply threads
  • You must be logged in to reply to this topic.