You're proposing this read only tx bullshit. I don't expect a transaction to be readonly and be commited or rollbacked.
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. I'm done here. Cheers, Henry Conceição On Tue, Oct 5, 2010 at 1:46 PM, Jordan Muscott <[email protected]> wrote: > On Oct 5, 5:36 pm, Henry Conceição <[email protected]> wrote: >> I'm pretty aware of what the Facility can do or not. I just want to >> know what you were doing. You know, from someone that marks a >> transaction as a readonly but still leave the commit/rollback working, >> we must expect everything. > > How else do you propose that a transaction is ended without committing > or rolling it back? > > 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. > > -- 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.
