From: Date: January 31 2007 3:47pm Subject: svn commit - mysqldoc@docsrva: r4703 - in trunk: refman-4.1 refman-5.0 refman-5.1 List-Archive: http://lists.mysql.com/commits/19090 Message-Id: <200701311447.l0VElTSo023930@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: mcbrown Date: 2007-01-31 15:47:28 +0100 (Wed, 31 Jan 2007) New Revision: 4703 Log: Fixing typos (Docs Bug #25699) Modified: trunk/refman-4.1/se-innodb.xml trunk/refman-5.0/se-innodb.xml trunk/refman-5.1/se-innodb.xml Modified: trunk/refman-4.1/se-innodb.xml =================================================================== --- trunk/refman-4.1/se-innodb.xml 2007-01-31 14:45:01 UTC (rev 4702) +++ trunk/refman-4.1/se-innodb.xml 2007-01-31 14:47:28 UTC (rev 4703) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 1155 bytes @@ -597,7 +597,7 @@ - In some cases, database performance improves the if all data is + In some cases, database performance improves if all data is not placed on the same physical disk. Putting log files on a different disk from data is very often beneficial for performance. The example illustrates how to do this. It places the two data @@ -3719,7 +3719,7 @@ Deadlock occurs here because client A needs an X lock to delete the row. However, - that lock request cannot be granted because client B is already + that lock request cannot be granted because client B already has a request for an X lock and is waiting for client A to release its S lock. Nor can the S lock held by A be Modified: trunk/refman-5.0/se-innodb.xml =================================================================== --- trunk/refman-5.0/se-innodb.xml 2007-01-31 14:45:01 UTC (rev 4702) +++ trunk/refman-5.0/se-innodb.xml 2007-01-31 14:47:28 UTC (rev 4703) Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1447 bytes @@ -525,7 +525,7 @@ - In some cases, database performance improves the if all data is + In some cases, database performance improves if all the data is not placed on the same physical disk. Putting log files on a different disk from data is very often beneficial for performance. The example illustrates how to do this. It places the two data @@ -3735,7 +3735,7 @@ Deadlock occurs here because client A needs an X lock to delete the row. However, - that lock request cannot be granted because client B is already + that lock request cannot be granted because client B already has a request for an X lock and is waiting for client A to release its S lock. Nor can the S lock held by A be @@ -4576,7 +4576,7 @@ - Statements that cause implicit cannot be used in an XA + Statements that cause implicit commit cannot be used in an XA transaction while the transaction is in an ACTIVE state. Modified: trunk/refman-5.1/se-innodb.xml =================================================================== --- trunk/refman-5.1/se-innodb.xml 2007-01-31 14:45:01 UTC (rev 4702) +++ trunk/refman-5.1/se-innodb.xml 2007-01-31 14:47:28 UTC (rev 4703) Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1447 bytes @@ -512,7 +512,7 @@ - In some cases, database performance improves the if all data is + In some cases, database performance improves if all the data is not placed on the same physical disk. Putting log files on a different disk from data is very often beneficial for performance. The example illustrates how to do this. It places the two data @@ -3687,7 +3687,7 @@ Deadlock occurs here because client A needs an X lock to delete the row. However, - that lock request cannot be granted because client B is already + that lock request cannot be granted because client B already has a request for an X lock and is waiting for client A to release its S lock. Nor can the S lock held by A be @@ -4514,7 +4514,7 @@ - Statements that cause implicit cannot be used in an XA + Statements that cause implicit commit cannot be used in an XA transaction while the transaction is in an ACTIVE state.