transaction isolation的意思

transaction isolation中文翻譯：

事務隔離

相似詞語短語

isolation───n.隔離；孤立；[電]絕緣；[化學]離析

transaction───n.交易；事務；辦理；會報，學報

splendid isolation───光榮的孤立（以前的英國外交政策，表示不卷入歐洲政治旋渦）；光輝孤立

isolation forest───隔離林

orderly transaction───有序交易

isolation ward───n.隔離病房

isolation valve───[機]隔離閥；[化] 隔離閥

transaction failed───交易失敗

commercial transaction───買賣，交易；商業行為

雙語使用場景

Isolation: JPA 1.0 doesn't support custom isolation levels, so developers are required to specify the default transaction isolation level on the database side.───isolation： JPA 1.0不支持自定義隔離級別，因此開發人員需要指定數據庫端的默認事務隔離級別。

Follow the steps in transaction isolation level setting for a data source reference to change the transaction isolation level to REPEATABLE_READ, and run the application again.───遵循為數據源引用設置事務隔離級別中的步驟將事務隔離級別更改為REPEATABLE_READ，然后再次運行該應用程序。

Without proper transaction isolation, other units of work can access updates made by an ongoing unit of work, even though that unit of work is incomplete.───沒有適當的事務隔離性，其他工作單元就可以訪問某一活動工作單元所做的更新，即使該工作單元還未完成。

The transaction isolation level is the degree to which the underlying database exposes changed but uncommitted data to other transactions.───事務隔離級別是基礎數據庫將已更改但尚未提交的數據向其他事務公開的程度。

To determine the transaction isolation level currently set, use the DBCC USEROPTIONS statement as shown in the following example.───若要確定當前設置的事務隔離級別，請使用DBCCUSEROPTIONS語句，如下面的示例所示。

The J2EE specification defines a deployment descriptor attribute that specifies the transaction isolation level for a given EJB method.───J2EE規范定義了用來為具體EJB方法指定事務隔離級別的部署描述符屬性。

Symptom: Informix transaction isolation settings in a session are not getting propagated across XA global transactions.───現象：會話中的Informix事務隔離設置沒有在XA全局事務中得到傳播。

Choosing a transaction isolation level does not affect the locks that are acquired to protect data modifications.───選擇事務隔離級別不影響保護數據修改所需的鎖定。

These characteristics reduce the chance for catastrophic results stemming from inconsistency and lack of transaction isolation.───這些特點降低了由于不一致性和缺少事務隔離而導致災難性結果的機會。

英語使用場景

The J2EE specification defines a deployment descriptor attribute that specifies the transaction isolation level for a given EJB method.

If value is set to 2, the optimizer would uses estimated costs to determine an execution plan regardless of the transaction isolation mode.

The transaction isolation level is the degree to which the underlying database exposes changed but uncommitted data to other transactions.

GemFire Enterprise 5.5 adds a "Repeatable Read" cache transaction isolation level to the other two isolation levels already supported: "Read Committed" and "Uncommitted Read".

If the transaction isolation mode is Repeatable Read, then the optimizer would base its choice purely on the estimated costs.