Accessing tables through DBlinks via ADF BC entities, jdev11.1.1.2.0

Question

To my understanding, everytime any object is accessed via a dblink, a transaction is created on the database; even if one merely selects from a table. For example, whenever we were writing PL/SQL, after we were finished accessing data through a dblink we performed a commit to close any open transaction that opened via selects. Using ADF BC, if we create an entity that accesses a table via dblink, what guarantee that transaction sessions are closed after simple selects (no DML)? How would these transactions be closed if data from a db link is simply displayed in an ADF table or referenced via LOV? Is there perhaps some setting that can be set to open connections without transactions?
Reference: http://www.jlcomp.demon.co.uk/faq/dblink_commit.html
Best Regards,
Valon

Answer 1

valon,
This is indeed a tricky one. You are correct that a transaction is started whenever you do any selects that touch a remote object. The problem that I see is that even if you were somehow able to execute a commit after every SELECT statement, the transaction always executes in the context of an application module - if you committed the transaction, you'd also commit any outstanding transaction going on in the AM at the time. In general, this would be a bad thing, although you may be able to ensure that it is OK for your specific use case. I did a quick scan of the APIs to see if I could locate any method that you could possibly override, but didn't locate anything that looked promising.
John