18.4.10 ODBI Parameter
The ODBI parameter is used to specify the transaction isolation level for all ODBC database connections.
The default is 0.
Valid values are as per the table following. Any other values will be ignored and the default transaction isolation level will be used. Note that some ODBC drivers may not support all of the transaction isolation levels and may return an error when attempting to set the transaction isolation level.
Note: Careful consideration must be given when specifying this value as it affects all ODBC database connections for the executing application. This is an issue between you, the designer of the application, and your chosen database management system.
|
Value
|
Transaction Isolation Level
|
Meaning
|
|
0
|
SQL_TXN_READ_COMMITTED
|
Refer to Value 2 unless the default for the database is higher.
|
|
1
|
SQL_TXN_READ_UNCOMMITTED
|
Dirty reads, non-repeatable reads and phantoms are possible. This is the default for SQL Anywhere.
|
|
2
|
SQL_TXN_READ_COMMITTED
|
Dirty reads are not possible. Non-repeatable reads and phantoms are possible. This is the default for Oracle and SQL Server.
|
|
3
|
SQL_TXN_REPEATABLE_READ
|
Dirty reads and non-repeatable reads are not possible. Phantoms are possible.
|
|
4
|
SQL_TXN_SERIALIZABLE
|
Transactions are serializable. Dirty reads, non-repeatable reads and phantoms are not possible.
|
|
6
|
SQL Server only: SQL_TXN_SS_SNAPSHOT
|
Refer to LANSA and SQL Server - Configuration Options in the Tips and Techniques on the LANSA web site.
|
|
Platform Specific Notes
IBM i:
- For files that are under Commitment Control, a commitment definition must be exist before any updates are made to these files. Refer to Commitment Control in the LANSA for i User Guide for more information.
- The ODBI parameter is ignored. If a commitment definition exists, LANSA sets the transaction isolation level appropriately for the lock level used when commitment control was started. Otherwise, the transaction isolation level is set to Read Uncommitted. Refer to Isolation Level in the DB2 for i SQL Reference for more information.
Also see
Commitment Control in the LANSA Application Design Guide.
