Re: Need commit/rollback for query exe returning a read-only, non-scrollable resultset?
Wednesday, September 5, 2001 02:38 PM
this is vendor-specific. there is some manipulation you can do in the app server with setting transaction isolation levels (e.g. read uncommitted) where there is no sane reason why RDBMS will hold a lock on tables during a transaction. the more restricted isolation levels are, less performance due to db locking tables and less restrictive means better performance but also opens up a chance for dirty reads and other transaction isolation issues.