Hi, when one starts a db transaction with system.db.beginTransaction and sets a timeout, in the documentation it states:
If a transaction is detected to have timed out, it will be automatically closed and its transaction id will no longer be valid
Does it also perform a rollback at that time? I would think it would, but I didn't see it listed explicitly in the documentation.
Also, I notice I can only have 8 transactions open from the pool at once on my Oracle test system. I have up to 10 stations that perform an insert to two tables in a database every 4 or 5 seconds. It is conceivable that all could want to have 10 open at once. Is there any control over how many transactions can be active?
Thanks