In MVC I am first an M guy .... Do not get me wrong, cake is great and I can achieve whatever is needed. Concerning the M, the big missing bit, and the Noobs (as I have been) always get stuck with this :
Why does it require more work to code a simple condition in an hasMany / HABTM relation than in a belongsTo or hasOne ? To me this is the real "missing bit" for cake. Because the hasMany does not uses JOIN query but several queries, you are somehow twisting around using "bindModel/unbindModel", also with the great containable/ bindable behavior. Of course you can bindModel with a constraint on the targeted hasMany, but still you will have to filter out. Again do not get me wrong, it's possible to do it with cake, but maybe not as "simple" as out of the box. I will not pretend I can make it, it is complex and certainly have a lot of side effects and I am sure that the cake's gurus knows about this better than any one else. Was just my though about "what I really wish in cake that is missing" => make a query just as easy in hasMany and HABTM as it's easy with belongsTo .. and probably get the best Mvc framework :-) Cheers, and congratulation for the 1.2 RC1 Franck --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
