Hello,
After some tests, PhPMyAdmin (version 4.3.13) seems to be the responsible.
If I export the structure (or structure and data) of my Database with this version, I don't have the notion of Primary key and AUTO_INCREMENT
CREATE TABLE IF NOT EXISTS `prjaccessprofile` (
`id` int(12) unsigned NOT NULL,
`name` varchar(100) DEFAULT NULL,
`description` mediumtext,
`idAccessScopeRead` int(12) DEFAULT NULL,
`idAccessScopeCreate` int(12) DEFAULT NULL,
`idAccessScopeUpdate` int(12) DEFAULT NULL,
`idAccessScopeDelete` int(12) DEFAULT NULL,
`sortOrder` int(3) DEFAULT NULL,
`idle` int(1) unsigned DEFAULT '0'
) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8
The same table, with an export with an other version of PhpMyAdmin (here an older version 4.1.6) give this result, correct
CREATE TABLE IF NOT EXISTS `prjaccessprofile` (
`id` int(12) unsigned NOT NULL AUTO_INCREMENT,
`name` varchar(100) DEFAULT NULL,
`description` mediumtext,
`idAccessScopeRead` int(12) DEFAULT NULL,
`idAccessScopeCreate` int(12) DEFAULT NULL,
`idAccessScopeUpdate` int(12) DEFAULT NULL,
`idAccessScopeDelete` int(12) DEFAULT NULL,
`sortOrder` int(3) DEFAULT NULL,
`idle` int(1) unsigned DEFAULT '0',
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=14 ;
My production environment is in version 4.3.13 and my test environment is in 4.1.6.
Before any change of version, I make a backup (normal
), with a dump executed from PhpMyAdmin (3 dumps : structure, data, structure and data).
Few weeks ago, the update was not good (problem with formatting - see ticket in the forum). so I restored my precedent database version......and the problem come from this restoration
The dump did'nt have primary key and AUTO_INCREMENT and my base was corrupted
I can reproduce this problemon all my test environment. I'm interested to know if other people can also reproduce it ?
Thanks