Subject | Firebird 2.0.1 fails with index creation where 2.0 succeeds |
---|---|
Author | vincent.schmid |
Post date | 2007-04-22T00:26:26Z |
Hello,
I'm using a database with a page size of 4K.
The default charset is UTF8
I create the following table :
CREATE TABLE Clients (ID BIGINT NOT NULL, Name VARCHAR(255) NOT NULL,
PRIMARY KEY (ID))
And then I create an idex :
CREATE UNIQUE INDEX IDX_CLIENTS ON Clients (Name)
This works with Firebird 2.0, but fails with 2.0.1 with the message :
"key size exceeds implementation restriction for index IDX_CLIENTS"
The maximum I can use with FB 2.0.1 is 253 for the size of the "Name"
field.
If I create this table with a 8K page size it works again with
Firebird 2.0.1.
Why do we "lose" two characters from FB 2.0 to FB 2.0.1 ? This is not
a problem as I will use 8K Pages from now on, but it still seems weired.
Best regards,
Vincent Schmid
I'm using a database with a page size of 4K.
The default charset is UTF8
I create the following table :
CREATE TABLE Clients (ID BIGINT NOT NULL, Name VARCHAR(255) NOT NULL,
PRIMARY KEY (ID))
And then I create an idex :
CREATE UNIQUE INDEX IDX_CLIENTS ON Clients (Name)
This works with Firebird 2.0, but fails with 2.0.1 with the message :
"key size exceeds implementation restriction for index IDX_CLIENTS"
The maximum I can use with FB 2.0.1 is 253 for the size of the "Name"
field.
If I create this table with a 8K page size it works again with
Firebird 2.0.1.
Why do we "lose" two characters from FB 2.0 to FB 2.0.1 ? This is not
a problem as I will use 8K Pages from now on, but it still seems weired.
Best regards,
Vincent Schmid