Karl,

I think it really depends on the app and usage scenario as to whether you'd want to make read methods non-transactional. Generally, I think it's easierand better to start with things transactional, then the config is simpler, and there are no issues with inconsitent data. Even if you are only reading data, if data is being read in multiple operations it can be inconsistent if you are non-transactional. Then if you start needing to optimize, you can do things like reading non-transactionally. Don't forget also that you can also do things like mark a transaction as read only, which will make the tx never commit, but still ensure that the data you read is consistent in that batch...

Regards,