StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
370092
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2008-12-15T23:46:15.550
FavoriteCount
0
LastActivityDate
2008-12-15T23:46:15.550
LastEditDate
LastEditorUserId
0
OwnerUserId
1136215
ParentId
369978
PostTypeId
2
Score
15
ViewCount
0
LastEditorDisplayName
text
Body
I found ActiveRecord to be a good piece of kit, and very suitable for the small/medium projects I've used it for. Like Rails, it makes many important decisions for you, which has the effect of keeping you focused you on the meat of the problem. In my opinion pro's and cons are: Pros <ul> <li>Lets you focus on problem in hand, because many decisions are made for you.</li> <li>Includes mature, very usable infrastructure classes (Repository, Validations etc)</li> <li>Writing AR attributes are faster than writing XML or NHibernate.Mapping.Attributes IMHO.</li> <li>Good documentation and community support</li> <li>It's fairly easy to use other NHibernate features with it.</li> <li>A safe start. You have a get-out clause. You can slowly back into a bespoke NHibernate solution if you hit walls with AR. </li> <li>Great for domain-first development (generating the db).</li> <li>You might also want to look up the benefits and drawbacks of the <a href="http://martinfowler.com/eaaCatalog/activeRecord.html" rel="noreferrer">ActiveRecord pattern</a></li> </ul> Cons <ul> <li>You can't pretend NHibernate isn't there - you still need to learn it.</li> <li>Might not be so productive if you already have a legacy database to work with.</li> <li>Not transparent persistence.</li> <li>In-built mappings are comprehensive, but for some projects you might need to revert to NHibernate mappings in places. I haven't had this problem, but just a thought. </li> </ul> In general, I really like ActiveRecord and it's always been a time saver, mainly because I seem to happily accept the decisions and tools baked into the library, and subsequently spend more time focusing on the problem in hand. I'd give it a try on a few projects and see what you think.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhats the pros and cons of using Castle Active Record vs Straight NHibernate?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UStobinharris
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.