Subject | Re: [firebird-support] Re: unsuccessful metadata update, key size too big for index |
---|---|
Author | Martijn Tonies |
Post date | 2004-02-05T13:14:57Z |
Hi,
of a single constraint.
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
> > Well, that explains a lot. This characterset uses 3 bytes/character.Nope, same limit.
> > So you're max VARCHAR length - as a single column in an unique
> > constraint - would be around 80, 82 or so. It's limited to 255
> > of 250 bytes (cannot remember exactly).
>
> Hmm. So is a CHAR instead of a VARCHAR better?
> > > > I have no idea why this should help.Ah no, it's not a matter of how many constraints, but the total size
> > >
> > > I figured that each table would only have two constraints max.
> >
> > Oh no, you can have more :-)
> >
> > Each constraint uses its own auto-created index.
>
> Ah, no, I meant: if I break up this table into multiple tables, each
> would only *require* two constrainst max, and that that could maybe
> fall within the 255 bytes limit (as inconvenient this setup may be).
of a single constraint.
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com