It depends. If you are a pseudo-DDD type, go along with naked NH, Repositories, pretended persistence ignorance and virtual properties and default constructors for non-ignorable persistence needs.
If you are accepting that there is a database, prefer having mappings with your code and value the convenience of simply calling Entity.Save(), AR is for you. -Markus 2009/5/26 Cesar Sanz <[email protected]>: > > So, > > What is more recommended? > > ----- Original Message ----- > From: "Gabe Anzelini" <[email protected]> > To: <[email protected]> > Sent: Tuesday, May 26, 2009 12:02 PM > Subject: Re: Is AR just for prototyping > > >> >> some people just don't like to have their mapping logic spread >> throughout their objects, this is prob more important for larger >> projects than i have worked on, but AR seems to work fine for me. also >> if i need to change mapping i often need to change the properties as >> well, AR keeps these together which is nice. >> >> On Tue, May 26, 2009 at 10:10 AM, [email protected] >> <[email protected]> wrote: >>> >>> Hello community, >>> >>> I have a question about ActiveRecord, I've heard that the only purpose >>> of AR is for Rapid Developent, just >>> for prototyping, then once you have created your model, you must to >>> switch to pure nhibernate.. >>> >>> Why is that? Is not suitable AR for a production environment? >>> >>> Slts. >>> > >>> >> >> > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
