> -----Original Message-----
> From: Bruno Mattarollo [mailto:bruno@...]
> Sent: Miércoles 16 de Agosto de 2000 11:07
>
> create table t_UserGroupActionRoleMap (
> iGroupID integer not null references t_UserGroups(iGroupID),
> sRole varchar(200) not null,

[...]

> primary key (iGroupID, sRole)
> );

[...]

> unsuccessful metadata update
> key size too big for index RDB$PRIMARY115
>
> Is there a limit on the size of the columns that made part of the
> primary key?

Certainly there's a limit. I hope I succeded in introducing that
information in the final IB6 docs that Inprise still doesn't release. The
limit is 252 bytes. InterBase (TM) creates automatically an index for PK, FK
and UNIQUE declarations. That index is affected by the charset and the
collation. I see that you aren't using any specific character set, so you
have the best chance to get the maximum key length allowed.
However, Murphy said clearly IT WON'T WORK and InterBase® honors Murphy.
:-) I don't know for sure how IB manages internally the concatenation of an
integer and a varchar to make up an index, but in your case, your varchar
can be at most 192 characters wide, not 200.

> Thanks in advance... ah! and excuse my question but I have looked
> through all the documentation and couldn't find any reference for the
> key size ...

Hopefully it will be present in the non-beta docs. I guess you have to send
10 million dollars to Dale Fuller for causing an immediate release.

C.