Project

General

Profile

Actions

Bug #48381

closed

after git pull db compare -> CREATE TABLE ( ( categories int(11) NOT NULL default '0' );

Added by Matthias Eberlein almost 11 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Must have
Category:
-
Target version:
Start date:
2013-05-19
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
Sprint Focus:

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


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Task #38972: Improve method makeCategorizable to be used everywhereClosedFabien Udriot2012-07-16

Actions
Has duplicate TYPO3 Core - Bug #48527: Database error after update to 6.1.1Closed2013-05-25

Actions
Actions #1

Updated by Matthias Eberlein almost 11 years ago

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.

Actions #2

Updated by Alexander Opitz almost 11 years ago

I have this issue in 6.1.1-dev but not in 6.2-dev

Actions #3

Updated by Alexander Opitz almost 11 years ago

  • Status changed from New to Accepted
  • Assignee set to Alexander Opitz
Actions #4

Updated by Alexander Opitz almost 11 years ago

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'

Actions #5

Updated by Gerrit Code Review almost 11 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20938

Actions #6

Updated by Marc Bastian Heinrichs almost 11 years ago

Was introduced with #38972

Actions #7

Updated by Björn Jacob almost 11 years ago

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.

Actions #8

Updated by Gerrit Code Review almost 11 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20938

Actions #9

Updated by Gerrit Code Review almost 11 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20938

Actions #10

Updated by Gerrit Code Review almost 11 years ago

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/20938

Actions #11

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #12

Updated by Chris topher almost 11 years ago

  • Target version changed from 6.1.1 to next-patchlevel
Actions #13

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF