Subject | Re: Indices and views |
---|---|
Author | csswa |
Post date | 2002-07-12T02:05:44Z |
--- In ib-support@y..., Christian Gütter <cguetter@p...> wrote:
famous 'brain fade' that the planner succumbs to now and then. Or it
may be a case of expecting the planner to make a choice that seems
perfectly logical to us humans, but...
Anyway, try adding a dummy WHERE clause to your view to force the
engine to engage available indexes, e.g. use the index for NUMMER
thusly:
WHERE NUMMER = NUMMER
I think this was the fudge to use in this case. Don't know if that's
the best format to use, though. Others will correct me if not.
Regards,
Andrew Ferguson
-- Andrew is not controlled by monkeys. He's controlled by *a* monkey.
> This is quite strange, because the view V_BESCHR_PROJEKTE isYes, possibly too simple for the engine. This may be a case of the
> a simple view for T_Projekte which is used in the first query.
famous 'brain fade' that the planner succumbs to now and then. Or it
may be a case of expecting the planner to make a choice that seems
perfectly logical to us humans, but...
Anyway, try adding a dummy WHERE clause to your view to force the
engine to engage available indexes, e.g. use the index for NUMMER
thusly:
WHERE NUMMER = NUMMER
I think this was the fudge to use in this case. Don't know if that's
the best format to use, though. Others will correct me if not.
Regards,
Andrew Ferguson
-- Andrew is not controlled by monkeys. He's controlled by *a* monkey.