Bug #15587
closed
SQL-Error while updating to 4beta2 (create table sys_refindex)
0%
Description
Install Tool can´t create Table sys_refindex while updating in 4beta2 caused by an SQL Error:
CREATE TABLE sys_refindex (
hash varchar(32) default '',
tablename varchar(40) default '',
recuid int(11) default '0',
field varchar(40) default '',
flexpointer tinytext,
softref_key varchar(30) default '',
softref_id varchar(40) default '',
sorting int(11) default '0',
ref_table varchar(40) default '',
ref_uid int(11) default '0',
ref_string varchar(40) default '',
PRIMARY KEY (hash),
KEY lookup_rec (tablename,recuid),
KEY lookup_uid (ref_table,ref_uid),
KEY lookup_string (ref_table,ref_string)
);
mySQL Version 3.23.52
#1171 - All parts of a PRIMARY KEY must be NOT NULL; If you need NULL in a key, use UNIQUE instead
(issue imported from #M2511)
Updated by Harald Klotzberg almost 19 years ago
4beta1 has NOT NULL behind each statement and this of course works:
CREATE TABLE sys_refindex(
hash varchar( 32 ) DEFAULT '' NOT NULL ,
tablename varchar( 40 ) DEFAULT '' NOT NULL ,
recuid int( 11 ) DEFAULT '0' NOT NULL ,
field varchar( 40 ) DEFAULT '' NOT NULL ,
flexpointer tinytext NOT NULL ,
softref_key varchar( 30 ) DEFAULT '' NOT NULL ,
softref_id varchar( 40 ) DEFAULT '' NOT NULL ,
sorting int( 11 ) DEFAULT '0' NOT NULL ,
ref_table varchar( 40 ) DEFAULT '' NOT NULL ,
ref_uid int( 11 ) DEFAULT '0' NOT NULL ,
ref_string varchar( 40 ) DEFAULT '' NOT NULL ,
PRIMARY KEY ( hash ) ,
KEY lookup_rec( tablename, recuid ) ,
KEY lookup_uid( ref_table, ref_uid ) ,
KEY lookup_string( ref_table, ref_string )
)
Updated by Sebastian Kurfuerst almost 19 years ago
Hi,
I think this was broken by one of your patches. Could you have a look?
Thanks for your great work,
Sebastian
Updated by Ingmar Schlecht over 18 years ago
Steffen Sach hat auf der deutschen mailingliste geschrieben:
wenn ich unter Typo3 RC2 eine neue Seite anlegen möchte, dann erhalte ich
folgenden Error:
2: SQL error: 'Column 'TSconfig' cannot be null' (pages:NEW442902c1e9316)Jemand ne Ahnung, woran das liegen könnte? Hab ich etwas vergessen
einzustellen?
Und kurz darauf:
Wenn ich die Extension "dbal" entferne, kommt der Error nicht mehr.
cheers
Ingmar