On Aug 2, 2007, at 9:23 AM, walterbyrd wrote:
> > I'm framework shopping. I need something for significant relational > database work, and probably some CRUD. > > I tried Django, made some progress, and might go back. The things that > I didn't care for with Django: > > 1) Hosting requirements. Few hosts really work well with Django. If > you doing work for a client who uses shared hosting - forget it. Cake should be pretty easy to lay down on a hosting account. PHP 4 and 5 support. That's not too hard to find. > 2) Configuration and administrative overhead seems borderline > excessive. You have to sync you urls file to your views. You have to > create a configuration file for every application. You have to create > a database model file, and and edit that file, and sync that file with > your database everytime you make a change to your db. Everytime you > make any change to the code, you have to restart your web-server, or > touch all your files depending on whether you mod_python or fastcgi. Most config in CakePHP is done by convention. Table information is also cached and stored - you never have to provide column details. Yuck. You do have to point it to a host, but that's about it. > I also tried CodeIgitor. I made much more progress with a few hours of > CodeIgnitor, than I made with weeks of Django. But, I'm not sure about > how well CodeIgnitor will work with CRUD and/or relational database > work. CI is kinda cake-like, but I'm not sure why you'd go with it since CakePHP's community is larger and ever-so much better looking. I also hear CI has forked in the recent past (Blue Flame?). -- John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
