Subject | Err -663 "Too many keys defined for index" while trying to create single field index on table with 4 records.. |
---|---|
Author | Brenden Walker |
Post date | 2005-10-04T18:15:10Z |
I'm not sure what gives, somehow we've got a database in a state where
we cannot re-create an index on a table. If I drop and re-add the table
everything works fine. I tried searching the bug tracker on source
forge with no luck.
I can remove all the data, still can't create the index. Just for
clarity's sake, here's the table DDL:
CREATE TABLE REP_PARSEDLOGS (
CHANGEID INTEGER,
LOGDATE DATE,
TABLENAME CHAR(32),
CLASSID SMALLINT,
CHANGETYPE CHAR(1),
FIELDNAMES VARCHAR(1024),
FIELDVALUES VARCHAR(8192)
);
And here's the index I'm trying to create: create unique index
primary_parsedlogs on rep_parsedlogs(ChangeID)
I know this is proper syntax, and works fine normally.. It just there's
something very specific wrong with this database and I'm trying to
figure out how/why it got that way.
Anyone ever heard of anything like this? This is a FB 1.5.2 database.
we cannot re-create an index on a table. If I drop and re-add the table
everything works fine. I tried searching the bug tracker on source
forge with no luck.
I can remove all the data, still can't create the index. Just for
clarity's sake, here's the table DDL:
CREATE TABLE REP_PARSEDLOGS (
CHANGEID INTEGER,
LOGDATE DATE,
TABLENAME CHAR(32),
CLASSID SMALLINT,
CHANGETYPE CHAR(1),
FIELDNAMES VARCHAR(1024),
FIELDVALUES VARCHAR(8192)
);
And here's the index I'm trying to create: create unique index
primary_parsedlogs on rep_parsedlogs(ChangeID)
I know this is proper syntax, and works fine normally.. It just there's
something very specific wrong with this database and I'm trying to
figure out how/why it got that way.
Anyone ever heard of anything like this? This is a FB 1.5.2 database.