I think the point is you *can* achieve what you are after by using var $scaffold;, or not as the case may be.
if all you need is the bog stock "stuff" scaffolding will do....when you decide you need something unique/custom, you can chose to not use scaffolding. Scaffolding will also build your views on the fly. Despite my previous misspeaking, I think scaffold is valid, especially if your schema is changing often in the early stages of development. I don't know that 40 tables automatically translates to 40 different controller...I often use multiple models in a single controller, either by virtue of relationships or because I just want to store something in a table that doesn't need to be directly accessed through its own view/form....though I may have the wrong end of the stick again here.... :S On Fri, Jan 28, 2011 at 11:29 PM, keymaster <[email protected]> wrote: > Generic crud ops in AppController would work fine for 80% of > controllers. > > Controllers which need something unique would override. > > Why would I want to bake a project with 40 tables, and end up with 40 > copies of nearly the same code in 40 different controllers? > > Is it so much harder to type $this->modelClass instead of $this->User? > > -- > Our newest site for the community: CakePHP Video Tutorials > http://tv.cakephp.org > Check out the new CakePHP Questions site http://ask.cakephp.org and help > others with their CakePHP related questions. > > > To unsubscribe from this group, send email to > [email protected]<cake-php%[email protected]>For > more options, visit this group at > http://groups.google.com/group/cake-php > -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php
