Bug #51090: SQL parser does not analyse NOT NULL in extension SQL files - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #51090

closed

SQL parser does not analyse NOT NULL in extension SQL files

Added by Tobias Klepp over 11 years ago. Updated about 7 years ago.

Status:

Closed

Priority:

Should have

Assignee:

Morton Jonuschat

Category:

Install Tool

Target version:

7.4 (Backend)

Start date:

2013-08-15

Due date:

% Done:

Estimated time:

TYPO3 Version:

6.1

PHP Version:

5.3

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

If I start the database analyzer in the install tool, the SQL parser didn't analyse the NULL attribute of the tables.

In ext_tables.sql there are the following example definition:

#
# Table structure for table 'tx_extkey_tablename'
#
CREATE TABLE tx_extkey_tablename (
  uid int(11) NOT NULL auto_increment,
  pid int(11) DEFAULT '0' NOT NULL,
  tstamp int(11) DEFAULT '0' NOT NULL,
  crdate int(11) DEFAULT '0' NOT NULL,
  cruser_id int(11) DEFAULT '0' NOT NULL,
  deleted tinyint(4) DEFAULT '0' NOT NULL,
  hidden tinyint(4) DEFAULT '0' NOT NULL,
  title varchar(150) DEFAULT '' NOT NULL,
  example tinyint(4) DEFAULT '0' NOT NULL,

  PRIMARY KEY (uid),
  KEY parent (pid)
);

In the database the structure looks like this:

#
# Table structure for table 'tx_extkey_tablename'
#
CREATE TABLE tx_extkey_tablename (
  uid int(11) NOT NULL auto_increment,
  pid int(11) DEFAULT '0' NOT NULL,
  tstamp int(11) DEFAULT '0' NOT NULL,
  crdate int(11) DEFAULT '0' NOT NULL,
  cruser_id int(11) DEFAULT '0' NOT NULL,
  deleted tinyint(4) DEFAULT '0' NOT NULL,
  hidden tinyint(4) DEFAULT '0' NOT NULL,
  title varchar(150) DEFAULT '' NOT NULL,
  example tinyint(4) DEFAULT '0',

  PRIMARY KEY (uid),
  KEY parent (pid)
);

The database analyzer say, that everything is ok. Nothing to do. But that's not true.

Related issues 1 (0 open — 1 closed)