Henry, I'm sorry if I offended you. To anyone who is still reading:
> You're proposing this read only tx bullshit. I don't expect a > transaction to be readonly and be commited or rollbacked. It is a perfectly normal to start a transaction that only reads and does not write. Yes, the semantics of 'committing' that transaction are a bit weird, but thats the way it is. > Anyway, open 2pc transaction and mark it's a readonly it's a freaking > hack and doesn't makes sense. The solution must be something on the > session machinery and not in the tx machinery. It does make sense. We need some way of telling the session to be readonly (ie FlushMode == Never) for the duration of this particular transaction, and thats exactly what this change does. This is necessary because the nhibernate session is not transactional, or as hammet pointed out, nor is memory: http://groups.google.com/group/castle-project-devel/msg/c4e4d41acfa7f162 Jordan. -- 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.
