The MVC design pattern is pretty much orthogonal to the design of the database. In fact one of the goals of MVC is to hide the particulars of your model from the rest of your application. Your data could come from a number of different sources (a database, XML, an RSS feed, web service) and it would not matter to the rest of your app. Ideally, one could swap out your source of data from a database or an ORM to a web service and the rest of your application would be none the wiser.
BTW I took the time to Google "best practices database structure MVC" and nobody seems to have addressed the topic. So yeah, what Matt said. https://www.google.com/search?num=100&hl=en&safe=off&q=best+practices++database+structure+MVC+&oq=best+practices++database+structure+MVC+&gs_l=serp.3...25075.36379.0.36670.13.13.0.0.0.0.124.1410.0j13.13.0.cqn%2Ccconf%3D1-0%2Cmin_length%3D2%2Crate_low%3D0-025%2Crate_high%3D0-025%2Csecond_pass%3Dfalse%2Cnum_suggestions%3D2%2Cignore_bad_origquery%3Dtrue..0.0...1c.yZGPO9vdhJg HTH G! On Fri, Jul 27, 2012 at 9:29 PM, Matt Quackenbush <quackfu...@gmail.com>wrote: > > Speaking from a purist perspective, the database has nothing to do with > MVC. Perhaps you should ask more specific questions so folks can have an > idea of what you're really after? > > HTH > > > On Fri, Jul 27, 2012 at 8:04 PM, Don <danfar...@hotmail.com> wrote: > > > > > What are some best practices in structuring the website database to > > accomodate good integration with an MVC model? > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:352012 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
