PS: Isn't the new per-transaction lifestyle better for fixing this NHibernate problem of read-after-faulted-write?
On Mar 15, 12:25 pm, Jordan <[email protected]> wrote: > Just briefly, a read only session in this scenario is not suitable > because the session is already open. The example in my first post > demonstrates this. AFAIK it is strongly against the advice of the > hibernate developers to have 2 sessions (persistence contexts) open at > the same time. This patch fixes a very real problem faced by > developers using nhibernate. > > regards, > Jordan. > > btw - Henry, I am not really trying to change your mind about this, I > accept that you don't like it :) > I'm just explaining my case for anyone else who might be reading and > want to help apply the patch. -- 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.
