On 08.05.2006, at 22:28 Uhr, Pierce T. Wetter III wrote:
Could it be the like that isn't optimized? I know that
col1 = 'a' or col1 = 'b' is optimized.
Let's see ... [firing up FrontBase Manager]
Ah, new information for this:
- col1 = 'a' or col1 = 'b' --> index is used
- col1 like 'a' or col1 like 'b' --> index is NOT used
- col1 = 'a' or col2 = 'a' --> index is NOT used
So, it is only helpfull with or clauses that go to the same column -
a case I had easily solved with the ERXInQualifier from Wonder. It
doesn't help with the other (more common for my apps) cases.
Hmmm... I actually have a need for that as well. Though in my
case I was going to build my own index, because I need ranking of
search results, etc.
We do use Lucene for this - works very well.
Well that's true enough, though personally over the years I've
gotten cynical about the MySQL/Postgres stuff, and lean more
towards Frontbase/Oracle.
Same for me with MySQL, but we are mostly happy with PostgreSQL. If
it had some easy to use multi master cluster support and some nicer
backup strategy for PITR, it would be a near perfect tool.
Oracle is long ago for me and I remember tons of problems and the
need for expensive consultants and DBAs to solve them. But okay,
things may have changed since the old days ... ;-)
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
