A given application might never update the underlying data or be run with other concurrent updaters.
某个给定的应用程序可能从不更新底层数据，或者从来不与其它并发更新程序一起运行。
Using this policy, one must be sure that there will be no concurrent update to the same row or range of rows.
使用该策略时必须确保同一行或多行没有进行同时的更新。
This property should be set to false in concurrent update scenarios as deadlocks may occur in these scenarios. V5.1.0.1 true false
在并发更新的情况下，这一属性应该设置为false，因为在这些情况下可能出现死锁。
When a table holds a Z lock, no concurrent application can read or update data in that table.
当表持有z锁时，任何并发应用程序都不能读取和更新该表中的数据。
When a table holds an IX lock, the lock owner and concurrent applications can read and update data in that table.
当表持有IX锁时，锁拥有者和并发应用程序可以读和更新该表中的数据。
However, it does not easily offer the flexibility of running multiple concurrent scripts to update statistics against different sets of tables in the same database.
但是它不能灵活地运行多个并发脚本，来在同一数据库中根据不同的表来更新统计数据。
Support for concurrent AIX kernel updates: allows you to update systems without having to do a reboot for this to take effect.
支持并发aix内核更新：不需要重新引导系统，系统更新即可生效。
Use the "nonstrict-read-write" strategy if your data is read-mostly or concurrent cache access and update is rare.
如果你的数据读很多或者很少有并发缓存访问和更新，那么可以使用“nonstrict - read - write”策略。
That is, if concurrent transactions update an entity bean with same primary key, updates could get lost.
如果并发事务用同样的主键更新实体bean 时，更新资料将会丢失。
Meanwhile, data update and schema change are possible to coexist under the concurrent environment which brings about many problems to view maintenance.
在并发环境下，数据更新和模式更新极有可能同时存在，这对视图维护工作带来极大的困难。
Meanwhile, data update and schema change are possible to coexist under the concurrent environment which brings about many problems to view maintenance.
在并发环境下，数据更新和模式更新极有可能同时存在，这对视图维护工作带来极大的困难。
应用推荐