Bug #48381
closed
after git pull db compare -> CREATE TABLE ( ( categories int(11) NOT NULL default '0' );
Added by Matthias Eberlein over 11 years ago.
Updated about 6 years ago.
Description
Hello TYPO3 People,
after a git pull TYPO3_6-1 i get in INSTALL TOOL DB Compare this db table error.
ALTER TABLE be_users CHANGE userMods userMods text;
Current value: varchar(255) default NULL
CREATE TABLE ( ( categories int(11) NOT NULL default '0' );
then Compare get the db error
CREATE TABLE ( ( categories int(11) NOT NULL default '0' );
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 '( ( categories int(11) NOT NULL default '0' )' at line 1
I think that have somthing to do with this [BUGFIX] be_users.userMods is too small to hold all modules https://review.typo3.org/#/c/20885/
greetings
matthias
Matthias Eberlein wrote:
Hello TYPO3 People,
after a git pull TYPO3_6-1 i get in INSTALL TOOL DB Compare this db table error.
ALTER TABLE be_users CHANGE userMods userMods text;
Current value: varchar(255) default NULL
CREATE TABLE ( ( categories int(11) NOT NULL default '0' );
then Compare get the db error
CREATE TABLE ( ( categories int(11) NOT NULL default '0' );
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 '( ( categories int(11) NOT NULL default '0' )' at line 1
I think that have somthing to do with this [BUGFIX] be_users.userMods is too small to hold all modules https://review.typo3.org/#/c/20885/
greetings
matthias
Tested on 2 Systems. One fresh Installation without any Installed Not System Extension.
I have this issue in 6.1.1-dev but not in 6.2-dev
- Status changed from New to Accepted
- Assignee set to Alexander Opitz
The problem is that $GLOBALS['TYPO3_CONF_VARS']['SYS']['defaultCategorizedTables'] isn't set (or an empty value) so that CategoryRegistry tries to add a category to an empty table name.
In 6.2 this defaults to 'pages,tt_content'
- Status changed from Accepted to Under Review
After a fresh installation of 6.1.1 I had the same problem. Setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['defaultCategorizedTables'] in Install Tool to 'pages,tt_content' helped me. Thx.
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Target version changed from 6.1.1 to next-patchlevel
- Status changed from Resolved to Closed
Also available in: Atom
PDF