Initdb-bug


#1

I have a problem while trying to install rt2 (1.3.46). I’m using mysql 2.22. First I got this message:

Creating database schema.
DBD::mysql::st execute failed: Column ‘Name’ is used with UNIQUE or INDEX but is not defined as NOT NULL at tools/initdb line 71, chunk 2.
Problem with statement:
CREATE TABLE Groups (
id INTEGER NOT NULL AUTO_INCREMENT,
Name varchar(16) NULL ,
Description varchar(64) NULL ,
Pseudo integer NOT NULL DEFAULT 0 ,
PRIMARY KEY (id),
UNIQUE (Name)
)

Column ‘Name’ is used with UNIQUE or INDEX but is not defined as NOT NULL at tools/initdb line 73, chunk 2.
Database handle destroyed without explicit disconnect, chunk 2.
make: *** [database] Error 255

Then I fixed this by editing etc/Schema.pm (by putting NOT before the various NULLs (only the ones that are unique)). When I tried to install it again I got the following error:

Creating database schema.
DBD::mysql::st execute failed: Specified key was too long. Max key length is 256 at tools/initdb line 71, chunk 2.
Problem with statement:
CREATE TABLE Links (
id INTEGER NOT NULL AUTO_INCREMENT,
Base varchar(240) NOT NULL ,
Target varchar(240) NOT NULL ,
Type varchar(20) NOT NULL ,
LocalTarget integer NULL ,
LocalBase integer NULL ,
LastUpdatedBy integer NULL ,
LastUpdated DATETIME NULL ,
Creator integer NULL ,
Created DATETIME NULL ,
PRIMARY KEY (id),
UNIQUE (Base, Target, Type)
)

Specified key was too long. Max key length is 256 at tools/initdb line 73, chunk 2.
Database handle destroyed without explicit disconnect, chunk 2.
make: *** [database] Error 255

I’m not sure what this error means, or how to fix it.

Regards,
Marius Olsthoorn


#2

Not a bug in initdb. As the readme says, you need to be running mysql 3.23
or newer.On Mon, Feb 26, 2001 at 03:00:06PM +0100, M. Olsthoorn wrote:

I have a problem while trying to install rt2 (1.3.46). I’m using mysql 2.22. First I got this message:


Creating database schema.
DBD::mysql::st execute failed: Column ‘Name’ is used with UNIQUE or INDEX but is not defined as NOT NULL at tools/initdb line 71, chunk 2.
Problem with statement:
CREATE TABLE Groups (
id INTEGER NOT NULL AUTO_INCREMENT,
Name varchar(16) NULL ,
Description varchar(64) NULL ,
Pseudo integer NOT NULL DEFAULT 0 ,
PRIMARY KEY (id),
UNIQUE (Name)
)

Column ‘Name’ is used with UNIQUE or INDEX but is not defined as NOT NULL at tools/initdb line 73, chunk 2.
Database handle destroyed without explicit disconnect, chunk 2.
make: *** [database] Error 255


Then I fixed this by editing etc/Schema.pm (by putting NOT before the various NULLs (only the ones that are unique)). When I tried to install it again I got the following error:


Creating database schema.
DBD::mysql::st execute failed: Specified key was too long. Max key length is 256 at tools/initdb line 71, chunk 2.
Problem with statement:
CREATE TABLE Links (
id INTEGER NOT NULL AUTO_INCREMENT,
Base varchar(240) NOT NULL ,
Target varchar(240) NOT NULL ,
Type varchar(20) NOT NULL ,
LocalTarget integer NULL ,
LocalBase integer NULL ,
LastUpdatedBy integer NULL ,
LastUpdated DATETIME NULL ,
Creator integer NULL ,
Created DATETIME NULL ,
PRIMARY KEY (id),
UNIQUE (Base, Target, Type)
)

Specified key was too long. Max key length is 256 at tools/initdb line 73, chunk 2.
Database handle destroyed without explicit disconnect, chunk 2.
make: *** [database] Error 255


I’m not sure what this error means, or how to fix it.

Regards,
Marius Olsthoorn


Rt-devel mailing list
Rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

“It’s buried in the desert, got sand in it, melts Nazis. You know,
the Ark of the Covenant” – siva