Bug #16510
closedExt mng / compare: missing columns with auto_increments
0%
Description
Problem:
I found a plugin where, for some strange reasons, one field was not created upon install of the extension. Nevertheless, the install tool, as well as ext. mng. has no problem of reproducing and displaying the error.
This would ordinary work fine, but with auto_increment values you need to specify the primary key as well in the same SQL stmt.
i.e. my problem was presented as if two sql stmts needed to be fired away:
1.
ALTER TABLE `tx_veguestbook_entries` ADD `uid` INT UNSIGNED NOT NULL AUTO_INCREMENT
2.
ALTER TABLE `tx_veguestbook_entries` PRIMARY KEY
This should of course have been:
ALTER TABLE `tx_veguestbook_entries` ADD `uid` INT UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY
Ofcourse this problem might only relate to extensions which exhibit this particular flaw, but AFAIK MySQL will not accept the SQL stmt. 1) since auto_increment should be pri key!
I'd ofcourse be happy to correct the issue if anyone can point me in the direction of the source to diff
:-)
(issue imported from #M4125)
Updated by Stefan Kreisberg about 18 years ago
whoops, sorry .. posted this one twice (doh!)
anyone - how do I remove the duplicant?