As they respond to the write transactions they become eligible for further read transactions (selects).
当对写事务作出响应时，它们才有资格接收之后的读事务(选择)。
Because driver maintains connection to both nodes while write transactions are directed to the primary node, read transactions can be directed to either node.
由于驱动程序维护与两个节点的连接，同时写事务被定向到主节点，因此读事务可以定向到任何一个节点。
Read transactions require a consistent view of the data -- meaning if two read transactions are submitted at the same time, they should produce uniform result sets if they select the same data ranges.
读事务需要数据的一致视图 ——即当同时提交两个读事务时，如果它们选择相同的数据范围，那么应该产生一致的结果集。
(Locked rows can, however, be read by other transactions).
(但其他事务可读取锁定行)。
Run the read-only operations with no database transactions, as discussed previously.
如前所述，不带有任何数据库事务地运行只读操作。
This has interesting implications for the question of whether to use no transactions or read-only transactions in flow-managed persistence.
这对于在流管理的持久化中是不使用事务还是使用只读事务的问题产生了有趣的影响。
The initialization of the split mirror as snapshot performs a crash recovery, rolls back all uncommitted transactions, and makes the database available for any read or write operation.
将分割镜像初始化为快照时，将执行崩溃恢复，回滚所有未提交的事务，并使数据库可以被所有读或写操作访问。
Because database "b" only provides read-only data, we still use local transactions on both databases for those methods.
因为数据库“B”只提供只读数据，我们对这些方法在这两个数据库上仍然使用本地事务。
Because both of these operations are running in the same transaction and the previous access to EIS2 is read-only no compensating transactions are required at this stage.
因为这两项操作都是运行在同一事务中，而前面对EIS2的访问是只读的，所以在这一段中需要补偿事务。
The transactions involve one or two federated sources and comprise two multi-site update transactions (49%), two read only transactions (8%) and one single-site update (43%).
这些事务涉及一个或两个联邦数据源，并且由两个多站点更新事务(49%)、两个只读事务(8%)和一个单站点更新(43%)组成。
This is a great advantage of using read-only transactions over non-transactional data access in flow-managed persistence.
这是在流管理持久化中使用只读事务优于使用非事务性数据访问的地方。
In the event that all the transactions are read-only, the entire second phase is avoided.
在所有事务均为只读的情况下，可以避免整个第二阶段。
By now you may be wondering if this access to non-DB2 data using stored procedures is suitable for read-only types of operations or if can be used for real-world transactions.
至此，您可能想知道，这种使用存储过程访问非db2数据的方法是否适用于只读类型的操作，或者是否能用于现实中的事务。
Now, a read transaction can access the currently committed and consistent image of rows that are incompatibly locked by write transactions without being blocked.
现在，读取事务可以访问当前提交的、连贯的行映像(写入事务以不兼容方式锁定)，而不会受到阻塞。
After 5 minutes of commit transaction time, the secondary node will read the transactions from the staging directory LOG_STAGING_DIR and apply them.
在5分钟的提交事务时间之后，次要节点将从暂存目录LOG_STAGING_DIR读取事务，然后应用它们。
Read-only transactions are not supported by the JPA 1.0 specification, so this setting is useable only in some JPA providers.
JPA 1.0规范不支持只读事务，因此只有在某些JPA提供商中才能使用此设置。
In some cases, you might prefer read-only transactions over non-transactional ones.
在某些情况下，与非事务性事务相比您可能更愿意使用只读事务。
It is important that this data is correctly protected from the competing requirements of those transactions that require read access, and those that require update access.
在请求读访问和请求更新访问的事务之间产生冲突时，数据能否得到正确的保护是十分重要的。
SQL transactions fall into two basic types, read and write.
SQL事务可分为两种类型：读和写。
For example, a collector might be invoked every minute to read a host's CPU utilization or read the total number of committed transactions from a transaction manager through a JMX interface.
例如，可以每分钟调用一次收集器来读取主机的cpu利用率，或通过JXM接口从事务管理器读取提交事务的总数。
Read-only transactions executed on the secondary server
备用服务器上执行的只读事务
The most important of these is a multi-site read/update called "new order" that makes up about 45% of all transactions.
其中最重要的事务是名为 “neworder” 的多站点读/更新事务，大约占所有事务的 45%。
Update transactions first read a specific document based on an XQuery predicate, and then use it to update the original copy of that document in the database.
更新事务首先根据一个XQuery谓词读取一个特定文档，然后使用它更新数据库中这个文档的原副本。
In this case, we direct the Design Advisor to read the workload from a file which contains the transactions.
在这个案例中，我们让Design Advisor从一个包含事务的文件中读取工作负载。
Secondly, the pages are difficult to read because of both the design and the amount of information on the pages. Most of the information is not needed and will not enhance transactions.
其次，由于信息量过大和其不合理的设计，网页的可读性大大降低。
Mark them @Transactional(readOnly=false) such that the SQL queries are executed under read/write database transactions.
将其标记为 @Transactional(readOnly=false)，这样可以在读/写数据库事务下执行SQL查询。
Read committed -- The transaction can read data committed by other transactions.
Readcommitted（读已提交） ——事务可以读取由另一事务提交的数据。
Read-only transactions in Web flows.
web流中的只读事务。
The Spring framework does support read-only transactions.
Spring框架也支持只读事务。
Write a program that reads several transactions for the same ISBN. Write the sum of all the transactions that were read.
编写程序，读入几个具有相同ISBN的交易，输出所有读入交易的和。
应用推荐