Subject | Re: [firebird-support] Table Design |
---|---|
Author | Daniel Rail |
Post date | 2007-01-23T19:14:32Z |
Hi,
At January 23, 2007, 1:57 PM, Svein Erling Tysvaer wrote:
based on UPPER(fieldname)). So, the creation and maintenance of a
second field for an uppercase or lowercase equivalent is no more
needed.
--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Consultants Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)
At January 23, 2007, 1:57 PM, Svein Erling Tysvaer wrote:
> Hmm, if you say, have 1.3 million records, that would mean an average ofDon't forget that FB 2.0 also permits expression indices(i.e.: an index
> 50000 records for every query - a bit too much for my liking. I'd
> recommend that you rather let the user type as much as he wants, and
> only when he says 'search', execute the query.
> As for index, I'd simply recommend a normal ascending index on an upper-
> or lowercased version of the name (having one field with mixed-case,
> and another field with the uppercase equivalent populated through
> triggers, is a good option). If the field is too long to index, have a
> copy containing the beginning of the name.
based on UPPER(fieldname)). So, the creation and maintenance of a
second field for an uppercase or lowercase equivalent is no more
needed.
--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Consultants Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)