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.
- take my hands tonight
- window maker
- to extinguish
- spot buy
- solarpowersystem
- transaction journal
- they say its matter of time
- unloadblock
- terminal register
- take my hands up
- what is happening here
- terminal reheat system
- solarsmash
- to f
- vi auguro felicit
- watch the team games
- they say love is blind
- solarsmasher
- turning into an icy rain that
- superelevate
- to face