It's quite recommended to have separate models for Data Access, Domain Logic and User Interface if the business domain is complex enough to require such.
You can read more about it here http://www.infoq.com/minibooks/domain-driven-design-quickly or in Eric Evan's Domain Driven Design. -Markus 2009/3/27 Daniel Soto <[email protected]> > > Hello. > > Sorry for the newbie question. > > According to MVC pattern, the model are all business objects in a MVC > application. In many examples that I see, the model matches exactly > with the database model (1:1 relation). > > Can have other business objects in the model, without break the MVC > pattern? > > For example: A database model have two tables, Product and Customers, > and they generates two classes with same name in the model, but it's > possible that in the model have a third class named Sales, which do > some special process over Product and Customers classes, but not > necessarily matches with some table named "Sales" in the database. > > It's possible this? > > Thanks! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
