Bug #68512
closed
Mysql error running Upgrade Wizard
0%
Description
Update failed! SQL-ERROR: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '( type varchar(16) NOT NULL, tKey varchar(8) NOT NULL, tValue varchar(128) NOT N' at line 1 Update database schema: Create tables and fields CREATE TABLE IF ( type varchar(16) NOT NULL, tKey varchar(8) NOT NULL, tValue varchar(128) NOT NULL, index int(8) NOT NULL, id int(11) NOT NULL, deleted tinyint(4) NOT NULL default '0', rootPage int(11) NOT NULL, entityId int(11) NOT NULL, position int(11) NOT NULL, headline varchar(18) CHARACTER SET utf8 NOT NULL, subHeadline varchar(64) CHARACTER SET utf8 NOT NULL, link varchar(256) CHARACTER SET utf8 NOT NULL, name varchar(256) NOT NULL, clearName varchar(64) default NULL, placeholderId int(11) NOT NULL, picturePath varchar(256) CHARACTER SET utf8 NOT NULL, originalHeight int(11) NOT NULL, originalWidth int(11) NOT NULL, text varchar(2048) NOT NULL, iata varchar(3) NOT NULL ) ENGINE=MEMORY;
Following Code works:
CREATE TABLE `IF` ( type varchar(16) NOT NULL, tKey varchar(8) NOT NULL, tValue varchar(128) NOT NULL, index int(8) NOT NULL, id
int(11) NOT NULL, deleted tinyint(4) NOT NULL default '0', rootPage int(11) NOT NULL, entityId int(11) NOT NULL, position int(11)
NOT NULL, headline varchar(18) CHARACTER SET utf8 NOT NULL, subHeadline varchar(64) CHARACTER SET utf8 NOT NULL, link
varchar(256) CHARACTER SET utf8 NOT NULL, name varchar(256) NOT NULL, clearName varchar(64) default NULL, placeholderId int(11)
NOT NULL, picturePath varchar(256) CHARACTER SET utf8 NOT NULL, originalHeight int(11) NOT NULL, originalWidth int(11) NOT NULL,
text varchar(2048) NOT NULL, iata varchar(3) NOT NULL ) ENGINE=MEMORY;
Updated by Mathias Schreiber over 9 years ago
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
We strongly advise against using reserved keywords in schema definitions.
Keep in mind that you might want to use Databases different from MySQL rendering the backtick workaround rather useless.
Updated by Riccardo De Contardi about 9 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.