Re: optimization/indexing
Re: optimization/indexing
- Subject: Re: optimization/indexing
- From: Mike Schrag <email@hidden>
- Date: Thu, 18 Dec 2008 23:22:30 -0500
Does WinAnalysis.comboTeamID have an index? I'd guess that it does
and that the index is corrupt. Or that is one VERY large table and
there is no index. If you can get FrontBase to use an IN instead of
ORs that will also make it faster, but you have some kind of hunka
burning serious SQL problem happening there.
I seem to recall that FB optimizes these or's into an in query if you
look at the execution plan, so I believe you only really save on
parse time for that. Wonder does have an ERXInOrQualifier or
something like that that turns ors into in-sets given a set of
criteria. This used to be the default, but we took it back out after
a couple people had problems (I think maybe 5.4-related, but it's been
a while). I actually prefer using it, though, as it makes much more
sane looking sql.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden