Subject | Re: error: key size too big for index |
---|---|
Author | vsvadlenka |
Post date | 2002-08-15T07:53:18Z |
--- In ib-support@y..., "svein_erling" <svein.erling.tysvaer@k...>
wrote:
fields. Form performance point of view, are three separate indexes
slower or is it the same as compound index? (Program is ported from
MS Access, so rules for using indexes maybe different).
Thank you for advise.
Regards Vlada
If this leads to many duplicate entries it is sometimes
wrote:
> Hi Vladislav and welcome (I cannot remember to have seen anymessage
> from you before)!compound
>
> First, I thought the maximum index length limit for non-english
> character sets was close to 80 (240/3) and not 60 characters, but I
> may be mixing things.
>
> You could use separate indexes for each field rather than a
> index.I need quickly find out, if there is record matching all three
fields. Form performance point of view, are three separate indexes
slower or is it the same as compound index? (Program is ported from
MS Access, so rules for using indexes maybe different).
Thank you for advise.
Regards Vlada
If this leads to many duplicate entries it is sometimes
> benefitial to add the primary key to the end of such an index (Ipopulated
> expect that you have a primary key consisting of an integer
> through the use of a generator - if not, start making it a habit).ODBC
>
> HTH,
> Set
> -collating myself to a decent character
>
> > I need collation on columns, because I access database through
> > driver and without collating sorting is bad.
> >
> > There is some internal limit on index key soze, about 60 char if
> > collating is used and it is too small, (about 255 chars without
> > collating).
> >
> > Is there any workaround?