I'm sorry, but building a database around a framework is flat out wrong. On so many levels. There are two basic options when designing a database for a web application:
1) Design your schema from the perspective of the data. 2) Focus on the model, and let your ORM (Hibernate, Transfer. Reactor, etc.) handle the schema design. Obviously I am over simplifying things here, but the database is the database. It is not part of the MVC architecture. "M" is Model. "V" is View. "C" is Controller. MVC doesn't give a rat's about the database. Hell, MVC doesn't even require a database! The bottom line is that MVC is about the separation of concerns. (Google "separation of concerns".) For that very reason, you should never consider the database when choosing whether or not to use an MVC architecture for the application. Am I saying that the database schema is unimportant and should not be considered? Hell no. I am simply saying that the database is the database, and the MVC architecture is the MVC architecture. They have nothing to do with one another. So, I again suggest that you ask questions that are specific. Your initial question has been fully answered. :-) Sent from my Samsung Galaxy SII On Jul 28, 2012 6:38 AM, "John M Bliss" <bliss.j...@gmail.com> wrote: > > Perhaps it'd help you to check out a framework that "does MVC" and see how > the tables/columns are setup in that DB...? > > For example: > http://cfwheels.org/docs/1-1/chapter/beginner-tutorial-hello-database > > > On Sat, Jul 28, 2012 at 4:54 AM, Andrew Scott <andr...@andyscott.id.au > >wrote: > > > > > Well I am not sure what your looking at achieving either, the question > you > > posed was answered correctly. > > > > The thing that you need to take into consideration, that everything you > do > > whether it is MVC or not has nothing to do with the design of a database. > > The reason behind this is that something like a database is and should be > > considered a different tier to your application design. > > > > So if you are after something more specific, the answer given is exactly > > that, what exactly are you trying to achieve in your design? > > > > -- > > Regards, > > Andrew Scott > > WebSite: http://www.andyscott.id.au/ > > Google+: http://plus.google.com/113032480415921517411< > > http://plus.google.com/108193156965451149543> > > > > > > > > On Sat, Jul 28, 2012 at 5:52 PM, Don <danfar...@hotmail.com> wrote: > > > > > > > > Sounds to me like you didn't understand the question! > > > > > > >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 > > > > > > > > > > > > > > > > > > > >> > > > >> 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:352008 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
