CUBRID specifies a transaction isolation level so that the transaction is executed with less restrictive consistency. The transaction isolation level is the degree to which a transaction is separated from all other concurrent transactions. The higher the isolation level, the lower the influences from other transactions. The lower the isolation level, the higher concurrency. A transaction is valid if the transaction acquires a lock in an exclusive (shared/exclusive) mode before it updates (reads) an object and does not acquire any more locks after they are released.
Note A transaction can be restored in all supported isolation levels because updates are not committed before the end of the transaction.