Bug #20828 Additional option "mysql50" needed for mysqldump --compatible=....
Submitted: 3 Jul 2006 19:00 Modified: 8 Sep 2006 11:26
Reporter: Nikolay Grishakin Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Backup Severity:S3 (Non-critical)
Version:5.1 OS:Linux (Linux)
Assigned to: Magnus Blåudd CPU Architecture:Any
Tags: Test blocking

[3 Jul 2006 19:00] Nikolay Grishakin 
Description:
Additional option "mysql50" needed for mysqldump --compatible=....
"Compatible" option is used to specify different version of MySQL. For current version only "mysql40" is available but not "mysql50". We need this to get rid of CREATE LOGFILE GROUP, TABLE SPACE and PARTITION statments from create table.

How to repeat:
...
[27 Jul 2006 9:33] Magnus Blåudd 
When dumping a feature not found in a previous version of mysql, it should be surrounded by "version limit comments"
For example /*!50100 CREATE TABLESPACE */
[27 Jul 2006 10:12] Magnus Blåudd 
Tablespaces are dumped only if the option --all-tablespaces are given to mysqldump. By omitting that parameter, no tablespace infor should be dumped. 

If that is the case please give exact explanation of when and where it occurs.
[1 Aug 2006 19:16] Nikolay Grishakin 
Yes, it does not save CREATE TABLR SPACE and LG in a resulted sql file after using mysqldump but it leaves TS information in CREATE TABLE statments. For example, I loaded database in 5.1 using load_tpcb.pl script and took a dump.
Table "history" had "TABLESPACE ts1" in it.

DROP TABLE IF EXISTS `history`;
CREATE TABLE `history` (
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `aid` int(11) DEFAULT NULL,
  `tid` int(11) DEFAULT NULL,
  `bid` int(11) DEFAULT NULL,
  `TransTime` datetime DEFAULT NULL,
  `scriptId` char(10) DEFAULT NULL,
  `filler` char(80) DEFAULT NULL,
  PRIMARY KEY (`id`)
) TABLESPACE ts1 STORAGE DISK ENGINE=ndbcluster DEFAULT CHARSET=latin1;
[3 Aug 2006 14:17] Magnus Blåudd 
Isn't this a duplicate of Bug#20841 mysqldump fails to store right info with --compatible=mysql40 option
[7 Aug 2006 17:39] Nikolay Grishakin 
It will be a duplicate of Bug#20841 if we decide not to implement
--compatible=mysql50 option.
[8 Sep 2006 11:26] Magnus Blåudd 
Duplicate of bug#20841, we will not implement mysql50 option to mysqldump. All such issues will be fixed by adding not before version comments on the form /*!<version> <feature>/*