Project

General

Profile

Actions

Bug #15888

closed

Database analyzer fails creating some tables with MySQL 3.23

Added by Alban Cousinie over 18 years ago. Updated over 18 years ago.

Status:
Closed
Priority:
Should have
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2006-03-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.0
PHP Version:
4
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The install tool fails to create the tables listed below with MySQL 3.23 because the primary keys definitions in the tables below do not state NOT NULL.

Thus when using the database analyzer update feature, an invisible SQL error is raised stating a PRIMARY key must be NOT NULL and the table creation fails. No error message is stated, but there are 2 symptoms to this problem :
- the database analyser update page keeps saying some tables are missing although you just attempted to create them and it did not report any failure.
- Once you attempt to login with the login page of the backend, a "Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in typo3_src_path/t3lib/class.t3lib_db.php on line 796" error is raised followed by many "Cannot modify header information " consequent warnings. As a result, and because of the missing tables, you are unable to login into the backend.

This affected the following table in my installation :
be_sessions
cache_hash
cache_imagesizes
sys_preview
sys_refindex
cache_pagesection
cache_typo3temp_log
cache_md5params
fe_session_data
fe_sessions

I solved the problem by manually creating the tables into MySQL using the table definitions outpouted in the "COMPARE" page of the database analyzer. Thus when seizing manually a table like :

CREATE TABLE cache_pagesection (
page_id int(11) unsigned default '0',
mpvar_hash int(11) unsigned default '0',
content blob,
tstamp int(11) unsigned default '0',
PRIMARY KEY (page_id,mpvar_hash)
);

you should write :

CREATE TABLE cache_pagesection (
page_id int(11) unsigned default '0' NOT NULL,
mpvar_hash int(11) unsigned default '0' NOT NULL,
content blob,
tstamp int(11) unsigned default '0',
PRIMARY KEY (page_id,mpvar_hash)
);

(issue imported from #M2969)


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #15772: "NOT NULL" removed from SQL gives error with MySQL 3.23.52ClosedMichael Stucki2006-03-06

Actions

No data to display

Actions

Also available in: Atom PDF