Re: Setting the Isolation Level within ODBC Driver Settings
Posted in 2001
Topics: Connectivity: ODBC / JDBC / .NET, Transactions, Locking & Isolation
On Mon, 5 Feb 2001 14:21:36 -0600, "John Crimi" <crimij@newmetrics.com> wrote: >I am using the Informix ODBC Driver provided by Informix to retrieve data >into an Excel spreadsheet. The problem that I am having is that the default >connection locks the database as I am retrieving the rows. I have looked in >the ODBC documentation to find a way to specify in the connection that the >isolation should be "dirty read" but have have not found a way to do it >either in the ODBC Driver or Informix Connect. > >Your help would be appreciated as when I am requesting large amounts of data >many users are being locked out of the database. > >Thanks in advance. Use the SQLSetStmtOption method, specifically you want to apply one of the SQL_TXN_ISOLATION option masks to your statement handle. From memory, the options are SQL_TXN_READ_UNCOMMITTED SQL_TXN_READ_COMMITTED SQL_TXN_REPEATABLE_READ SQL_TXN_SERIALIZABLE SQL_TXN_VERSIONING Your Informix driver should support them all (though I'm unsure of the last one). Ciao Fuzzy :-)
Fuzzy, Thanks for your help! John "Fuzzy" <granta@nospam.student.canberra.edu.au> wrote in message news:3a7f35c6.4807022@newshost.interact.net.au... > On Mon, 5 Feb 2001 14:21:36 -0600, "John Crimi" > <crimij@newmetrics.com> wrote: > > >I am using the Informix ODBC Driver provided by Informix to retrieve data > >into an Excel spreadsheet. The problem that I am having is that the default > >connection locks the database as I am retrieving the rows. I have looked in > >the ODBC documentation to find a way to specify in the connection that the > >isolation should be "dirty read" but have have not found a way to do it > >either in the ODBC Driver or Informix Connect. > > > >Your help would be appreciated as when I am requesting large amounts of data > >many users are being locked out of the database. > > > >Thanks in advance. > > Use the SQLSetStmtOption method, specifically you want to apply one of > the SQL_TXN_ISOLATION option masks to your statement handle. From > memory, the options are > > SQL_TXN_READ_UNCOMMITTED > SQL_TXN_READ_COMMITTED > SQL_TXN_REPEATABLE_READ > SQL_TXN_SERIALIZABLE > SQL_TXN_VERSIONING > > Your Informix driver should support them all (though I'm unsure of the > last one). > > Ciao > Fuzzy > :-) >