Maintains a list of objects affected by a business transaction and coordinates the writing out of changes and the resolution of concurrency problems.
I was asked about a warning from NHProfiler from a colleague to see my opinion on the matter. The warning was: http://hibernatingrhinos.com/products/NHProf/learn/alert/QueriesFromViews “Don’t Query From the View”.
The team had a session lifetime per controller action using AOP (Attribute Filters), but needed to extend this out to be active during the view rendering phase after the controller completed. They did this by instantiating the session in the request filter chain instead of the controller attribute filters. When they did this, they received the NHProfiler warning above.
The collegue was dismissive of the warning, partly because the implementation of the code was innocuous and partly because the warning reasons were not particularly compelling.
There are some serious implications of the pattern that was being followed however, some of which I have covered on this blog in the past (here) and (here).
tldr;
· Sessions can be open as long as you need them to be. You do not need to arbitrarily close them if you know they will be needed again as soon as the next step in the pipeline is reached.
· There are (arguably) valid reasons why the View rendering would be able to access an active session.
· The longer a session is open, the more chance of unexpected behaviour from working with Entities in a connected state. Care should be taken.
Pro1: Simplicity
One benefit from having a session opened and closed automatically using cross-cutting AOP is that your application doesn’t need to care about it. It knows that it will have a session when used, and will commit everything when the scope ends. This is often done as a controller/action filter attribute, or higher in the request pipeline. You don’t need to pass a session around, check if it exists, etc.
Con1: Deferring code to View Rendering adds complexity.
I have argued that having the session active outside the controller makes it more difficult to maintain and debug your code as the session is active during the View render component. The response was that forcing a controller action to pre-load everything the view *might* need and just pushing a dumb model prevents the view from performing optimisation of what it actually loads. I don’t believe that the View rendering should have such an impact on code execution but the point is a valid point of contention.
Con2: Loss of control.
When using AOP to manage the session lifetime you have much less control over the failed state. As the failure occurred outside of the business logic context, you can’t easily use business logic to handle the failure. If the standard policy is to simply direct you to an error page or similar, then this behaviour is completely valid. However if you needed to perform actions based on the failure (such as attempting to resolve optimistic concurrency issues automatically) then you can’t.
Con3: Loss of traceability.
When using a long running session there is no traceability between the persistence and the application logic that made the entity changes. If you experience an unexpected query when the unit of work commits, you can’t immediately identify which code caused this behaviour.
Con4: Unexpected change tracking.
Having a long running (and potentially ‘invisible’) session exposes you to potentially unexpected behaviour due to the session tracking all changes on the underlying entities. If you load an entity from the data access layer, then make some changes for display purposes (perhaps change a Name property from “Jason Leach” to “LEACH, Jason”) before passing that entity to the view, when the unit of work cleanup occurs it will persist that change to the database because all of your changes are being tracked.
A less obvious example is if you had a Parent entity with a list of Children. In a particular controller action you want to get the parent and only a subset of the children. So you might select the parent and all children. Then you may do something like Parent.Children = Parent.Children.Select(x=>childfilter).ToList(). Depending on your configuration this is likely to delete all of the children not matching the filter when the unit of work completes. Oops.
Con3 and 4 are direct side effects of leaving a session open longer. In the Parent->Child example, you would likely only need the session active when you did the initial load of the Parent and Child entities, then close the session and start manipulating the entities. Obviously you should be mapping entities to ViewModels and never manipulating those entities, but it is a very easy mistake to make. Coupled with con3, it can be near impossible to identify in a complex unit of work.
Conclusion
As long as you are careful about what you are doing, and not arbitrarily altering domain model entities while a session is open, then long-running sessions are not a problem. However there is significant potential of issues if your devs don't understand the risks.
As long as you are happy with standard error/failure, or UI driven resolution workflows, then AOP for unit of work management is acceptable, again as long as the risks / limitations are acknowledged.
As long as you are happy with standard error/failure, or UI driven resolution workflows, then AOP for unit of work management is acceptable, again as long as the risks / limitations are acknowledged.
