添加清单10中的代码将数据读回并更改呈现的信息。
Add the code shown below in Listing 10 to read the data back in and change the presented information.
框架同步信号检测，存储，并插以确保稳定的数据读回。
The frame synchronizing signal is detected, stored, and interpolated to insure stable data read back.
最常见的错误是做出这样的假设：因为程序将该数据写出，该程序就能不用验证再一次将该数据读回去。
The most common mistake is to assume that because an instance of your program wrote the data out, it can read that data back in again without verifying it.
如果你的数据读很多或者很少有并发缓存访问和更新，那么可以使用“nonstrict - read - write”策略。
Use the "nonstrict-read-write" strategy if your data is read-mostly or concurrent cache access and update is rare.
Informix：如果数据格式指定为Informix，从(到)文件的数据读(或写)将采用只能通过Informix解码的二进制格式。
Informix: if the data format is specified as Informix, the data read (or written) from (or to) the file is in the binary format that can be decoded only by Informix.
当从套接字读取数据时，如果EWOULDBLOCK返回。有可能，只有部分数据读取？或者是当ewouldblock返回的数据读是0吗？
When reading from socket, if EWOULDBLOCK is returned... is it possible that only partial data is read? Or is it that when EWOULDBLOCK is returned data read is 0?
显然，对所有数据编索引不仅对于读而且对于写都很耗时。
Indexing all that data is obviously expensive for reads, but also for writes.
与前面其他优化一样，这个优化在磁盘上收集相关的数据，以实现相邻读优化。
Like the previous optimizations, this optimization collects related data on the disk to optimize for sequential Read optimization.
注意其中的差别，方法，也就是指令序列，其实是需要读的，被当做数据来对待。
Notice the difference. The recipe, the sequence of instructions, is actually getting read in, and it's treated just like data.
对于关系数据是如此，对于XML的读和写访问更是如此。
This is true for relational data, and even more so for XML read and write access.
由于只需复制被更改的数据，所以读事务不受HADR实现的影响。
Only data changes are required to be replicated, so read transaction are unaffected by the implementation of HADR.
因此，请求存储在内存中的数据的读事件不会访问硬盘。
Therefore, read events that request data already stored in memory don't generate a trip to the hard disk.
DB 2直接从磁盘读(写)lob数据。
该方法要求确保数据在被读或是被更新时没有改变。
This method requires a way to ensure that the data has not been altered between the time it was read it and when it was updated.
如果你的数据是又读又写的，那么使用“read-write”策略。
buf_read _ callback：当客户端套接字有要读的数据时调用它。
Buf_read_callback : Called when the client socket has data to be read.
然后，您就可以写入必要的数据，并为数据提供不错的读性能。
You can then write the necessary data and provide bounded Read performance over the data.
每个成员可以同时访问相同的数据库，包括读和写操作。
Each member can simultaneously access the same database for both read and write operations.
信道数是等待被读取的数据量(对于读信道而言)或仍能被写入的数据量(对于写信道而言)。
The channel count is the amount of data waiting to be read (for read channels), or the amount of data which can still be written (for write channels).
但是，假若我们想全部利用IOCP服务器的潜力，我们应该有很多的异步读操作等待数据的到达。
But if we want to use the IOCP server's full potential, we should have several pending asynchronous reads waiting for data to arrive.
注册风格：这种风格为只需要读主数据而不需要修改的下游系统提供主数据的只读视图。
Registry style: This style provides a read-only view to master data for downstream systems which need to read but not modify master data.
请记住，这里所使用的帐户必须具有对REPORTS数据库的读权限。
Keep in mind that the account used here must have read rights to the REPORTS database.
在数据库读操作成功之后，它循环遍历结果集并收集帐户数据信息。
After a successful database read operation, it iterates on the result set and collects the individual account data information.
在收集到新的事件数据时，与最近的未读事件数据进行比较。
When new event data is collected, it is compared to the most recent unread event data.
读事务需要数据的一致视图 ——即当同时提交两个读事务时，如果它们选择相同的数据范围，那么应该产生一致的结果集。
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.
当用户试图读带安全标签的数据时，则应用读访问规则。
Read access rules are applied when a user attempts to read labeled data.
他们没有建立严格的事务规则，而是把数据库表推到最简，索引只用来引用，发生实际的数据库读操作的时候才施加数据过滤。
Instead of a strict transaction protocol, they made the database tables canonical and used the indexes only for references and reapplied filters to the actual database reads.
当测量血压时，要读两个数据——心脏收缩压和心脏舒张压。
When your blood pressure is measured, there are two readings — systolic and diastolic.
其他特性（比如多MAIL.BOX数据库）消除了未读标记带来的额外开销，并且通过事务日志改进了性能。
Other features, like multiple MAIL.BOX databases, eliminating the extra overhead of unread marks, and transaction logging have also improved performance.
其他特性（比如多MAIL.BOX数据库）消除了未读标记带来的额外开销，并且通过事务日志改进了性能。
Other features, like multiple MAIL.BOX databases, eliminating the extra overhead of unread marks, and transaction logging have also improved performance.
应用推荐