StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2920914
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-05-27T12:10:26.860
FavoriteCount
0
LastActivityDate
2010-05-27T12:10:26.860
LastEditDate
LastEditorUserId
0
OwnerUserId
231216
ParentId
2912925
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Thanks for everyone's help so far. A bit more research led me to the NHibernate Burrow project. From the project FAQ (<a href="http://nhforge.org/wikis/burrow/faq.aspx" rel="nofollow noreferrer">http://nhforge.org/wikis/burrow/faq.aspx</a>): Burrow is a light weight middleware developed to support .Net applications using NHibernate (maybe also referred as NH in this article) as ORM framework. Using Asp.net with NHibernate could be a challenge because of the fact that NHibernate is a stateful environment while Asp.net is a stateless framework. Burrow can help solve this conflict by providing advanced and smart session/transaction management and other facilitates. I had to jump through a few hoops to get it working in my project. Since the current release uses an old version of NHibernate I had to download the <a href="http://nhcontrib.svn.sourceforge.net/viewvc/nhcontrib/trunk/src/NHibernate.Burrow/" rel="nofollow noreferrer">latest source</a> from the trunk, open in VS, add references to latest version of NHibernate and recompile (fortunately no errors). I tested NHibernate Burrow in a number of ways. 1) Continue injecting ISession into my repositories To do this, I had to add references to NHibernate, NHibernate.Burrow and NHibernate.Burrow.WebUtil to my MVC project. In web.config I had to set up Burrow (see <a href="http://nhforge.org/wikis/burrow/get-started.aspx" rel="nofollow noreferrer">http://nhforge.org/wikis/burrow/get-started.aspx</a>) and then in my StructureMap registry add the following: <pre><code> For<ISession>() .TheDefault.Is .ConstructedBy(x => new NHibernate.Burrow.BurrowFramework().GetSession()); </code></pre> I like this approach as it means my repositories (or controllers) are not coupled with Burrow. I don't really like the fact that I have to reference these three assemblies in my web project but at least I lose the code for managing the session - this is all handled by Burrow. 2) The second approach would be to set ISession in my repository constructors like so: <pre><code> public ProductRepository() : this(new BurrowFramework().GetSession()) { } public ProductRepository(ISession session) { _session = session; } </code></pre> I can still override ISession making my repositories testable. I then have a direct dependency on Burrow but perhaps this isn't such a bad thing? On the plus side, the only assembly I need to reference from my web project is NHibernate.Burrow.WebUtils. Interested to see which of the two people would go for and why.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow can I implement NHibernate session per request without a dependency on NHibernate?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBen Foster
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. This table or related slice is empty.
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.