I agree with James, there are some queries you'd always want in SQL. But Alessio, are you familiar with the Containable (formerly Bindable) behaviour? It's a nicer way to bind your models, including particular fields.
On Jul 2, 7:41 pm, James K <[EMAIL PROTECTED]> wrote: > The only disadvantage to this method is that you lose some of the > "automagic" benefits of having cake pull and model the data. If you're > pulling the data to populate a form, for instance, you'd have to set > the values manually since the FormHelper won't understand how to > interpret your custom result set. > > That said, there is significant overhead with using Cake's find > functions and if you find it easier and/or more convenient to write > your own queries, I say go for it. In fact, any sort of complex query > should be hand-written IMO for the sake of performance. Cake doesn't > try very hard to be efficient with the queries it generates beyond > simple joins. > > On Jul 2, 12:37 pm, Alessio <[EMAIL PROTECTED]> wrote: > > > i am trying to use custom query for retrieving the data. > > I noticed that using query ...I get the array filled in corretly and I > > can choose very easily only the fields that i need... > > And I can fill my data vars without removing or adding bind or unbind > > model... > > What about this method of getting data? > > I use this because I need to load data always in my site...and I > > noticed a very good performance.... > > using model->query...()... with the join written by myself... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
