Author: paul
Date: 2007-08-23 16:38:39 +0200 (Thu, 23 Aug 2007)
New Revision: 7524
Log:
r29258@polar: paul | 2007-08-23 09:31:14 -0500
Slight rewording for effect of updates on rows seen by
consistent read. (PeterG)
Modified:
trunk/refman-4.1/se-innodb.xml
trunk/refman-5.0/se-innodb.xml
trunk/refman-5.1/se-innodb.xml
trunk/refman-5.2/se-innodb.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:29253
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24002
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19696
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:29258
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:24002
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19696
Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml 2007-08-23 14:37:31 UTC (rev 7523)
+++ trunk/refman-4.1/se-innodb.xml 2007-08-23 14:38:39 UTC (rev 7524)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1043 bytes
@@ -4038,10 +4038,10 @@
by earlier statements within the same transaction. Note that the
exception to the rule causes the following anomaly: if you
update some rows in a table, a <literal>SELECT</literal> will
- see the latest version of the updated rows, while it sees the
- old version of other rows. If other users simultaneously update
- the same table, the anomaly means that you may see the table in
- a state that never existed in the database.
+ see the latest version of the updated rows, but it might also
+ see older versions of any rows. If other users simultaneously
+ update the same table, the anomaly means that you may see the
+ table in a state that never existed in the database.
</para>
<para>
Modified: trunk/refman-5.0/se-innodb.xml
===================================================================
--- trunk/refman-5.0/se-innodb.xml 2007-08-23 14:37:31 UTC (rev 7523)
+++ trunk/refman-5.0/se-innodb.xml 2007-08-23 14:38:39 UTC (rev 7524)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1043 bytes
@@ -4033,10 +4033,10 @@
by earlier statements within the same transaction. Note that the
exception to the rule causes the following anomaly: if you
update some rows in a table, a <literal>SELECT</literal> will
- see the latest version of the updated rows, while it sees the
- old version of other rows. If other users simultaneously update
- the same table, the anomaly means that you may see the table in
- a state that never existed in the database.
+ see the latest version of the updated rows, but it might also
+ see older versions of any rows. If other users simultaneously
+ update the same table, the anomaly means that you may see the
+ table in a state that never existed in the database.
</para>
<para>
Modified: trunk/refman-5.1/se-innodb.xml
===================================================================
--- trunk/refman-5.1/se-innodb.xml 2007-08-23 14:37:31 UTC (rev 7523)
+++ trunk/refman-5.1/se-innodb.xml 2007-08-23 14:38:39 UTC (rev 7524)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1043 bytes
@@ -4048,10 +4048,10 @@
by earlier statements within the same transaction. Note that the
exception to the rule causes the following anomaly: if you
update some rows in a table, a <literal>SELECT</literal> will
- see the latest version of the updated rows, while it sees the
- old version of other rows. If other users simultaneously update
- the same table, the anomaly means that you may see the table in
- a state that never existed in the database.
+ see the latest version of the updated rows, but it might also
+ see older versions of any rows. If other users simultaneously
+ update the same table, the anomaly means that you may see the
+ table in a state that never existed in the database.
</para>
<para>
Modified: trunk/refman-5.2/se-innodb.xml
===================================================================
--- trunk/refman-5.2/se-innodb.xml 2007-08-23 14:37:31 UTC (rev 7523)
+++ trunk/refman-5.2/se-innodb.xml 2007-08-23 14:38:39 UTC (rev 7524)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 1043 bytes
@@ -4048,10 +4048,10 @@
by earlier statements within the same transaction. Note that the
exception to the rule causes the following anomaly: if you
update some rows in a table, a <literal>SELECT</literal> will
- see the latest version of the updated rows, while it sees the
- old version of other rows. If other users simultaneously update
- the same table, the anomaly means that you may see the table in
- a state that never existed in the database.
+ see the latest version of the updated rows, but it might also
+ see older versions of any rows. If other users simultaneously
+ update the same table, the anomaly means that you may see the
+ table in a state that never existed in the database.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7524 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 23 Aug |
