> That's a pretty typical (and kinda sad) answer from someone with no real > sql/ database background, and happy with MySQL, which just recently, > (version 5) realised that Views, stored procedures, triggers, etc are > MANDATORY in any serious database engine.( I use Postgresql exclusively > with Cake, and am increasingly frustrated by the numerous limitations of > cake versus a REAL database)
remember the main-demo of rails or cake is creating a blog and getting some pictures out of flickr. you dont do a backend in rails that serves any views outside the webworld. you do the model in php or ruby because it doesnt have to be independent of this app. = rapid development of web2.0 apps, nothing more. simple. at least, that is the _focus_ on these frameworks IMHO. when you dont need the modelling-features of a framework because it duplicates your fine SQL-code and you only see a need for the VC of the MVC probably switch to CodeIgniter and query your views and execute your procedures and do the validation in the controller. beside that cake sucks because..anyway --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
