Synchronization problem with "SUBPARTITION BY KEY"

Discussion of open issues, suggestions and bugs regarding database management and administration tools for MySQL
Post Reply
michabbb
Posts: 217
Joined: Mon 21 Nov 2011 02:35
Location: DE
Contact:

Synchronization problem with "SUBPARTITION BY KEY"

Post by michabbb » Thu 16 Feb 2012 22:54

dear support,

after creating a table by "Synchronization" i switched source and destination and made the sync again. the same table, that was created at the first time, now appears to be changed, because of this lines:

Code: Select all

SUBPARTITION BY KEY (`llog_id_type`)
and

Code: Select all

SUBPARTITION BY KEY (llog_id_type)
would be nice if you fix that in your next updates ;)

thank you,
michael

alexa

Post by alexa » Fri 17 Feb 2012 11:04

Hello,

We are currently investigating this issue and will get back to you with a result asap.

michabbb
Posts: 217
Joined: Mon 21 Nov 2011 02:35
Location: DE
Contact:

Post by michabbb » Fri 30 Mar 2012 15:13

any news ?

alexa

Post by alexa » Mon 02 Apr 2012 13:27

Sorry for the delay on this.

We still were not able to reproduce the issue.

Could you please provide us the CREATE TABLE statement of the table (right-click the table in Database Explorer and select 'Generate Script As -> CREATE' from the popup menu)?

Since it may contain confidential information, we suggest you to send it straight to our support system e-mail address which is supportATdevartDOTcom, so we will keep further correspondence with you via that system.

michabbb
Posts: 217
Joined: Mon 21 Nov 2011 02:35
Location: DE
Contact:

Post by michabbb » Thu 12 Apr 2012 13:40

hi,

here is the create statement from the mysql server version 5.5.8

Code: Select all

CREATE TABLE IF NOT EXISTS logging
(
  llog_id INT(11) NOT NULL AUTO_INCREMENT,
  llog_id_type CHAR(5) NOT NULL,
  llog_id_value INT(11) NOT NULL,
  llog_db_created TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (llog_id, llog_db_created, llog_id_type),
  INDEX IX_lister_logging (llog_id_type, llog_id_value)
) ENGINE = MYISAM AUTO_INCREMENT = 22260 AVG_ROW_LENGTH = 18 CHARACTER SET 
latin1 COLLATE latin1_swedish_ci PARTITION BY RANGE (unix_timestamp(
  llog_db_created)) SUBPARTITION BY KEY (`llog_id_type`) (PARTITION partition1 
  VALUES LESS THAN (1328050800) ENGINE = MYISAM (SUBPARTITION partition1sp0 
  ENGINE = MYISAM), PARTITION partition2 VALUES LESS THAN (1330556400) ENGINE = 
  MYISAM (SUBPARTITION partition2sp0 ENGINE = MYISAM), PARTITION partition3 
  VALUES LESS THAN (1333231200) ENGINE = MYISAM (SUBPARTITION partition3sp0 
  ENGINE = MYISAM), PARTITION partition4 VALUES LESS THAN (1335823200) ENGINE = 
  MYISAM (SUBPARTITION partition4_subpartition1 ENGINE = MYISAM), PARTITION 
  partition5 VALUES LESS THAN (1338501600) ENGINE = MYISAM (SUBPARTITION 
  partition5_subpartition1 ENGINE = MYISAM), PARTITION partition6 VALUES LESS 
  THAN (1341093600) ENGINE = MYISAM (SUBPARTITION partition6_subpartition1 
  ENGINE = MYISAM), PARTITION partition7 VALUES LESS THAN (1343772000) ENGINE = 
  MYISAM (SUBPARTITION partition7_subpartition1 ENGINE = MYISAM), PARTITION 
  partition8 VALUES LESS THAN (1346450400) ENGINE = MYISAM (SUBPARTITION 
  partition8_subpartition1 ENGINE = MYISAM), PARTITION partition9 VALUES LESS 
  THAN (1349042400) ENGINE = MYISAM (SUBPARTITION partition9_subpartition1 
  ENGINE = MYISAM), PARTITION partition10 VALUES LESS THAN (1351724400) ENGINE = 
  MYISAM (SUBPARTITION partition10_subpartition1 ENGINE = MYISAM), PARTITION 
  partition11 VALUES LESS THAN (1354316400) ENGINE = MYISAM (SUBPARTITION 
  partition11_subpartition1 ENGINE = MYISAM), PARTITION partition12 VALUES LESS 
  THAN (MAXVALUE) ENGINE = MYISAM (SUBPARTITION partition12_subpartition1 ENGINE 
  = MYISAM));
and here is the create from the other mysql server i compare the table with (version 5.1.49-3-log)

Code: Select all

CREATE TABLE IF NOT EXISTS logging
(
  llog_id INT(11) NOT NULL AUTO_INCREMENT,
  llog_id_type CHAR(5) NOT NULL,
  llog_id_value INT(11) NOT NULL,
  llog_db_created TIMESTAMP DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (llog_id, llog_db_created, llog_id_type),
  INDEX IX_lister_logging (llog_id_type, llog_id_value)
) ENGINE = MYISAM AUTO_INCREMENT = 1 CHARACTER SET latin1 COLLATE 
latin1_swedish_ci PARTITION BY RANGE (unix_timestamp(llog_db_created)) 
  SUBPARTITION BY KEY (llog_id_type) (PARTITION partition1 VALUES LESS THAN (
  1328050800) ENGINE = MYISAM (SUBPARTITION partition1sp0 ENGINE = MYISAM), 
  PARTITION partition2 VALUES LESS THAN (1330556400) ENGINE = MYISAM (
  SUBPARTITION partition2sp0 ENGINE = MYISAM), PARTITION partition3 VALUES LESS 
  THAN (1333231200) ENGINE = MYISAM (SUBPARTITION partition3sp0 ENGINE = MYISAM)
  , PARTITION partition4 VALUES LESS THAN (1335823200) ENGINE = MYISAM (
  SUBPARTITION partition4_subpartition1 ENGINE = MYISAM), PARTITION partition5 
  VALUES LESS THAN (1338501600) ENGINE = MYISAM (SUBPARTITION 
  partition5_subpartition1 ENGINE = MYISAM), PARTITION partition6 VALUES LESS 
  THAN (1341093600) ENGINE = MYISAM (SUBPARTITION partition6_subpartition1 
  ENGINE = MYISAM), PARTITION partition7 VALUES LESS THAN (1343772000) ENGINE = 
  MYISAM (SUBPARTITION partition7_subpartition1 ENGINE = MYISAM), PARTITION 
  partition8 VALUES LESS THAN (1346450400) ENGINE = MYISAM (SUBPARTITION 
  partition8_subpartition1 ENGINE = MYISAM), PARTITION partition9 VALUES LESS 
  THAN (1349042400) ENGINE = MYISAM (SUBPARTITION partition9_subpartition1 
  ENGINE = MYISAM), PARTITION partition10 VALUES LESS THAN (1351724400) ENGINE = 
  MYISAM (SUBPARTITION partition10_subpartition1 ENGINE = MYISAM), PARTITION 
  partition11 VALUES LESS THAN (1354316400) ENGINE = MYISAM (SUBPARTITION 
  partition11_subpartition1 ENGINE = MYISAM), PARTITION partition12 VALUES LESS 
  THAN (MAXVALUE) ENGINE = MYISAM (SUBPARTITION partition12_subpartition1 ENGINE 
  = MYISAM));
even both create statemants seems to be indentical the compare schema always shows this (as i posted before):

SUBPARTITION BY KEY (`llog_id_type`)

vs.

SUBPARTITION BY KEY (llog_id_type)

source mysql server: 5.5.8
target mysql server: 5.1.49-3-log

thank you!
micha

alexa

Post by alexa » Fri 13 Apr 2012 11:59

We are planning to implement a new feature that allows ignoring quotes in one of the next versions of dbForge Studio for MySQL. So, there will no be such problem then.

alexa

Post by alexa » Mon 23 Apr 2012 13:29

We would like to let you know that the new versions of the products, where the issue is fixed, have been released and are available for downloading:

http://www.devart.com/dbforge/mysql/stu ... nload.html
http://www.devart.com/dbforge/mysql/sch ... nload.html

Thank you for your help in improving our products.

michabbb
Posts: 217
Joined: Mon 21 Nov 2011 02:35
Location: DE
Contact:

Post by michabbb » Wed 25 Apr 2012 09:53

hi, looks like its fixed, thank you!! ;)

Post Reply