On Dec 11, 2007 10:25 PM, Mr-Yellow <[EMAIL PROTECTED]> wrote: > > As for writting CakePHP.... I think that would be better left to those > with an eye on the direction and conventions of the project, those who > should realise this is a feature at the basis of being able to use > CakePHP for DB access. Without full and proper database support, raw > SQL is much faster and easier to use, so what if a few servers might > not like a query here or there. Kind of defeats the purpose of RAD > when takes 10x as long to write a query in Cake as it does in SQL, > then said query runs twice as slow do to being broken into 50 parts > and looping through everything to construct arrays.
Ben, you are absolutely write that there are some situations where doing the SQL yourself is faster than what CakePHP can produce. However, the point is not to create perfectly tuned SQL. The point is to build the application fast by using all sorts of helpers. Luckily you're not locked in to using Cake's DB model if you really don't want to, you just lose all those nicely formatted result sets. -- Chris Hartjes My motto for 2007: "Just build it, damnit!" @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
