Upgraded From Mysql Community Edition 5.21 To 5.22a

[adarsh]

“I have problems …” Please explain the problems! the script imports OK here if we!

1)

change this

CREATE TABLE `A` (

`B` int(10) NOT NULL auto_increment

) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_spanish_ci;

to

1) change this

CREATE TABLE `A` (

`B` int(10) NOT NULL

) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_spanish_ci;

first thing you cannot create a table with autoincrement without key.

and

2) delete this line

/*!50003 DROP TRIGGER `trgA` */$$

The comments are not a comments really! /*!50003 DROP TRIGGER `trgA` */$$ for instance means that this will be executed on MySQL 5.0.3 and higher. Before that the line is skipped. Every backup program will have to do like this is backup/restore across MySQL versions shall be possible. Also all programs from MySQL themselves do. most of the MySQL server does not support this “Drop Trigger statement”.

[wchiquito]

Perfect! thanks.

I already understood:

SQLyog Backups are now 'backwards compatible' (they import on earlier MySQL versions due to the use of 'version-dependent conditional comments' (like /*!40101 Engine …*/)).

[peterlaursen]

However it is still a mystery to me how

Code:

CREATE TABLE `A` (
`B` int(10) NOT NULL auto_increment
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_spanish_ci;

(auto_increment and no key)

… comes into existence.  When exporting we do a “SHOW CREATE TABLE” statement only.

So this is what MySQL sends – unless you have edited the table?

[Author]

Posts