Subject | Re: Too many executions of the same request |
---|---|
Author | jjochoa75 |
Post date | 2005-03-29T14:56:39Z |
--- In firebird-support@yahoogroups.com, "Bogdan" <bogdan@m...>
wrote:
Why
SELECT * FROM my_recusrive_proc
works and
SELECT a,sum(b) FROM my_recusrive_proc group by a?
Why
SELECT * FROM my_recusrive_proc order by a
doesn't work?
May be the answer is *the engine need to execute the query
again and again to make the sort*. But, why?
(If this is the case) Isn't it better to execute the plain-query
and then make the sorts and grouping in memory instead of more
executions?
Same issue with the *WHERE X IN (SELECT ...)* Why the engine need to
execute the SELECT clause every time it is going to evaluate X
instead of compare it with a in-memory internal result set?
probably there is a good reason for this behaviour. I really
appreciate if you can explain it to me.
Thank you.
Juan Jose Ochoa
wrote:
> You've reached the limit for recursive callsWhat's that limit?
>
> Bogdan
>
Why
SELECT * FROM my_recusrive_proc
works and
SELECT a,sum(b) FROM my_recusrive_proc group by a?
Why
SELECT * FROM my_recusrive_proc order by a
doesn't work?
May be the answer is *the engine need to execute the query
again and again to make the sort*. But, why?
(If this is the case) Isn't it better to execute the plain-query
and then make the sorts and grouping in memory instead of more
executions?
Same issue with the *WHERE X IN (SELECT ...)* Why the engine need to
execute the SELECT clause every time it is going to evaluate X
instead of compare it with a in-memory internal result set?
probably there is a good reason for this behaviour. I really
appreciate if you can explain it to me.
Thank you.
Juan Jose Ochoa