On 29 mayo, 10:46, "R. Rajesh Jeba Anbiah"
<[EMAIL PROTECTED]> wrote:
> On May 29, 12:32 pm, AD7six <[EMAIL PROTECTED]> wrote:
>
> > On 29 mayo, 09:10, "R. Rajesh Jeba Anbiah"
> <snip>
> > > FWIW, I do not question the need to run the queries. But, my
> > > question is that why it can't be optimized. With the better join
> > > query, we can have a single query that serves the purpose, instead of
> > > about 60 queries.
>
> > Consider what would happen if you had some of your blogs are
> > associated with a large number (relative to your limit) of tags/
> > categories/comments. You can't apply a limit to the number of
> > associated items, but also you can't even know how many results from
> > your primary table will be returned.
>
> Thanks for your explanation. But, it's getting crazy; 50-100 queries
> (unbind isn't helpful as I need the relevant data) often force me to
> handcode the queries.
Does this ticket apply https://trac.cakephp.org/ticket/2448 ? If so
perhaps at some point your queries will be reduced.
In the absence of any details, if each query gives you info that isn't
already duplicated and you _need_ it, I think that's simply the way it
(has to?) works.
hth,
AD
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
