[eluser]TheActionCombo[/eluser]
Coming from CakePHP, I'm used to there being a set way to do everything. For example, every database table has a corresponding model. From what I've read in the user guide, this is not necessarily true in CI. It seems as if the system is so flexible that your application can just have a single model that handles every database table (or a single controller for all business logic, etc) or even no model at all. Obviously, the downside of this flexibility is the potential for bad MVC practice.
So, how do you guys design your applications in this respect? The reason I am asking is because I am going to build a blog that features 3 tables: Posts, Comments, and Tags. CakePHP would have me create a post, comment, and tag model, as well as a posts, comments, and tags controller. In CI, would it be best practice to do the same? Or I could I, for example, just have a single "blog" controller and model that handles all 3 of these? At first glance, handling posts, comments, and tags would not be outside the scope of a "blog" controller or model. How would you design this app?
Thanks.