Re: Forms performance [need help!]
From: BARRY ROOMBERG <barry.roomberg_at_compudata.com>
Date: Sun, 09 Oct 94 21:17:00 -0400
Message-ID: <89B74FD.03890015A1.uuout_at_compudata.com>
Date: Sun, 09 Oct 94 21:17:00 -0400
Message-ID: <89B74FD.03890015A1.uuout_at_compudata.com>
-> Bottom line, compared to just using the predicate UPPER(DNAME) =
-> 'ACCOUNTING' and presuming you *need* the declarative capability of
-> letting your users query in a case- insensitive way, it's faster.
Ya mean I just spents 3 years keeping upper cased mirror tables for lookup purposes that I didn't NEED?!?!!?!?
I don't know whether to kiss you or kill you.
Thanks.
(I'll be doing some serious recoding now, assuming the tests show equivalent query speeds.)
What is the chance of an optimizer upgrade changing this behaviour?
Now, what can you do for my inverted word index, ie: for every word in a field, extract it into it's own field and track the source id. Received on Mon Oct 10 1994 - 02:17:00 CET