php中getdb,PHP: cubrid_get_db_parameter - Manual

说明

array cubrid_get_db_parameter ( resource $conn_identifier )

This function returns the CUBRID database parameters or it returns FALSE on failure. It returns an associative array with the values for the following parameters:

PARAM_ISOLATION_LEVEL

PARAM_LOCK_TIMEOUT

PARAM_MAX_STRING_LENGTH

PARAM_AUTO_COMMIT

Database parameters Parameter Description PARAM_ISOLATION_LEVEL The transaction isolation level.

LOCK_TIMEOUT CUBRID provides the lock timeout feature, which sets the waiting time (in seconds) for the lock until the transaction lock setting is allowed. The default value of the lock_timeout_in_secs parameter is -1, which means the application client will wait indefinitely until the transaction lock is allowed.

PARAM_AUTO_COMMIT In CUBRID PHP, auto-commit mode is disabled by default for transaction management. It can be set by using

The following table shows the isolation levels from 1 to 6. It consists of table schema (row) and isolation level:Levels of Isolation Supported by CUBRID Name Description SERIALIZABLE (6) In this isolation level, problems concerning concurrency (e.g. dirty read, non-repeatable read, phantom read, etc.) do not occur.

REPEATABLE READ CLASS with REPEATABLE READ INSTANCES (5) Another transaction T2 cannot update the schema of table A while transaction T1 is viewing table A. Transaction T1 may experience phantom read for the record R that was inserted by another transaction T2 when it is repeatedly retrieving a specific record.

REPEATABLE READ CLASS with READ COMMITTED INSTANCES (or CURSOR STABILITY) (4) Another transaction T2 cannot update the schema of table A while transaction T1 is viewing table A. Transaction T1 may experience R read (non-repeatable read) that was updated and committed by another transaction T2 when it is repeatedly retrieving the record R.

REPEATABLE READ CLASS with READ UNCOMMITTED INSTANCES (3) Default isolation level. Another transaction T2 cannot update the schema of table A while transaction T1 is viewing table A. Transaction T1 may experience R' read (dirty read) for the record that was updated but not committed by another transaction T2.

READ COMMITTED CLASS with READ COMMITTED INSTANCES (2) Transaction T1 may experience A' read (non-repeatable read) for the table that was updated and committed by another transaction T2 while it is viewing table A repeatedly. Transaction T1 may experience R' read (non-repeatable read) for the record that was updated and committed by another transaction T2 while it is retrieving the record R repeatedly.

READ COMMITTED CLASS with READ UNCOMMITTED INSTANCES (1) Transaction T1 may experience A' read (non-repeatable read) for the table that was updated and committed by another transaction T2 while it is repeatedly viewing table A. Transaction T1 may experience R' read (dirty read) for the record that was updated but not committed by another transaction T2.