> I think you're biased by the jta exposure. > > If you don't want a commit or a rollback, don't open a freaking > transaction. Why you want to add the tx overhead to some context if > you don't want the 2pc?
Hi Henry, I think I'm getting the picture that you don't like this at all, but you might want to read this article (it certainly surprised me when I first read it, and led to me always explicitly marking my transactions). http://community.jboss.org/wiki/Non-transactionaldataaccessandtheauto-commitmode In summary, by default SQLServer is set to auto commit mode, which means that if you don't explicitly start a transaction, a separate database transaction begins and ends (commits or rollsback) for each SQL statement you send to the database. (Yes, even just select statements). So if you have some code that issues multiple selects, you might actually end up with more overhead by not starting a transaction. Also, Oracle does implement read only transactions - so potentially this could be extended in the future to add some support for that. http://www.stanford.edu/dept/itss/docs/oracle/10g/server.101/b10759/statements_10005.htm 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.
