The use of RWDBConnection has implications for transaction control and locking. As you might expect, uncommitted transactions on one RWDBConnection may not be visible through another RWDBConnection, depending on the isolation level of the RWDBConnection instances.

Controlling connections in a database application is critical to avoiding front-end dead-lock. This problem can occur when the user tries to access data through one connection, while another connection holds a lock on that data. Almost every database application developer has encountered this problem. Users must be responsible for designing applications and managing connections to avoid this situation.