| List: | Internals | « Previous MessageNext Message » | |
| From: | paul | Date: | July 31 2005 5:50pm |
| Subject: | bk commit - mysqldoc@docsrva tree (paul:1.3144) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of paul. When paul does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.3144 05/07/31 11:50:07 paul@stripped +29 -0 Kill Texinfo quotes. refman/using-mysql-programs.xml 1.4 05/07/31 11:50:04 paul@stripped +20 -19 Kill Texinfo quotes. refman/tutorial.xml 1.8 05/07/31 11:50:03 paul@stripped +32 -30 Kill Texinfo quotes. refman/triggers.xml 1.12 05/07/31 11:50:03 paul@stripped +3 -3 Kill Texinfo quotes. refman/stored-procedures.xml 1.10 05/07/31 11:50:03 paul@stripped +7 -6 Kill Texinfo quotes. refman/storage-engines.xml 1.9 05/07/31 11:50:03 paul@stripped +40 -38 Kill Texinfo quotes. refman/sql-syntax.xml 1.27 05/07/31 11:50:03 paul@stripped +111 -103 Kill Texinfo quotes. refman/spatial-extensions-in-mysql.xml 1.5 05/07/31 11:50:02 paul@stripped +8 -7 Kill Texinfo quotes. refman/replication.xml 1.8 05/07/31 11:50:02 paul@stripped +7 -7 Kill Texinfo quotes. refman/regexp.xml 1.3 05/07/31 11:50:02 paul@stripped +3 -3 Kill Texinfo quotes. refman/problems.xml 1.10 05/07/31 11:50:02 paul@stripped +64 -58 Kill Texinfo quotes. refman/mysql-connectors.xml 1.10 05/07/31 11:50:01 paul@stripped +6 -6 Kill Texinfo quotes. refman-5.0/tutorial.xml 1.10 05/07/31 11:50:01 paul@stripped +22 -21 Kill Texinfo quotes. refman-5.0/triggers.xml 1.12 05/07/31 11:50:01 paul@stripped +3 -3 Kill Texinfo quotes. refman-5.0/stored-procedures.xml 1.10 05/07/31 11:50:01 paul@stripped +7 -6 Kill Texinfo quotes. refman-5.0/storage-engines.xml 1.13 05/07/31 11:50:01 paul@stripped +4 -4 Kill Texinfo quotes. refman-5.0/sql-syntax.xml 1.32 05/07/31 11:49:59 paul@stripped +113 -103 Kill Texinfo quotes. refman-5.0/spatial-extensions-in-mysql.xml 1.5 05/07/31 11:49:58 paul@stripped +8 -7 Kill Texinfo quotes. refman-5.0/regexp.xml 1.3 05/07/31 11:49:58 paul@stripped +3 -3 Kill Texinfo quotes. refman-5.0/problems.xml 1.10 05/07/31 11:49:58 paul@stripped +64 -58 Kill Texinfo quotes. refman-5.0/mysql-connectors.xml 1.7 05/07/31 11:49:58 paul@stripped +13 -10 Kill Texinfo quotes. refman-4.1/using-mysql-programs.xml 1.4 05/07/31 11:49:57 paul@stripped +20 -19 Kill Texinfo quotes. refman-4.1/tutorial.xml 1.8 05/07/31 11:49:57 paul@stripped +32 -30 Kill Texinfo quotes. refman-4.1/storage-engines.xml 1.9 05/07/31 11:49:57 paul@stripped +40 -38 Kill Texinfo quotes. refman-4.1/sql-syntax.xml 1.22 05/07/31 11:49:57 paul@stripped +100 -92 Kill Texinfo quotes. refman-4.1/spatial-extensions-in-mysql.xml 1.5 05/07/31 11:49:56 paul@stripped +8 -7 Kill Texinfo quotes. refman-4.1/replication.xml 1.7 05/07/31 11:49:56 paul@stripped +33 -30 Kill Texinfo quotes. refman-4.1/regexp.xml 1.3 05/07/31 11:49:56 paul@stripped +3 -3 Kill Texinfo quotes. refman-4.1/problems.xml 1.10 05/07/31 11:49:56 paul@stripped +64 -58 Kill Texinfo quotes. refman-4.1/mysql-connectors.xml 1.7 05/07/31 11:49:55 paul@stripped +13 -10 Kill Texinfo quotes. # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: paul # Host: frost.snake.net # Root: /Volumes/frost2/MySQL/bk/mysqldoc --- 1.6/refman-4.1/mysql-connectors.xml 2005-07-27 13:13:26 -04:00 +++ 1.7/refman-4.1/mysql-connectors.xml 2005-07-31 11:49:55 -04:00 @@ -931,9 +931,10 @@ most cases, you can continue by pressing <literal>Ignore</literal> to copy the rest of the MyODBC files and the final installation should still work. If it doesn't, the - solution is to re-boot your computer in ``safe mode.'' Choose - safe mode by pressing F8 just before your machine starts Windows - during re-booting, install MyODBC, and re-boot to normal mode. + solution is to re-boot your computer in <quote>safe + mode.</quote> Choose safe mode by pressing F8 just before your + machine starts Windows during re-booting, install MyODBC, and + re-boot to normal mode. </para> </section> @@ -2640,9 +2641,9 @@ <row> <entry>2</entry> <entry>The client can't handle that MySQL returns the true value of affected - rows. If this flag is set, MySQL returns ``found - rows'' instead. You must have MySQL 3.21.14 or newer - to get this to work.</entry> + rows. If this flag is set, MySQL returns <quote>found + rows</quote> instead. You must have MySQL 3.21.14 or + newer to get this to work.</entry> </row> <row> <entry>4</entry> @@ -3905,7 +3906,7 @@ <para> The purpose of <literal>CONCAT()</literal> in this example is to fool ODBC into thinking the column is - of ``string type.'' Without the + of <quote>string type.</quote> Without the <literal>CONCAT()</literal>, ODBC knows the column is of time type, and Excel does not understand that. </para> @@ -4843,7 +4844,8 @@ <title id='title-trapping-odbc-errors'>&title-trapping-odbc-errors;</title> <para> - Read ``How to Trap ODBC Login Error Messages in Access'' at + Read <quote>How to Trap ODBC Login Error Messages in + Access</quote> at <ulink url="http://support.microsoft.com/support/kb/articles/Q124/9/01.asp?LN=EN-US&SD=gn&FR=0%3CP%3E"/>. </para> @@ -4919,7 +4921,8 @@ <title id='title-query-timeout'>&title-query-timeout;</title> <para> - Read ``Set the QueryTimeout Value for ODBC Connections'' at + Read <quote>Set the QueryTimeout Value for ODBC + Connections</quote> at <ulink url="http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B153756"/>. </para> @@ -7534,7 +7537,7 @@ </section> - <xi:include href="../Docs/connector-net.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="../Docs/connector-net.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="../Docs/connector-j-en.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --- 1.9/refman-4.1/problems.xml 2005-07-19 22:54:54 -04:00 +++ 1.10/refman-4.1/problems.xml 2005-07-31 11:49:56 -04:00 @@ -155,15 +155,16 @@ happening. You should also state why you think that MySQL is causing the problem. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you - examine your system. Use the ``copy and paste'' method for any - output and error messages from programs and log files. + examine your system. Use the <quote>copy and paste</quote> method + for any output and error messages from programs and log files. </para> <para> Try to describe in detail which program is not working and all symptoms you see. We have in the past received many bug reports - that state only ``the system doesn't work.'' This doesn't provide - us with any information about what could be the problem. + that state only <quote>the system doesn't work.</quote> This + doesn't provide us with any information about what could be the + problem. </para> <para> @@ -553,9 +554,9 @@ <para> Substitute the password you want to use for - ``<replaceable>newpwd</replaceable>'' in the preceding - examples. MySQL cannot tell you what the original password - was, so you'll need to pick a new one. + <quote><replaceable>newpwd</replaceable></quote> in the + preceding examples. MySQL cannot tell you what the original + password was, so you'll need to pick a new one. </para> </listitem> @@ -1790,8 +1791,8 @@ <literal>--open-files-limit</literal> and <command>ulimit</command> can increase the number of file descriptors, but only up to the limit imposed by the operating - system. There is also a ``hard'' limit that can be overridden - only if you start <command>mysqld_safe</command> or + system. There is also a <quote>hard</quote> limit that can be + overridden only if you start <command>mysqld_safe</command> or <command>mysqld</command> as <literal>root</literal> (just remember that you also need to start the server with the <literal>--user</literal> option in this case so that it does @@ -2455,9 +2456,9 @@ </para> <para> - Replace ``<replaceable>newpwd</replaceable>'' with the - actual <literal>root</literal> password that you want to - use. + Replace <quote><replaceable>newpwd</replaceable></quote> + with the actual <literal>root</literal> password that you + want to use. </para> </listitem> @@ -2822,16 +2823,17 @@ <para> This section describes how MySQL responds to disk-full errors - (such as ``no space left on device''), and, as of MySQL 4.0.22, - to quota-exceeded errors (such as ``write failed'' or ``user - block limit reached"). + (such as <quote>no space left on device</quote>), and, as of + MySQL 4.0.22, to quota-exceeded errors (such as <quote>write + failed</quote> or <quote>user block limit reached</quote>). </para> <para> This section is relevant for writes to <literal>MyISAM</literal> tables. As of MySQL 4.1.9, it also applies for writes to binary log files and binary log index file, except that references to - ``row'' and ``record'' should be understood to mean ``event.'' + <quote>row</quote> and <quote>record</quote> should be + understood to mean <quote>event.</quote> </para> <para> @@ -2881,9 +2883,10 @@ <listitem> <para> Other threads might be waiting for the table that caused the - disk-full condition. If you have several ``locked'' threads, - killing the one thread that is waiting on the disk-full - condition allows the other threads to continue. + disk-full condition. If you have several + <quote>locked</quote> threads, killing the one thread that + is waiting on the disk-full condition allows the other + threads to continue. </para> </listitem> @@ -3217,9 +3220,10 @@ <para> Simple comparison operations (<literal>>=, >, =, <, <=</literal>, sorting, and grouping) are based on each - character's ``sort value.'' Characters with the same sort value - (such as '<literal>E</literal>', '<literal>e</literal>', and - '<literal>é</literal>') are treated as the same character. + character's <quote>sort value.</quote> Characters with the same + sort value (such as '<literal>E</literal>', + '<literal>e</literal>', and '<literal>é</literal>') are treated + as the same character. </para> </section> @@ -3258,12 +3262,13 @@ <para> As a convenience, MySQL automatically converts a date to a number if the date is used in a numeric context (and vice - versa). It is also smart enough to allow a ``relaxed'' string - form when updating and in a <literal>WHERE</literal> clause that - compares a date to a <literal>TIMESTAMP</literal>, - <literal>DATE</literal>, or <literal>DATETIME</literal> column. - (``Relaxed form'' means that any punctuation character may be - used as the separator between parts. For example, + versa). It is also smart enough to allow a + <quote>relaxed</quote> string form when updating and in a + <literal>WHERE</literal> clause that compares a date to a + <literal>TIMESTAMP</literal>, <literal>DATE</literal>, or + <literal>DATETIME</literal> column. (<quote>Relaxed form</quote> + means that any punctuation character may be used as the + separator between parts. For example, <literal>'2004-08-15'</literal> and <literal>'2004#08#15'</literal> are equivalent.) MySQL can also convert a string containing no separators (such as @@ -3280,8 +3285,8 @@ <literal>></literal>, or <literal>BETWEEN</literal> operators, MySQL normally converts the string to an internal long integer for faster comparision (and also for a bit more - ``relaxed'' string checking). However, this conversion is - subject to the following exceptions: + <quote>relaxed</quote> string checking). However, this + conversion is subject to the following exceptions: </para> <itemizedlist> @@ -3390,9 +3395,9 @@ <para> If you are not using the <literal>NO_ZERO_DATE</literal> SQL mode, MySQL also allows you to store - <literal>'0000-00-00'</literal> as a ``dummy date.'' This is in - some cases more convenient than using <literal>NULL</literal> - values. + <literal>'0000-00-00'</literal> as a <quote>dummy date.</quote> + This is in some cases more convenient than using + <literal>NULL</literal> values. </para> <para> @@ -3451,9 +3456,9 @@ Both statements insert a value into the <literal>phone</literal> column, but the first inserts a <literal>NULL</literal> value and the second inserts an empty string. The meaning of the first - can be regarded as ``phone number is not known'' and the meaning - of the second can be regarded as ``the person is known to have - no phone, and thus no phone number.'' + can be regarded as <quote>phone number is not known</quote> and + the meaning of the second can be regarded as <quote>the person + is known to have no phone, and thus no phone number.</quote> </para> <para> @@ -3521,8 +3526,8 @@ empty or missing columns are updated with <literal>''</literal>. If you want a <literal>NULL</literal> value in a column, you should use <literal>\N</literal> in the data file. The literal - word ``<literal>NULL</literal>'' may also be used under some - circumstances. See <xref linkend="load-data"/>. + word <quote><literal>NULL</literal></quote> may also be used + under some circumstances. See <xref linkend="load-data"/>. </para> <para> @@ -4004,8 +4009,8 @@ Depending on your computer architecture, you may or may not see similar results. Different CPUs may evaluate floating-point numbers differently. For example, on some machines you may get - the ``correct'' results by multiplying both arguments by 1, as - the following example shows. + the <quote>correct</quote> results by multiplying both arguments + by 1, as the following example shows. </para> <para> @@ -4084,8 +4089,8 @@ MySQL uses a cost-based optimizer to determine the best way to resolve a query. In many cases, MySQL can calculate the best possible query plan, but sometimes MySQL doesn't have enough - information about the data at hand and has to make ``educated'' - guesses about the data. + information about the data at hand and has to make + <quote>educated</quote> guesses about the data. </para> <para> @@ -4994,15 +4999,15 @@ <listitem> <para> <literal>BLOB</literal> and <literal>TEXT</literal> values - can't ``reliably'' be used in <literal>GROUP BY</literal>, - <literal>ORDER BY</literal> or <literal>DISTINCT</literal>. - Only the first <literal>max_sort_length</literal> bytes are - used when comparing <literal>BLOB</literal> values in these - cases. The default value of - <literal>max_sort_length</literal> value is 1024 and can be - changed at server startup time. As of MySQL 4.0.3, it can be - changed at runtime. For older versions, a workaround is to - use a substring. For example: + can't <quote>reliably</quote> be used in <literal>GROUP + BY</literal>, <literal>ORDER BY</literal> or + <literal>DISTINCT</literal>. Only the first + <literal>max_sort_length</literal> bytes are used when + comparing <literal>BLOB</literal> values in these cases. The + default value of <literal>max_sort_length</literal> value is + 1024 and can be changed at server startup time. As of MySQL + 4.0.3, it can be changed at runtime. For older versions, a + workaround is to use a substring. For example: </para> <programlisting> @@ -5094,13 +5099,14 @@ <listitem> <para> The optimizer may handle <literal>DISTINCT</literal> - differently when you are using ``hidden'' columns in a join - than when you are not. In a join, hidden columns are counted - as part of the result (even if they are not shown), whereas - in normal queries, hidden columns don't participate in the - <literal>DISTINCT</literal> comparison. We will probably - change this in the future to never compare the hidden - columns when executing <literal>DISTINCT</literal>. + differently when you are using <quote>hidden</quote> columns + in a join than when you are not. In a join, hidden columns + are counted as part of the result (even if they are not + shown), whereas in normal queries, hidden columns don't + participate in the <literal>DISTINCT</literal> comparison. + We will probably change this in the future to never compare + the hidden columns when executing + <literal>DISTINCT</literal>. </para> <para> --- 1.2/refman-4.1/regexp.xml 2005-07-19 11:57:24 -04:00 +++ 1.3/refman-4.1/regexp.xml 2005-07-31 11:49:56 -04:00 @@ -220,9 +220,9 @@ <para> <literal>{n}</literal> or <literal>{m,n}</literal> notation provides a more general way of writing regular expressions that - match many occurrences of the previous atom (or ``piece'') of - the pattern. <literal>m</literal> and <literal>n</literal> are - integers. + match many occurrences of the previous atom (or + <quote>piece</quote>) of the pattern. <literal>m</literal> and + <literal>n</literal> are integers. </para> <itemizedlist> --- 1.6/refman-4.1/replication.xml 2005-07-19 11:57:24 -04:00 +++ 1.7/refman-4.1/replication.xml 2005-07-31 11:49:56 -04:00 @@ -683,8 +683,8 @@ <listitem> <para> When the size of the current relay log file becomes too - large. The meaning of ``too large'' is determined as - follows: + large. The meaning of <quote>too large</quote> is determined + as follows: </para> <itemizedlist> @@ -1936,8 +1936,9 @@ MySQL only supports one master and many slaves. Later we will add a voting algorithm to automatically change master if something goes wrong with the current master. We will also - introduce ``agent'' processes to help do load balancing by - sending <literal>SELECT</literal> queries to different slaves. + introduce <quote>agent</quote> processes to help do load + balancing by sending <literal>SELECT</literal> queries to + different slaves. </para> </listitem> @@ -2689,19 +2690,19 @@ <para> Places an upper limit on the total size of all relay logs on - the slave (a value of 0 means ``unlimited''). This is useful - for a slave server host that has limited disk space. When the - limit is reached, the I/O thread stops reading binary log - events from the master server until the SQL thread has caught - up and deleted some unused relay logs. Note that this limit is - not absolute: There are cases where the SQL thread needs more - events before it can delete relay logs. In that case, the I/O - thread exceeds the limit until it becomes possible for the SQL - thread to delete some relay logs. Not doing so would cause a - deadlock (which is what happens before MySQL 4.0.13). You - should not set <literal>--relay-log-space-limit</literal> to - less than twice the value of - <literal>--max-relay-log-size</literal> (or + the slave (a value of 0 means <quote>unlimited</quote>). This + is useful for a slave server host that has limited disk space. + When the limit is reached, the I/O thread stops reading binary + log events from the master server until the SQL thread has + caught up and deleted some unused relay logs. Note that this + limit is not absolute: There are cases where the SQL thread + needs more events before it can delete relay logs. In that + case, the I/O thread exceeds the limit until it becomes + possible for the SQL thread to delete some relay logs. Not + doing so would cause a deadlock (which is what happens before + MySQL 4.0.13). You should not set + <literal>--relay-log-space-limit</literal> to less than twice + the value of <literal>--max-relay-log-size</literal> (or <literal>--max-binlog-size</literal> if <literal>--max-relay-log-size</literal> is 0). In that case, there is a chance that the I/O thread waits for free space @@ -2755,13 +2756,14 @@ </para> <para> - The main reason for this ``just-check-the-default-database'' - behavior is that it's difficult from the statement alone to - know whether or not it should be replicated (for example, if - you are using multiple-table <literal>DELETE</literal> or - multiple-table <literal>UPDATE</literal> statements that go - across multiple databases). It's also very fast to just check - the default database. + The main reason for this + <quote>just-check-the-default-database</quote> behavior is + that it's difficult from the statement alone to know whether + or not it should be replicated (for example, if you are using + multiple-table <literal>DELETE</literal> or multiple-table + <literal>UPDATE</literal> statements that go across multiple + databases). It's also very fast to just check the default + database. </para> </listitem> @@ -3223,10 +3225,11 @@ sales SELECT * FROM prices</literal>: only <literal>sales</literal> are compared to the rules). If several tables are to be updated (multiple-table - statement), the first matching table (matching ``do'' or - ``ignore'') wins. That is, the first table is compared to - the rules. Then, if no decision could be mad, the second - table is compared to the rules, and so forth. + statement), the first matching table (matching + <quote>do</quote> or <quote>ignore</quote>) wins. That is, + the first table is compared to the rules. Then, if no + decision could be mad, the second table is compared to the + rules, and so forth. </para> </listitem> @@ -4249,8 +4252,8 @@ If you have a repeatable test case that demonstrates the bug, please enter it into our bugs database at <ulink url="http://bugs.mysql.com/"/>. If you have a phantom - problem (one that you cannot duplicate ``at will''), use the - following procedure: + problem (one that you cannot duplicate <quote>at will</quote>), + use the following procedure: </para> <orderedlist> --- 1.4/refman-4.1/spatial-extensions-in-mysql.xml 2005-07-19 11:57:25 -04:00 +++ 1.5/refman-4.1/spatial-extensions-in-mysql.xml 2005-07-31 11:49:56 -04:00 @@ -856,8 +856,8 @@ <para> The OpenGIS specification defines a simple <literal>Surface</literal> as a geometry that consists of a - single ``patch'' that is associated with a single exterior - boundary and zero or more interior boundaries. + single <quote>patch</quote> that is associated with a single + exterior boundary and zero or more interior boundaries. </para> </listitem> @@ -1109,10 +1109,11 @@ <listitem> <para> A <literal>MultiCurve</literal> boundary is obtained by - applying the ``mod 2 union rule'' (also known as the - ``odd-even rule''): A point is in the boundary of a - <literal>MultiCurve</literal> if it is in the boundaries of - an odd number of <literal>MultiCurve</literal> elements. + applying the <quote>mod 2 union rule</quote> (also known as + the <quote>odd-even rule</quote>): A point is in the + boundary of a <literal>MultiCurve</literal> if it is in the + boundaries of an odd number of <literal>MultiCurve</literal> + elements. </para> </listitem> @@ -1493,7 +1494,7 @@ <para> The Well-Known Binary (WKB) representation for geometric values is defined by the OpenGIS specifications. It is also defined in - the ISO ``SQL/MM Part 3: Spatial'' standard. + the ISO <quote>SQL/MM Part 3: Spatial</quote> standard. </para> <para> --- 1.21/refman-4.1/sql-syntax.xml 2005-07-28 07:40:46 -04:00 +++ 1.22/refman-4.1/sql-syntax.xml 2005-07-31 11:49:57 -04:00 @@ -1438,8 +1438,8 @@ if it contains only positive values. Inserting a negative number is regarded as inserting a very large positive number. This is done to avoid precision problems when - numbers ``wrap'' over from positive to negative and also to - ensure that you don't accidentally get an + numbers <quote>wrap</quote> over from positive to negative + and also to ensure that you don't accidentally get an <literal>AUTO_INCREMENT</literal> column that contains <literal>0</literal>. </para> @@ -1589,10 +1589,10 @@ <para> For date and time types other than <literal>TIMESTAMP</literal>, the default is the - appropriate ``zero'' value for the type. For the first - <literal>TIMESTAMP</literal> column in a table, the - default value is the current date and time. See - <xref linkend="date-and-time-types"/>. + appropriate <quote>zero</quote> value for the type. For + the first <literal>TIMESTAMP</literal> column in a + table, the default value is the current date and time. + See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -2335,17 +2335,18 @@ <para> This means that if you have many equal keys on two - consecutive rows, all following ``same'' keys usually only - take two bytes (including the pointer to the row). Compare - this to the ordinary case where the following keys takes - <literal>storage_size_for_key + pointer_size</literal> - (where the pointer size is usually 4). Conversely, you get a - big benefit from prefix compression only if you have many - numbers that are the same. If all keys are totally - different, you use one byte more per key, if the key isn't a - key that can have <literal>NULL</literal> values. (In this - case, the packed key length is stored in the same byte that - is used to mark if a key is <literal>NULL</literal>.) + consecutive rows, all following <quote>same</quote> keys + usually only take two bytes (including the pointer to the + row). Compare this to the ordinary case where the following + keys takes <literal>storage_size_for_key + + pointer_size</literal> (where the pointer size is usually + 4). Conversely, you get a big benefit from prefix + compression only if you have many numbers that are the same. + If all keys are totally different, you use one byte more per + key, if the key isn't a key that can have + <literal>NULL</literal> values. (In this case, the packed + key length is stored in the same byte that is used to mark + if a key is <literal>NULL</literal>.) </para> </listitem> @@ -4299,16 +4300,16 @@ ... SELECT</literal> statements, the column is set to the implicit default value for the column data type. This is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' - value for date and time types. <literal>INSERT INTO ... - SELECT</literal> statements are handled the same way as - multiple-row inserts because the server does not examine the - result set from the <literal>SELECT</literal> to see whether - it returns a single row. (For a single-row - <literal>INSERT</literal>, no warning occurs when - <literal>NULL</literal> is inserted into a <literal>NOT - NULL</literal> column. Instead, the statement fails with an - error.) + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. + <literal>INSERT INTO ... SELECT</literal> statements are + handled the same way as multiple-row inserts because the + server does not examine the result set from the + <literal>SELECT</literal> to see whether it returns a single + row. (For a single-row <literal>INSERT</literal>, no warning + occurs when <literal>NULL</literal> is inserted into a + <literal>NOT NULL</literal> column. Instead, the statement + fails with an error.) </para> </listitem> @@ -4616,10 +4617,11 @@ The following describes in detail what happens when you use the <literal>DELAYED</literal> option to <literal>INSERT</literal> or <literal>REPLACE</literal>. In - this description, the ``thread'' is the thread that received - an <literal>INSERT DELAYED</literal> statement and ``handler'' - is the thread that handles all <literal>INSERT - DELAYED</literal> statements for a particular table. + this description, the <quote>thread</quote> is the thread that + received an <literal>INSERT DELAYED</literal> statement and + <quote>handler</quote> is the thread that handles all + <literal>INSERT DELAYED</literal> statements for a particular + table. </para> <itemizedlist> @@ -5509,10 +5511,10 @@ is used. With fixed-row format, no delimiters are used between fields (but you can still have a line terminator). Instead, column values are written and read using the - ``display'' widths of the columns. For example, if a column - is declared as <literal>INT(7)</literal>, values for the - column are written using seven-character fields. On input, - values for the column are obtained by reading seven + <quote>display</quote> widths of the columns. For example, + if a column is declared as <literal>INT(7)</literal>, values + for the column are written using seven-character fields. On + input, values for the column are obtained by reading seven characters. </para> @@ -5698,7 +5700,7 @@ <listitem> <para> For date and time types, the column is set to the - appropriate ``zero'' value for the type. See + appropriate <quote>zero</quote> value for the type. See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -7431,7 +7433,8 @@ <para> They are, in many people's opinion, readable. Indeed, it was the innovation of subqueries that gave people the original - idea of calling the early SQL ``Structured Query Language.'' + idea of calling the early SQL <quote>Structured Query + Language.</quote> </para> </listitem> @@ -7658,10 +7661,11 @@ <para> The <literal>ANY</literal> keyword, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ANY</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ANY</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7712,12 +7716,12 @@ <para> Use of the word <literal>SOME</literal> is rare, but this example shows why it might be useful. To most people's ears, - the English phrase ``a is not equal to any b'' means ``there - is no b which is equal to a,'' but that isn't what is meant by - the SQL syntax. The syntax means ``there is some b to which a - is not equal.'' Using <literal><> SOME</literal> instead - helps ensure that everyone understands the true meaning of the - query. + the English phrase <quote>a is not equal to any b</quote> + means <quote>there is no b which is equal to a,</quote> but + that isn't what is meant by the SQL syntax. The syntax means + <quote>there is some b to which a is not equal.</quote> Using + <literal><> SOME</literal> instead helps ensure that + everyone understands the true meaning of the query. </para> </section> @@ -7736,10 +7740,11 @@ <para> The word <literal>ALL</literal>, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ALL</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ALL</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7854,9 +7859,9 @@ <para> The normal use of row constructors, though, is for comparisons with subqueries that return two or more columns. For example, - the following query answers the request, ``find all rows in - table <literal>t1</literal> that also exist in table - <literal>t2</literal>'': + the following query answers the request, <quote>find all rows + in table <literal>t1</literal> that also exist in table + <literal>t2</literal></quote>: </para> <programlisting> @@ -7948,11 +7953,11 @@ The last example is a double-nested <literal>NOT EXISTS</literal> query. That is, it has a <literal>NOT EXISTS</literal> clause within a <literal>NOT EXISTS</literal> - clause. Formally, it answers the question ``does a city exist - with a store that is not in <literal>Stores</literal>?'' But - it's easier to say that a nested <literal>NOT EXISTS</literal> - answers the question ``is x <literal>TRUE</literal> for all - y?'' + clause. Formally, it answers the question <quote>does a city + exist with a store that is not in + <literal>Stores</literal>?</quote> But it's easier to say that + a nested <literal>NOT EXISTS</literal> answers the question + <quote>is x <literal>TRUE</literal> for all y?</quote> </para> </section> @@ -8071,8 +8076,8 @@ <literal>FROM</literal> clause must have a name. Any columns in the <replaceable>subquery</replaceable> select list must have unique names. You can find this syntax described - elsewhere in this manual, where the term used is ``derived - tables.'' + elsewhere in this manual, where the term used is + <quote>derived tables.</quote> </para> <!-- TODO: figure out what the "elsewhere" in previous sentence refers to. --> @@ -8521,10 +8526,11 @@ </itemizedlist> <para> - There is a chapter titled ``How MySQL Transforms Subqueries'' - in the MySQL Internals Manual. You can obtain this document by - downloading the MySQL source package and looking for a file - named <filename>internals.texi</filename> in the + There is a chapter titled <quote>How MySQL Transforms + Subqueries</quote> in the MySQL Internals Manual. You can + obtain this document by downloading the MySQL source package + and looking for a file named + <filename>internals.texi</filename> in the <filename>Docs</filename> directory. </para> @@ -8872,8 +8878,8 @@ is set to the default value appropriate for the column type and the warning count is incremented. The default value is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' value - for date and time types. + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. </para> <indexterm type="function"> @@ -10489,7 +10495,7 @@ </row> <row> <entry><literal>USAGE</literal></entry> - <entry>Synonym for ``no privileges''</entry> + <entry>Synonym for <quote>no privileges</quote></entry> </row> <row> <entry><literal>GRANT OPTION</literal></entry> @@ -11686,10 +11692,11 @@ <para> <emphasis role="bold">Note</emphasis>: In some cases, <literal>CHECK TABLE</literal> changes the table. This happens - if the table is marked as ``corrupted'' or ``not closed - properly'' but <literal>CHECK TABLE</literal> doesn't find any - problems in the table. In this case, <literal>CHECK - TABLE</literal> marks the table as okay. + if the table is marked as <quote>corrupted</quote> or + <quote>not closed properly</quote> but <literal>CHECK + TABLE</literal> doesn't find any problems in the table. In + this case, <literal>CHECK TABLE</literal> marks the table as + okay. </para> <para> @@ -11706,8 +11713,9 @@ can take the very small risk that <literal>QUICK</literal> doesn't find an error in the data file. (In most cases, MySQL should find, under normal usage, any error in the data file. - If this happens, the table is marked as ``corrupted'' and - cannot be used until it's repaired.) + If this happens, the table is marked as + <quote>corrupted</quote> and cannot be used until it's + repaired.) </para> <para> @@ -12765,9 +12773,9 @@ <para> The maximum number of records to return from <literal>SELECT</literal> statements. The default value for - a new connection is ``unlimited.'' If you have changed the - limit, the default value can be restored by using a - <literal>SQL_SELECT_LIMIT</literal> value of + a new connection is <quote>unlimited.</quote> If you have + changed the limit, the default value can be restored by + using a <literal>SQL_SELECT_LIMIT</literal> value of <literal>DEFAULT</literal>. </para> @@ -17023,7 +17031,7 @@ <para> The error number and error message returned by the most recently executed query. An error number of 0 and message - of the empty string mean ``no error.'' If the + of the empty string mean <quote>no error.</quote> If the <literal>Last_Error</literal> value is not empty, it also appears as a message in the slave's error log. </para> @@ -17208,12 +17216,12 @@ This field is present beginning with MySQL 4.1.1. It's been experimental and has been changed in MySQL 4.1.9. The following applies to slaves running MySQL 4.1.9 or newer. - This field is an indication of how ``late'' the slave is. - When the slave SQL thread is actively running (processing - updates), this field is the number of seconds that have - elapsed since the timestamp of the last master's event - executed by that thread. When that thread has caught up on - the slave I/O thread and goes idle waiting from more + This field is an indication of how <quote>late</quote> the + slave is. When the slave SQL thread is actively running + (processing updates), this field is the number of seconds + that have elapsed since the timestamp of the last master's + event executed by that thread. When that thread has caught + up on the slave I/O thread and goes idle waiting from more events from the I/O thread this field is zero. To sum up, this field measures in seconds the time difference between the slave SQL thread and the slave I/O thread. @@ -17239,14 +17247,14 @@ difference is computed when the slave I/O thread starts, and assumed to remain constant from then on). <literal>Seconds_Behind_Master</literal> is - <literal>NULL</literal> (which means ``unknown'') if the - slave SQL thread is not running, or if the slave I/O - thread is not running or not connected to master. For - example if the slave I/O thread is sleeping for - <literal>master-connect-retry</literal> seconds before - reconnecting, <literal>NULL</literal> is shown, as the - slave cannot know what the master is doing, and thus - cannot reliably say how late it is. + <literal>NULL</literal> (which means + <quote>unknown</quote>) if the slave SQL thread is not + running, or if the slave I/O thread is not running or not + connected to master. For example if the slave I/O thread + is sleeping for <literal>master-connect-retry</literal> + seconds before reconnecting, <literal>NULL</literal> is + shown, as the slave cannot know what the master is doing, + and thus cannot reliably say how late it is. </para> <para> --- 1.8/refman-4.1/storage-engines.xml 2005-07-29 13:18:54 -04:00 +++ 1.9/refman-4.1/storage-engines.xml 2005-07-31 11:49:57 -04:00 @@ -183,12 +183,12 @@ <listitem> <para> The <literal>EXAMPLE</literal> storage engine was added in MySQL - 4.1.3. It is a ``stub'' engine that does nothing. You can create - tables with this engine, but no data can be stored into them or - retrieved from them. The purpose of this engine is to serve as - an example in the MySQL source code that illustrates how to - begin writing new storage engines. As such, it is primarily of - interest to developers. + 4.1.3. It is a <quote>stub</quote> engine that does nothing. You + can create tables with this engine, but no data can be stored + into them or retrieved from them. The purpose of this engine is + to serve as an example in the MySQL source code that illustrates + how to begin writing new storage engines. As such, it is + primarily of interest to developers. </para> </listitem> @@ -1598,12 +1598,13 @@ <para> A <literal>MERGE</literal> table is a collection of identical <literal>MyISAM</literal> tables that can be used as one. - ``Identical'' means that all tables have identical column and - index information. You can't merge tables in which the columns are - listed in a different order, don't have exactly the same columns, - or have the indexes in different order. However, any or all of the - tables can be compressed with <command>myisampack</command>. See - <xref linkend="myisampack"/>. Differences in table options such as + <quote>Identical</quote> means that all tables have identical + column and index information. You can't merge tables in which the + columns are listed in a different order, don't have exactly the + same columns, or have the indexes in different order. However, any + or all of the tables can be compressed with + <command>myisampack</command>. See <xref linkend="myisampack"/>. + Differences in table options such as <literal>AVG_ROW_LENGTH</literal>, <literal>MAX_ROWS</literal>, or <literal>PACK_KEYS</literal> do not matter. @@ -1863,11 +1864,11 @@ <listitem> <para> - If the <literal>MERGE</literal> table is non-temporary, - all underlying <literal>MyISAM</literal> tables have to be + If the <literal>MERGE</literal> table is non-temporary, all + underlying <literal>MyISAM</literal> tables have to be permanent, too. If the <literal>MERGE</literal> table is - temporary, the <literal>MyISAM</literal> tables can be any - mix of temporary and non-temporary. + temporary, the <literal>MyISAM</literal> tables can be any mix + of temporary and non-temporary. </para> </listitem> @@ -1887,11 +1888,12 @@ Key reads are slower. When you read a key, the <literal>MERGE</literal> storage engine needs to issue a read on all underlying tables to check which one most closely - matches the given key. If you then do a ``read-next,'' the - <literal>MERGE</literal> storage engine needs to search the - read buffers to find the next key. Only when one key buffer is - used up, the storage engine needs to read the next key block. - This makes <literal>MERGE</literal> keys much slower on + matches the given key. If you then do a + <quote>read-next,</quote> the <literal>MERGE</literal> storage + engine needs to search the read buffers to find the next key. + Only when one key buffer is used up, the storage engine needs + to read the next key block. This makes + <literal>MERGE</literal> keys much slower on <literal>eq_ref</literal> searches, but not much slower on <literal>ref</literal> searches. See <xref linkend="explain"/> for more information about <literal>eq_ref</literal> and @@ -1945,12 +1947,12 @@ TABLE</literal>, <literal>TRUNCATE TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, or <literal>ANALYZE TABLE</literal> on any of the tables that are mapped into a - <literal>MERGE</literal> table that is ``open.'' If you do - this, the <literal>MERGE</literal> table may still refer to - the original table and you get unexpected results. The - easiest way to work around this deficiency is to issue a + <literal>MERGE</literal> table that is <quote>open.</quote> + If you do this, the <literal>MERGE</literal> table may still + refer to the original table and you get unexpected results. + The easiest way to work around this deficiency is to issue a <literal>FLUSH TABLES</literal> statement to ensure that no - <literal>MERGE</literal> tables remain ``open.'' + <literal>MERGE</literal> tables remain <quote>open.</quote> </para> </listitem> @@ -3187,10 +3189,10 @@ <para> The <literal>EXAMPLE</literal> storage engine was added in MySQL - 4.1.3. It is a ``stub'' engine that does nothing. Its purpose is - to serve as an example in the MySQL source code that illustrates - how to begin writing new storage engines. As such, it is primarily - of interest to developers. + 4.1.3. It is a <quote>stub</quote> engine that does nothing. Its + purpose is to serve as an example in the MySQL source code that + illustrates how to begin writing new storage engines. As such, it + is primarily of interest to developers. </para> <para> @@ -3409,8 +3411,8 @@ <para> Next, create a <literal>FEDERATED</literal> table for accessing the remote table. The server where you create the - <literal>FEDERATED</literal> table is the ``client server.'' On - this server, create the table as follows: + <literal>FEDERATED</literal> table is the <quote>client + server.</quote> On this server, create the table as follows: </para> <programlisting> @@ -3444,12 +3446,12 @@ <para> The remote host information indicates the remote server to which - your ``client'' server connects, and the database and table - information indicates which remote table to use as the ``data - file.'' In the example, the remote server is indicated to be - running as <literal>remote_host</literal> on port 9306, so you - want to start that server so that it is indeed listening to port - 9306. + your <quote>client</quote> server connects, and the database and + table information indicates which remote table to use as the + <quote>data file.</quote> In the example, the remote server is + indicated to be running as <literal>remote_host</literal> on + port 9306, so you want to start that server so that it is indeed + listening to port 9306. </para> <para> --- 1.7/refman-4.1/tutorial.xml 2005-07-19 11:57:27 -04:00 +++ 1.8/refman-4.1/tutorial.xml 2005-07-31 11:49:57 -04:00 @@ -34,12 +34,13 @@ This chapter provides a tutorial introduction to MySQL by showing how to use the <command>mysql</command> client program to create and use a simple database. <command>mysql</command> (sometimes referred - to as the ``terminal monitor'' or just ``monitor'') is an - interactive program that allows you to connect to a MySQL server, - run queries, and view the results. <command>mysql</command> may also - be used in batch mode: you place your queries in a file beforehand, - then tell <command>mysql</command> to execute the contents of the - file. Both ways of using <command>mysql</command> are covered here. + to as the <quote>terminal monitor</quote> or just + <quote>monitor</quote>) is an interactive program that allows you to + connect to a MySQL server, run queries, and view the results. + <command>mysql</command> may also be used in batch mode: you place + your queries in a file beforehand, then tell + <command>mysql</command> to execute the contents of the file. Both + ways of using <command>mysql</command> are covered here. </para> <para> @@ -269,8 +270,8 @@ idea of server performance. These values are imprecise because they represent wall clock time (not CPU or machine time), and because they are affected by factors such as server load and - network latency. (For brevity, the ``rows in set'' line is not - shown in the remaining examples in this chapter.) + network latency. (For brevity, the <quote>rows in set</quote> + line is not shown in the remaining examples in this chapter.) </para> </listitem> @@ -1198,9 +1199,10 @@ <para> <literal>what_to_select</literal> indicates what you want to see. This can be a list of columns, or <literal>*</literal> to - indicate ``all columns.'' <literal>which_table</literal> - indicates the table from which you want to retrieve data. The - <literal>WHERE</literal> clause is optional. If it's present, + indicate <quote>all columns.</quote> + <literal>which_table</literal> indicates the table from which + you want to retrieve data. The <literal>WHERE</literal> clause + is optional. If it's present, <literal>conditions_to_satisfy</literal> specifies conditions that rows must satisfy to qualify for retrieval. </para> @@ -2269,8 +2271,8 @@ <para> You could also write the previous query using the - '<literal>{n}</literal>' ``repeat-<literal>n</literal>-times'' - operator: + '<literal>{n}</literal>' + <quote>repeat-<literal>n</literal>-times</quote> operator: </para> <programlisting> @@ -2305,19 +2307,19 @@ </indexterm> <para> - Databases are often used to answer the question, ``How often - does a certain type of data occur in a table?'' For example, - you might want to know how many pets you have, or how many - pets each owner has, or you might want to perform various - kinds of census operations on your animals. + Databases are often used to answer the question, <quote>How + often does a certain type of data occur in a table?</quote> + For example, you might want to know how many pets you have, or + how many pets each owner has, or you might want to perform + various kinds of census operations on your animals. </para> <para> Counting the total number of animals you have is the same - question as ``How many rows are in the <literal>pet</literal> - table?'' because there is one record per pet. - <literal>COUNT(*)</literal> counts the number of rows, so the - query to count your animals looks like this: + question as <quote>How many rows are in the + <literal>pet</literal> table?</quote> because there is one + record per pet. <literal>COUNT(*)</literal> counts the number + of rows, so the query to count your animals looks like this: </para> <programlisting> @@ -3093,7 +3095,7 @@ <title id='title-example-maximum-column'>&title-example-maximum-column;</title> <para> - ``What's the highest item number?'' + <quote>What's the highest item number?</quote> </para> <programlisting> @@ -3113,8 +3115,8 @@ <title id='title-example-maximum-row'>&title-example-maximum-row;</title> <para> - ``Find number, dealer, and price of the most expensive - article.'' + <quote>Find number, dealer, and price of the most expensive + article.</quote> </para> <para> @@ -3197,7 +3199,7 @@ <title id='title-example-maximum-column-group'>&title-example-maximum-column-group;</title> <para> - ``What's the highest price per article?'' + <quote>What's the highest price per article?</quote> </para> <programlisting> @@ -3222,8 +3224,8 @@ <title id='title-example-maximum-column-group-row'>&title-example-maximum-column-group-row;</title> <para> - ``For each article, find the dealer or dealers with the most - expensive price.'' + <quote>For each article, find the dealer or dealers with the + most expensive price.</quote> </para> <para> @@ -3288,12 +3290,12 @@ </para> <para> - ``Can it be done with a single query?'' + <quote>Can it be done with a single query?</quote> </para> <para> Yes, but only by using a quite inefficient trick called the - ``MAX-CONCAT trick'': + <quote>MAX-CONCAT trick</quote>: </para> <programlisting> --- 1.3/refman-4.1/using-mysql-programs.xml 2005-07-19 11:57:27 -04:00 +++ 1.4/refman-4.1/using-mysql-programs.xml 2005-07-31 11:49:57 -04:00 @@ -219,10 +219,10 @@ shell or command prompt), enter the program name followed by any options or other arguments needed to instruct the program what you want it to do. The following commands show some sample program - invocations. ``<literal>shell></literal>'' represents the - prompt for your command interpreter; it is not part of what you - type. The particular prompt you see depends on your command - interpreter. Typical prompts are <literal>$</literal> for + invocations. <quote><literal>shell></literal></quote> + represents the prompt for your command interpreter; it is not part + of what you type. The particular prompt you see depends on your + command interpreter. Typical prompts are <literal>$</literal> for <command>sh</command> or <command>bash</command>, <literal>%</literal> for <command>csh</command> or <command>tcsh</command>, and <literal>C:\></literal> for @@ -283,12 +283,13 @@ You may find it necessary to invoke MySQL programs using the pathname to the <filename>bin</filename> directory in which they are installed. This is likely to be the case if you get a - ``program not found'' error whenever you attempt to run a MySQL - program from any directory other than the <filename>bin</filename> - directory. To make it more convenient to use MySQL, you can add - the pathname of the <filename>bin</filename> directory to your - <literal>PATH</literal> environment variable setting. Then to run - a program you need only type its name, not its entire pathname. + <quote>program not found</quote> error whenever you attempt to run + a MySQL program from any directory other than the + <filename>bin</filename> directory. To make it more convenient to + use MySQL, you can add the pathname of the + <filename>bin</filename> directory to your <literal>PATH</literal> + environment variable setting. Then to run a program you need only + type its name, not its entire pathname. </para> <para> @@ -449,13 +450,13 @@ <para> MySQL 4.0 introduced some additional flexibility in the way you specify options. These changes were made in MySQL 4.0.2. Some of - them relate to the way you specify options that have ``enabled'' - and ``disabled'' states, and to the use of options that might be - present in one version of MySQL but not another. Those - capabilities are discussed in this section. Another change - pertains to the way you use options to set program variables. - <xref linkend="program-variables"/> discusses that topic - further. + them relate to the way you specify options that have + <quote>enabled</quote> and <quote>disabled</quote> states, and + to the use of options that might be present in one version of + MySQL but not another. Those capabilities are discussed in this + section. Another change pertains to the way you use options to + set program variables. <xref linkend="program-variables"/> + discusses that topic further. </para> <!-- TODO: also: can specify unambigious prefix of option - hm, but that's --> @@ -491,8 +492,8 @@ </para> <para> - The ``enabled'' form of the option may be specified in any of - these ways: + The <quote>enabled</quote> form of the option may be specified + in any of these ways: </para> <programlisting> --- 1.6/refman-5.0/mysql-connectors.xml 2005-07-27 13:13:26 -04:00 +++ 1.7/refman-5.0/mysql-connectors.xml 2005-07-31 11:49:58 -04:00 @@ -931,9 +931,10 @@ most cases, you can continue by pressing <literal>Ignore</literal> to copy the rest of the MyODBC files and the final installation should still work. If it doesn't, the - solution is to re-boot your computer in ``safe mode.'' Choose - safe mode by pressing F8 just before your machine starts Windows - during re-booting, install MyODBC, and re-boot to normal mode. + solution is to re-boot your computer in <quote>safe + mode.</quote> Choose safe mode by pressing F8 just before your + machine starts Windows during re-booting, install MyODBC, and + re-boot to normal mode. </para> </section> @@ -2640,9 +2641,9 @@ <row> <entry>2</entry> <entry>The client can't handle that MySQL returns the true value of affected - rows. If this flag is set, MySQL returns ``found - rows'' instead. You must have MySQL 3.21.14 or newer - to get this to work.</entry> + rows. If this flag is set, MySQL returns <quote>found + rows</quote> instead. You must have MySQL 3.21.14 or + newer to get this to work.</entry> </row> <row> <entry>4</entry> @@ -3905,7 +3906,7 @@ <para> The purpose of <literal>CONCAT()</literal> in this example is to fool ODBC into thinking the column is - of ``string type.'' Without the + of <quote>string type.</quote> Without the <literal>CONCAT()</literal>, ODBC knows the column is of time type, and Excel does not understand that. </para> @@ -4843,7 +4844,8 @@ <title id='title-trapping-odbc-errors'>&title-trapping-odbc-errors;</title> <para> - Read ``How to Trap ODBC Login Error Messages in Access'' at + Read <quote>How to Trap ODBC Login Error Messages in + Access</quote> at <ulink url="http://support.microsoft.com/support/kb/articles/Q124/9/01.asp?LN=EN-US&SD=gn&FR=0%3CP%3E"/>. </para> @@ -4919,7 +4921,8 @@ <title id='title-query-timeout'>&title-query-timeout;</title> <para> - Read ``Set the QueryTimeout Value for ODBC Connections'' at + Read <quote>Set the QueryTimeout Value for ODBC + Connections</quote> at <ulink url="http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B153756"/>. </para> @@ -7534,7 +7537,7 @@ </section> - <xi:include href="../Docs/connector-net.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="../Docs/connector-net.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="../Docs/connector-j-en.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> --- 1.9/refman-5.0/problems.xml 2005-07-19 22:54:55 -04:00 +++ 1.10/refman-5.0/problems.xml 2005-07-31 11:49:58 -04:00 @@ -155,15 +155,16 @@ happening. You should also state why you think that MySQL is causing the problem. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you - examine your system. Use the ``copy and paste'' method for any - output and error messages from programs and log files. + examine your system. Use the <quote>copy and paste</quote> method + for any output and error messages from programs and log files. </para> <para> Try to describe in detail which program is not working and all symptoms you see. We have in the past received many bug reports - that state only ``the system doesn't work.'' This doesn't provide - us with any information about what could be the problem. + that state only <quote>the system doesn't work.</quote> This + doesn't provide us with any information about what could be the + problem. </para> <para> @@ -553,9 +554,9 @@ <para> Substitute the password you want to use for - ``<replaceable>newpwd</replaceable>'' in the preceding - examples. MySQL cannot tell you what the original password - was, so you'll need to pick a new one. + <quote><replaceable>newpwd</replaceable></quote> in the + preceding examples. MySQL cannot tell you what the original + password was, so you'll need to pick a new one. </para> </listitem> @@ -1792,8 +1793,8 @@ <literal>--open-files-limit</literal> and <command>ulimit</command> can increase the number of file descriptors, but only up to the limit imposed by the operating - system. There is also a ``hard'' limit that can be overridden - only if you start <command>mysqld_safe</command> or + system. There is also a <quote>hard</quote> limit that can be + overridden only if you start <command>mysqld_safe</command> or <command>mysqld</command> as <literal>root</literal> (just remember that you also need to start the server with the <literal>--user</literal> option in this case so that it does @@ -2457,9 +2458,9 @@ </para> <para> - Replace ``<replaceable>newpwd</replaceable>'' with the - actual <literal>root</literal> password that you want to - use. + Replace <quote><replaceable>newpwd</replaceable></quote> + with the actual <literal>root</literal> password that you + want to use. </para> </listitem> @@ -2824,16 +2825,17 @@ <para> This section describes how MySQL responds to disk-full errors - (such as ``no space left on device''), and, as of MySQL 4.0.22, - to quota-exceeded errors (such as ``write failed'' or ``user - block limit reached"). + (such as <quote>no space left on device</quote>), and, as of + MySQL 4.0.22, to quota-exceeded errors (such as <quote>write + failed</quote> or <quote>user block limit reached</quote>). </para> <para> This section is relevant for writes to <literal>MyISAM</literal> tables. As of MySQL 4.1.9, it also applies for writes to binary log files and binary log index file, except that references to - ``row'' and ``record'' should be understood to mean ``event.'' + <quote>row</quote> and <quote>record</quote> should be + understood to mean <quote>event.</quote> </para> <para> @@ -2883,9 +2885,10 @@ <listitem> <para> Other threads might be waiting for the table that caused the - disk-full condition. If you have several ``locked'' threads, - killing the one thread that is waiting on the disk-full - condition allows the other threads to continue. + disk-full condition. If you have several + <quote>locked</quote> threads, killing the one thread that + is waiting on the disk-full condition allows the other + threads to continue. </para> </listitem> @@ -3219,9 +3222,10 @@ <para> Simple comparison operations (<literal>>=, >, =, <, <=</literal>, sorting, and grouping) are based on each - character's ``sort value.'' Characters with the same sort value - (such as '<literal>E</literal>', '<literal>e</literal>', and - '<literal>é</literal>') are treated as the same character. + character's <quote>sort value.</quote> Characters with the same + sort value (such as '<literal>E</literal>', + '<literal>e</literal>', and '<literal>é</literal>') are treated + as the same character. </para> </section> @@ -3260,12 +3264,13 @@ <para> As a convenience, MySQL automatically converts a date to a number if the date is used in a numeric context (and vice - versa). It is also smart enough to allow a ``relaxed'' string - form when updating and in a <literal>WHERE</literal> clause that - compares a date to a <literal>TIMESTAMP</literal>, - <literal>DATE</literal>, or <literal>DATETIME</literal> column. - (``Relaxed form'' means that any punctuation character may be - used as the separator between parts. For example, + versa). It is also smart enough to allow a + <quote>relaxed</quote> string form when updating and in a + <literal>WHERE</literal> clause that compares a date to a + <literal>TIMESTAMP</literal>, <literal>DATE</literal>, or + <literal>DATETIME</literal> column. (<quote>Relaxed form</quote> + means that any punctuation character may be used as the + separator between parts. For example, <literal>'2004-08-15'</literal> and <literal>'2004#08#15'</literal> are equivalent.) MySQL can also convert a string containing no separators (such as @@ -3282,8 +3287,8 @@ <literal>></literal>, or <literal>BETWEEN</literal> operators, MySQL normally converts the string to an internal long integer for faster comparision (and also for a bit more - ``relaxed'' string checking). However, this conversion is - subject to the following exceptions: + <quote>relaxed</quote> string checking). However, this + conversion is subject to the following exceptions: </para> <itemizedlist> @@ -3392,9 +3397,9 @@ <para> If you are not using the <literal>NO_ZERO_DATE</literal> SQL mode, MySQL also allows you to store - <literal>'0000-00-00'</literal> as a ``dummy date.'' This is in - some cases more convenient than using <literal>NULL</literal> - values. + <literal>'0000-00-00'</literal> as a <quote>dummy date.</quote> + This is in some cases more convenient than using + <literal>NULL</literal> values. </para> <para> @@ -3453,9 +3458,9 @@ Both statements insert a value into the <literal>phone</literal> column, but the first inserts a <literal>NULL</literal> value and the second inserts an empty string. The meaning of the first - can be regarded as ``phone number is not known'' and the meaning - of the second can be regarded as ``the person is known to have - no phone, and thus no phone number.'' + can be regarded as <quote>phone number is not known</quote> and + the meaning of the second can be regarded as <quote>the person + is known to have no phone, and thus no phone number.</quote> </para> <para> @@ -3523,8 +3528,8 @@ empty or missing columns are updated with <literal>''</literal>. If you want a <literal>NULL</literal> value in a column, you should use <literal>\N</literal> in the data file. The literal - word ``<literal>NULL</literal>'' may also be used under some - circumstances. See <xref linkend="load-data"/>. + word <quote><literal>NULL</literal></quote> may also be used + under some circumstances. See <xref linkend="load-data"/>. </para> <para> @@ -4006,8 +4011,8 @@ Depending on your computer architecture, you may or may not see similar results. Different CPUs may evaluate floating-point numbers differently. For example, on some machines you may get - the ``correct'' results by multiplying both arguments by 1, as - the following example shows. + the <quote>correct</quote> results by multiplying both arguments + by 1, as the following example shows. </para> <para> @@ -4086,8 +4091,8 @@ MySQL uses a cost-based optimizer to determine the best way to resolve a query. In many cases, MySQL can calculate the best possible query plan, but sometimes MySQL doesn't have enough - information about the data at hand and has to make ``educated'' - guesses about the data. + information about the data at hand and has to make + <quote>educated</quote> guesses about the data. </para> <para> @@ -4996,15 +5001,15 @@ <listitem> <para> <literal>BLOB</literal> and <literal>TEXT</literal> values - can't ``reliably'' be used in <literal>GROUP BY</literal>, - <literal>ORDER BY</literal> or <literal>DISTINCT</literal>. - Only the first <literal>max_sort_length</literal> bytes are - used when comparing <literal>BLOB</literal> values in these - cases. The default value of - <literal>max_sort_length</literal> value is 1024 and can be - changed at server startup time. As of MySQL 4.0.3, it can be - changed at runtime. For older versions, a workaround is to - use a substring. For example: + can't <quote>reliably</quote> be used in <literal>GROUP + BY</literal>, <literal>ORDER BY</literal> or + <literal>DISTINCT</literal>. Only the first + <literal>max_sort_length</literal> bytes are used when + comparing <literal>BLOB</literal> values in these cases. The + default value of <literal>max_sort_length</literal> value is + 1024 and can be changed at server startup time. As of MySQL + 4.0.3, it can be changed at runtime. For older versions, a + workaround is to use a substring. For example: </para> <programlisting> @@ -5096,13 +5101,14 @@ <listitem> <para> The optimizer may handle <literal>DISTINCT</literal> - differently when you are using ``hidden'' columns in a join - than when you are not. In a join, hidden columns are counted - as part of the result (even if they are not shown), whereas - in normal queries, hidden columns don't participate in the - <literal>DISTINCT</literal> comparison. We will probably - change this in the future to never compare the hidden - columns when executing <literal>DISTINCT</literal>. + differently when you are using <quote>hidden</quote> columns + in a join than when you are not. In a join, hidden columns + are counted as part of the result (even if they are not + shown), whereas in normal queries, hidden columns don't + participate in the <literal>DISTINCT</literal> comparison. + We will probably change this in the future to never compare + the hidden columns when executing + <literal>DISTINCT</literal>. </para> <para> --- 1.2/refman-5.0/regexp.xml 2005-07-19 11:57:35 -04:00 +++ 1.3/refman-5.0/regexp.xml 2005-07-31 11:49:58 -04:00 @@ -220,9 +220,9 @@ <para> <literal>{n}</literal> or <literal>{m,n}</literal> notation provides a more general way of writing regular expressions that - match many occurrences of the previous atom (or ``piece'') of - the pattern. <literal>m</literal> and <literal>n</literal> are - integers. + match many occurrences of the previous atom (or + <quote>piece</quote>) of the pattern. <literal>m</literal> and + <literal>n</literal> are integers. </para> <itemizedlist> --- 1.4/refman-5.0/spatial-extensions-in-mysql.xml 2005-07-19 11:57:35 -04:00 +++ 1.5/refman-5.0/spatial-extensions-in-mysql.xml 2005-07-31 11:49:58 -04:00 @@ -856,8 +856,8 @@ <para> The OpenGIS specification defines a simple <literal>Surface</literal> as a geometry that consists of a - single ``patch'' that is associated with a single exterior - boundary and zero or more interior boundaries. + single <quote>patch</quote> that is associated with a single + exterior boundary and zero or more interior boundaries. </para> </listitem> @@ -1109,10 +1109,11 @@ <listitem> <para> A <literal>MultiCurve</literal> boundary is obtained by - applying the ``mod 2 union rule'' (also known as the - ``odd-even rule''): A point is in the boundary of a - <literal>MultiCurve</literal> if it is in the boundaries of - an odd number of <literal>MultiCurve</literal> elements. + applying the <quote>mod 2 union rule</quote> (also known as + the <quote>odd-even rule</quote>): A point is in the + boundary of a <literal>MultiCurve</literal> if it is in the + boundaries of an odd number of <literal>MultiCurve</literal> + elements. </para> </listitem> @@ -1493,7 +1494,7 @@ <para> The Well-Known Binary (WKB) representation for geometric values is defined by the OpenGIS specifications. It is also defined in - the ISO ``SQL/MM Part 3: Spatial'' standard. + the ISO <quote>SQL/MM Part 3: Spatial</quote> standard. </para> <para> --- 1.31/refman-5.0/sql-syntax.xml 2005-07-30 03:47:30 -04:00 +++ 1.32/refman-5.0/sql-syntax.xml 2005-07-31 11:49:59 -04:00 @@ -1427,9 +1427,9 @@ properly only if it contains only positive values. Inserting a negative number is regarded as inserting a very large positive number. This is done to avoid precision problems - when numbers ``wrap'' over from positive to negative and - also to ensure that you don't accidentally get an - <literal>AUTO_INCREMENT</literal> column that contains + when numbers <quote>wrap</quote> over from positive to + negative and also to ensure that you don't accidentally get + an <literal>AUTO_INCREMENT</literal> column that contains <literal>0</literal>. </para> @@ -1582,10 +1582,10 @@ <para> For date and time types other than <literal>TIMESTAMP</literal>, the default is the - appropriate ``zero'' value for the type. For the first - <literal>TIMESTAMP</literal> column in a table, the - default value is the current date and time. See - <xref linkend="date-and-time-types"/>. + appropriate <quote>zero</quote> value for the type. For + the first <literal>TIMESTAMP</literal> column in a + table, the default value is the current date and time. + See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -2304,17 +2304,18 @@ <para> This means that if you have many equal keys on two - consecutive rows, all following ``same'' keys usually only - take two bytes (including the pointer to the row). Compare - this to the ordinary case where the following keys takes - <literal>storage_size_for_key + pointer_size</literal> - (where the pointer size is usually 4). Conversely, you get a - big benefit from prefix compression only if you have many - numbers that are the same. If all keys are totally - different, you use one byte more per key, if the key isn't a - key that can have <literal>NULL</literal> values. (In this - case, the packed key length is stored in the same byte that - is used to mark if a key is <literal>NULL</literal>.) + consecutive rows, all following <quote>same</quote> keys + usually only take two bytes (including the pointer to the + row). Compare this to the ordinary case where the following + keys takes <literal>storage_size_for_key + + pointer_size</literal> (where the pointer size is usually + 4). Conversely, you get a big benefit from prefix + compression only if you have many numbers that are the same. + If all keys are totally different, you use one byte more per + key, if the key isn't a key that can have + <literal>NULL</literal> values. (In this case, the packed + key length is stored in the same byte that is used to mark + if a key is <literal>NULL</literal>.) </para> </listitem> @@ -4138,16 +4139,16 @@ ... SELECT</literal> statements, the column is set to the implicit default value for the column data type. This is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' - value for date and time types. <literal>INSERT INTO ... - SELECT</literal> statements are handled the same way as - multiple-row inserts because the server does not examine the - result set from the <literal>SELECT</literal> to see whether - or not it returns a single row. (For a single-row - <literal>INSERT</literal>, no warning occurs when - <literal>NULL</literal> is inserted into a <literal>NOT - NULL</literal> column. Instead, the statement fails with an - error.) + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. + <literal>INSERT INTO ... SELECT</literal> statements are + handled the same way as multiple-row inserts because the + server does not examine the result set from the + <literal>SELECT</literal> to see whether or not it returns a + single row. (For a single-row <literal>INSERT</literal>, no + warning occurs when <literal>NULL</literal> is inserted into + a <literal>NOT NULL</literal> column. Instead, the statement + fails with an error.) </para> </listitem> @@ -4446,10 +4447,11 @@ The following describes in detail what happens when you use the <literal>DELAYED</literal> option to <literal>INSERT</literal> or <literal>REPLACE</literal>. In - this description, the ``thread'' is the thread that received - an <literal>INSERT DELAYED</literal> statement and ``handler'' - is the thread that handles all <literal>INSERT - DELAYED</literal> statements for a particular table. + this description, the <quote>thread</quote> is the thread that + received an <literal>INSERT DELAYED</literal> statement and + <quote>handler</quote> is the thread that handles all + <literal>INSERT DELAYED</literal> statements for a particular + table. </para> <itemizedlist> @@ -5614,7 +5616,7 @@ <listitem> <para> For date and time types, the column is set to the - appropriate ``zero'' value for the type. See + appropriate <quote>zero</quote> value for the type. See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -7298,7 +7300,8 @@ <para> They are, in many people's opinion, readable. Indeed, it was the innovation of subqueries that gave people the original - idea of calling the early SQL ``Structured Query Language.'' + idea of calling the early SQL <quote>Structured Query + Language.</quote> </para> </listitem> @@ -7525,10 +7528,11 @@ <para> The <literal>ANY</literal> keyword, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ANY</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ANY</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7579,12 +7583,12 @@ <para> Use of the word <literal>SOME</literal> is rare, but this example shows why it might be useful. To most people's ears, - the English phrase ``a is not equal to any b'' means ``there - is no b which is equal to a,'' but that isn't what is meant by - the SQL syntax. The syntax means ``there is some b to which a - is not equal.'' Using <literal><> SOME</literal> instead - helps ensure that everyone understands the true meaning of the - query. + the English phrase <quote>a is not equal to any b</quote> + means <quote>there is no b which is equal to a,</quote> but + that isn't what is meant by the SQL syntax. The syntax means + <quote>there is some b to which a is not equal.</quote> Using + <literal><> SOME</literal> instead helps ensure that + everyone understands the true meaning of the query. </para> </section> @@ -7603,10 +7607,11 @@ <para> The word <literal>ALL</literal>, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ALL</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ALL</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7721,9 +7726,9 @@ <para> The normal use of row constructors, though, is for comparisons with subqueries that return two or more columns. For example, - the following query answers the request, ``find all rows in - table <literal>t1</literal> that also exist in table - <literal>t2</literal>'': + the following query answers the request, <quote>find all rows + in table <literal>t1</literal> that also exist in table + <literal>t2</literal></quote>: </para> <programlisting> @@ -7816,11 +7821,12 @@ The last example is a double-nested <literal>NOT EXISTS</literal> query. That is, it has a <literal>NOT EXISTS</literal> clause within a <literal>NOT EXISTS</literal> - clause. Formally, it answers the question ``does a city exist - with a store that is not in <literal>Stores</literal>?'' - However, it's easier to say that a nested<literal>NOT - EXISTS</literal> answers the question ``is x - <literal>TRUE</literal> for all y?'' + clause. Formally, it answers the question <quote>does a city + exist with a store that is not in + <literal>Stores</literal>?</quote> However, it's easier to say + that a nested<literal>NOT EXISTS</literal> answers the + question <quote>is x <literal>TRUE</literal> for all + y?</quote> </para> </section> @@ -7939,8 +7945,8 @@ <literal>FROM</literal> clause must have a name. Any columns in the <replaceable>subquery</replaceable> select list must have unique names. You can find this syntax described - elsewhere in this manual, where the term used is ``derived - tables.'' + elsewhere in this manual, where the term used is + <quote>derived tables.</quote> </para> <!-- @@ -8369,10 +8375,11 @@ </itemizedlist> <para> - There is a chapter titled ``How MySQL Transforms Subqueries'' - in the MySQL Internals Manual. You can obtain this document by - downloading the MySQL source package and looking for a file - named <filename>internals.texi</filename> in the + There is a chapter titled <quote>How MySQL Transforms + Subqueries</quote> in the MySQL Internals Manual. You can + obtain this document by downloading the MySQL source package + and looking for a file named + <filename>internals.texi</filename> in the <filename>Docs</filename> directory. </para> @@ -8722,8 +8729,8 @@ is set to the default value appropriate for the column type and the warning count is incremented. The default value is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' value - for date and time types. + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. </para> <indexterm type="function"> @@ -10283,7 +10290,7 @@ </row> <row> <entry><literal>USAGE</literal></entry> - <entry>Synonym for ``no privileges''</entry> + <entry>Synonym for <quote>no privileges</quote></entry> </row> <row> <entry><literal>GRANT OPTION</literal></entry> @@ -11471,10 +11478,11 @@ <para> <emphasis role="bold">Note</emphasis>: In some cases, <literal>CHECK TABLE</literal> changes the table. This happens - if the table is marked as ``corrupted'' or ``not closed - properly'' but <literal>CHECK TABLE</literal> doesn't find any - problems in the table. In this case, <literal>CHECK - TABLE</literal> marks the table as okay. + if the table is marked as <quote>corrupted</quote> or + <quote>not closed properly</quote> but <literal>CHECK + TABLE</literal> doesn't find any problems in the table. In + this case, <literal>CHECK TABLE</literal> marks the table as + okay. </para> <para> @@ -11491,8 +11499,9 @@ can take the very small risk that <literal>QUICK</literal> doesn't find an error in the data file. (In most cases, MySQL should find, under normal usage, any error in the data file. - If this happens, the table is marked as ``corrupted'' and - cannot be used until it's repaired.) + If this happens, the table is marked as + <quote>corrupted</quote> and cannot be used until it's + repaired.) </para> <para> @@ -12508,9 +12517,9 @@ <para> The maximum number of records to return from <literal>SELECT</literal> statements. The default value for - a new connection is ``unlimited.'' If you have changed the - limit, the default value can be restored by using a - <literal>SQL_SELECT_LIMIT</literal> value of + a new connection is <quote>unlimited.</quote> If you have + changed the limit, the default value can be restored by + using a <literal>SQL_SELECT_LIMIT</literal> value of <literal>DEFAULT</literal>. </para> @@ -14675,8 +14684,8 @@ </para> <para> - For the trigger <literal>ins_sum</literal> as defined in - <xref linkend="using-triggers"/>, the output of this statement + For the trigger <literal>ins_sum</literal> as defined in + <xref linkend="using-triggers"/>, the output of this statement is as shown here: <programlisting> @@ -14688,21 +14697,21 @@ +---------+--------+---------+-------------------------------+--------+---------+ </programlisting> </para> - + <para> - <emphasis role="bold">Note</emphasis>: When using a - <literal>LIKE</literal> clause with <literal>SHOW + <emphasis role="bold">Note</emphasis>: When using a + <literal>LIKE</literal> clause with <literal>SHOW TRIGGERS</literal>, the expression to be matched - (<replaceable>expr</replaceable>) is compared with the name - of the table on which the trigger is declared, and not with - the name of the trigger: - + (<replaceable>expr</replaceable>) is compared with the name of + the table on which the trigger is declared, and not with the + name of the trigger: + <programlisting> mysql> SHOW TRIGGERS LIKE 'ins%'; Empty set (0.01 sec) </programlisting> </para> - + <para> A brief explanation of the columns in the output of this statement is shown here: @@ -14748,7 +14757,7 @@ <listitem> <para> - <literal>Created</literal>: Currently this value of this + <literal>Created</literal>: Currently this value of this column is always <literal>NULL</literal>. </para> </listitem> @@ -16800,7 +16809,7 @@ <para> The error number and error message returned by the most recently executed query. An error number of 0 and message - of the empty string mean ``no error.'' If the + of the empty string mean <quote>no error.</quote> If the <literal>Last_Error</literal> value is not empty, it also appears as a message in the slave's error log. </para> @@ -16968,15 +16977,16 @@ </para> <para> - This field is an indication of how ``late'' the slave is. - When the slave SQL thread is actively running (processing - updates), this field is the number of seconds that have - elapsed since the timestamp of the most recent event on - the master executed by that thread. When that thread has - caught up on the slave I/O thread and goes idle waiting - from more events from the I/O thread this field is zero. - In sum, this field measures in seconds the time difference - between the slave SQL thread and the slave I/O thread. + This field is an indication of how <quote>late</quote> the + slave is. When the slave SQL thread is actively running + (processing updates), this field is the number of seconds + that have elapsed since the timestamp of the most recent + event on the master executed by that thread. When that + thread has caught up on the slave I/O thread and goes idle + waiting from more events from the I/O thread this field is + zero. In sum, this field measures in seconds the time + difference between the slave SQL thread and the slave I/O + thread. </para> <!-- TODO: How fast is "fast"? --> @@ -17001,14 +17011,14 @@ difference is computed when the slave I/O thread starts, and assumed to remain constant from then on). <literal>Seconds_Behind_Master</literal> is - <literal>NULL</literal> (which means ``unknown'') if the - slave SQL thread is not running, or if the slave I/O - thread is not running or not connected to master. For - example if the slave I/O thread is sleeping for - <literal>master-connect-retry</literal> seconds before - reconnecting, <literal>NULL</literal> is shown, as the - slave cannot know what the master is doing, and so cannot - say reliably how late it is. + <literal>NULL</literal> (which means + <quote>unknown</quote>) if the slave SQL thread is not + running, or if the slave I/O thread is not running or not + connected to master. For example if the slave I/O thread + is sleeping for <literal>master-connect-retry</literal> + seconds before reconnecting, <literal>NULL</literal> is + shown, as the slave cannot know what the master is doing, + and so cannot say reliably how late it is. </para> <para> --- 1.12/refman-5.0/storage-engines.xml 2005-07-29 13:18:57 -04:00 +++ 1.13/refman-5.0/storage-engines.xml 2005-07-31 11:50:01 -04:00 @@ -1840,11 +1840,11 @@ <listitem> <para> - If the <literal>MERGE</literal> table is non-temporary, - all underlying <literal>MyISAM</literal> tables have to be + If the <literal>MERGE</literal> table is non-temporary, all + underlying <literal>MyISAM</literal> tables have to be permanent, too. If the <literal>MERGE</literal> table is - temporary, the <literal>MyISAM</literal> tables can be any - mix of temporary and non-temporary. + temporary, the <literal>MyISAM</literal> tables can be any mix + of temporary and non-temporary. </para> </listitem> --- 1.9/refman-5.0/stored-procedures.xml 2005-07-19 15:01:41 -04:00 +++ 1.10/refman-5.0/stored-procedures.xml 2005-07-31 11:50:01 -04:00 @@ -690,11 +690,11 @@ <para> <literal>CALL</literal> can pass back values to its caller using parameters that are declared as <literal>OUT</literal> or - <literal>INOUT</literal> parameters. It also ``returns'' the - number of rows affected, which a client program can obtain at - the SQL level by calling the <literal>ROW_COUNT()</literal> - function and from C by calling the - <literal>mysql_affected_rows()</literal> C API function. + <literal>INOUT</literal> parameters. It also + <quote>returns</quote> the number of rows affected, which a + client program can obtain at the SQL level by calling the + <literal>ROW_COUNT()</literal> function and from C by calling + the <literal>mysql_affected_rows()</literal> C API function. </para> </section> @@ -1346,7 +1346,8 @@ <literal>ITERATE</literal> can only appear within <literal>LOOP</literal>, <literal>REPEAT</literal>, and <literal>WHILE</literal> statements. - <literal>ITERATE</literal> means ``do the loop again.'' + <literal>ITERATE</literal> means <quote>do the loop + again.</quote> </para> <para> --- 1.11/refman-5.0/triggers.xml 2005-07-22 19:48:42 -04:00 +++ 1.12/refman-5.0/triggers.xml 2005-07-31 11:50:01 -04:00 @@ -271,9 +271,9 @@ is a simple <literal>SET</literal> that accumulates the values inserted into the <literal>amount</literal> column. The statement refers to the column as - <literal>NEW.amount</literal> which means ``the value of the - <literal>amount</literal> column to be inserted into the new - row.'' + <literal>NEW.amount</literal> which means <quote>the value of + the <literal>amount</literal> column to be inserted into the + new row.</quote> </para> </listitem> --- 1.9/refman-5.0/tutorial.xml 2005-07-19 11:57:37 -04:00 +++ 1.10/refman-5.0/tutorial.xml 2005-07-31 11:50:01 -04:00 @@ -34,12 +34,13 @@ This chapter provides a tutorial introduction to MySQL by showing how to use the <command>mysql</command> client program to create and use a simple database. <command>mysql</command> (sometimes referred - to as the ``terminal monitor'' or just ``monitor'') is an - interactive program that allows you to connect to a MySQL server, - run queries, and view the results. <command>mysql</command> may also - be used in batch mode: you place your queries in a file beforehand, - then tell <command>mysql</command> to execute the contents of the - file. Both ways of using <command>mysql</command> are covered here. + to as the <quote>terminal monitor</quote> or just + <quote>monitor</quote>) is an interactive program that allows you to + connect to a MySQL server, run queries, and view the results. + <command>mysql</command> may also be used in batch mode: you place + your queries in a file beforehand, then tell + <command>mysql</command> to execute the contents of the file. Both + ways of using <command>mysql</command> are covered here. </para> <para> @@ -269,8 +270,8 @@ idea of server performance. These values are imprecise because they represent wall clock time (not CPU or machine time), and because they are affected by factors such as server load and - network latency. (For brevity, the ``rows in set'' line is not - shown in the remaining examples in this chapter.) + network latency. (For brevity, the <quote>rows in set</quote> + line is not shown in the remaining examples in this chapter.) </para> </listitem> @@ -1212,7 +1213,7 @@ <para> <replaceable>what_to_select</replaceable> indicates what you want to see. This can be a list of columns, or - <literal>*</literal> to indicate ``all columns.'' + <literal>*</literal> to indicate <quote>all columns.</quote> <replaceable>which_table</replaceable> indicates the table from which you want to retrieve data. The <literal>WHERE</literal> clause is optional. If it is present, @@ -2261,8 +2262,8 @@ <para> You could also write the previous query using the - '<literal>{n}</literal>' ``repeat-<literal>n</literal>-times'' - operator: + '<literal>{n}</literal>' + <quote>repeat-<literal>n</literal>-times</quote> operator: </para> <programlisting> @@ -2297,19 +2298,19 @@ </indexterm> <para> - Databases are often used to answer the question, ``How often - does a certain type of data occur in a table?'' For example, - you might want to know how many pets you have, or how many - pets each owner has, or you might want to perform various - kinds of census operations on your animals. + Databases are often used to answer the question, <quote>How + often does a certain type of data occur in a table?</quote> + For example, you might want to know how many pets you have, or + how many pets each owner has, or you might want to perform + various kinds of census operations on your animals. </para> <para> Counting the total number of animals you have is the same - question as ``How many rows are in the <literal>pet</literal> - table?'' because there is one record per pet. - <literal>COUNT(*)</literal> counts the number of rows, so the - query to count your animals looks like this: + question as <quote>How many rows are in the + <literal>pet</literal> table?</quote> because there is one + record per pet. <literal>COUNT(*)</literal> counts the number + of rows, so the query to count your animals looks like this: </para> <programlisting> @@ -3086,7 +3087,7 @@ <title id='title-example-maximum-column'>&title-example-maximum-column;</title> <para> - ``What's the highest item number?'' + <quote>What's the highest item number?</quote> </para> <programlisting> --- 1.9/refman/mysql-connectors.xml 2005-07-25 12:40:27 -04:00 +++ 1.10/refman/mysql-connectors.xml 2005-07-31 11:50:01 -04:00 @@ -931,7 +931,7 @@ most cases, you can continue by pressing <literal>Ignore</literal> to copy the rest of the MyODBC files and the final installation should still work. If it doesn't, the - solution is to re-boot your computer in ``safe mode.'' Choose + solution is to re-boot your computer in <quote>safe mode.</quote> Choose safe mode by pressing F8 just before your machine starts Windows during re-booting, install MyODBC, and re-boot to normal mode. </para> @@ -2640,8 +2640,8 @@ <row> <entry>2</entry> <entry>The client can't handle that MySQL returns the true value of affected - rows. If this flag is set, MySQL returns ``found - rows'' instead. You must have MySQL 3.21.14 or newer + rows. If this flag is set, MySQL returns <quote>found + rows</quote> instead. You must have MySQL 3.21.14 or newer to get this to work.</entry> </row> <row> @@ -3905,7 +3905,7 @@ <para> The purpose of <literal>CONCAT()</literal> in this example is to fool ODBC into thinking the column is - of ``string type.'' Without the + of <quote>string type.</quote> Without the <literal>CONCAT()</literal>, ODBC knows the column is of time type, and Excel does not understand that. </para> @@ -4845,7 +4845,7 @@ <title id='title-trapping-odbc-errors'>&title-trapping-odbc-errors;</title> <para> - Read ``How to Trap ODBC Login Error Messages in Access'' at + Read <quote>How to Trap ODBC Login Error Messages in Access</quote> at <ulink url="http://support.microsoft.com/support/kb/articles/Q124/9/01.asp?LN=EN-US&SD=gn&FR=0%3CP%3E"/>. </para> @@ -4921,7 +4921,7 @@ <title id='title-query-timeout'>&title-query-timeout;</title> <para> - Read ``Set the QueryTimeout Value for ODBC Connections'' at + Read <quote>Set the QueryTimeout Value for ODBC Connections</quote> at <ulink url="http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B153756"/>. </para> --- 1.9/refman/problems.xml 2005-07-19 22:54:57 -04:00 +++ 1.10/refman/problems.xml 2005-07-31 11:50:02 -04:00 @@ -155,15 +155,16 @@ happening. You should also state why you think that MySQL is causing the problem. Take into consideration all the situations in this chapter. State any problems exactly how they appear when you - examine your system. Use the ``copy and paste'' method for any - output and error messages from programs and log files. + examine your system. Use the <quote>copy and paste</quote> method + for any output and error messages from programs and log files. </para> <para> Try to describe in detail which program is not working and all symptoms you see. We have in the past received many bug reports - that state only ``the system doesn't work.'' This doesn't provide - us with any information about what could be the problem. + that state only <quote>the system doesn't work.</quote> This + doesn't provide us with any information about what could be the + problem. </para> <para> @@ -553,9 +554,9 @@ <para> Substitute the password you want to use for - ``<replaceable>newpwd</replaceable>'' in the preceding - examples. MySQL cannot tell you what the original password - was, so you'll need to pick a new one. + <quote><replaceable>newpwd</replaceable></quote> in the + preceding examples. MySQL cannot tell you what the original + password was, so you'll need to pick a new one. </para> </listitem> @@ -1792,8 +1793,8 @@ <literal>--open-files-limit</literal> and <command>ulimit</command> can increase the number of file descriptors, but only up to the limit imposed by the operating - system. There is also a ``hard'' limit that can be overridden - only if you start <command>mysqld_safe</command> or + system. There is also a <quote>hard</quote> limit that can be + overridden only if you start <command>mysqld_safe</command> or <command>mysqld</command> as <literal>root</literal> (just remember that you also need to start the server with the <literal>--user</literal> option in this case so that it does @@ -2457,9 +2458,9 @@ </para> <para> - Replace ``<replaceable>newpwd</replaceable>'' with the - actual <literal>root</literal> password that you want to - use. + Replace <quote><replaceable>newpwd</replaceable></quote> + with the actual <literal>root</literal> password that you + want to use. </para> </listitem> @@ -2824,16 +2825,17 @@ <para> This section describes how MySQL responds to disk-full errors - (such as ``no space left on device''), and, as of MySQL 4.0.22, - to quota-exceeded errors (such as ``write failed'' or ``user - block limit reached"). + (such as <quote>no space left on device</quote>), and, as of + MySQL 4.0.22, to quota-exceeded errors (such as <quote>write + failed</quote> or <quote>user block limit reached</quote>). </para> <para> This section is relevant for writes to <literal>MyISAM</literal> tables. As of MySQL 4.1.9, it also applies for writes to binary log files and binary log index file, except that references to - ``row'' and ``record'' should be understood to mean ``event.'' + <quote>row</quote> and <quote>record</quote> should be + understood to mean <quote>event.</quote> </para> <para> @@ -2883,9 +2885,10 @@ <listitem> <para> Other threads might be waiting for the table that caused the - disk-full condition. If you have several ``locked'' threads, - killing the one thread that is waiting on the disk-full - condition allows the other threads to continue. + disk-full condition. If you have several + <quote>locked</quote> threads, killing the one thread that + is waiting on the disk-full condition allows the other + threads to continue. </para> </listitem> @@ -3219,9 +3222,10 @@ <para> Simple comparison operations (<literal>>=, >, =, <, <=</literal>, sorting, and grouping) are based on each - character's ``sort value.'' Characters with the same sort value - (such as '<literal>E</literal>', '<literal>e</literal>', and - '<literal>é</literal>') are treated as the same character. + character's <quote>sort value.</quote> Characters with the same + sort value (such as '<literal>E</literal>', + '<literal>e</literal>', and '<literal>é</literal>') are treated + as the same character. </para> </section> @@ -3260,12 +3264,13 @@ <para> As a convenience, MySQL automatically converts a date to a number if the date is used in a numeric context (and vice - versa). It is also smart enough to allow a ``relaxed'' string - form when updating and in a <literal>WHERE</literal> clause that - compares a date to a <literal>TIMESTAMP</literal>, - <literal>DATE</literal>, or <literal>DATETIME</literal> column. - (``Relaxed form'' means that any punctuation character may be - used as the separator between parts. For example, + versa). It is also smart enough to allow a + <quote>relaxed</quote> string form when updating and in a + <literal>WHERE</literal> clause that compares a date to a + <literal>TIMESTAMP</literal>, <literal>DATE</literal>, or + <literal>DATETIME</literal> column. (<quote>Relaxed form</quote> + means that any punctuation character may be used as the + separator between parts. For example, <literal>'2004-08-15'</literal> and <literal>'2004#08#15'</literal> are equivalent.) MySQL can also convert a string containing no separators (such as @@ -3282,8 +3287,8 @@ <literal>></literal>, or <literal>BETWEEN</literal> operators, MySQL normally converts the string to an internal long integer for faster comparision (and also for a bit more - ``relaxed'' string checking). However, this conversion is - subject to the following exceptions: + <quote>relaxed</quote> string checking). However, this + conversion is subject to the following exceptions: </para> <itemizedlist> @@ -3392,9 +3397,9 @@ <para> If you are not using the <literal>NO_ZERO_DATE</literal> SQL mode, MySQL also allows you to store - <literal>'0000-00-00'</literal> as a ``dummy date.'' This is in - some cases more convenient than using <literal>NULL</literal> - values. + <literal>'0000-00-00'</literal> as a <quote>dummy date.</quote> + This is in some cases more convenient than using + <literal>NULL</literal> values. </para> <para> @@ -3453,9 +3458,9 @@ Both statements insert a value into the <literal>phone</literal> column, but the first inserts a <literal>NULL</literal> value and the second inserts an empty string. The meaning of the first - can be regarded as ``phone number is not known'' and the meaning - of the second can be regarded as ``the person is known to have - no phone, and thus no phone number.'' + can be regarded as <quote>phone number is not known</quote> and + the meaning of the second can be regarded as <quote>the person + is known to have no phone, and thus no phone number.</quote> </para> <para> @@ -3523,8 +3528,8 @@ empty or missing columns are updated with <literal>''</literal>. If you want a <literal>NULL</literal> value in a column, you should use <literal>\N</literal> in the data file. The literal - word ``<literal>NULL</literal>'' may also be used under some - circumstances. See <xref linkend="load-data"/>. + word <quote><literal>NULL</literal></quote> may also be used + under some circumstances. See <xref linkend="load-data"/>. </para> <para> @@ -4006,8 +4011,8 @@ Depending on your computer architecture, you may or may not see similar results. Different CPUs may evaluate floating-point numbers differently. For example, on some machines you may get - the ``correct'' results by multiplying both arguments by 1, as - the following example shows. + the <quote>correct</quote> results by multiplying both arguments + by 1, as the following example shows. </para> <para> @@ -4086,8 +4091,8 @@ MySQL uses a cost-based optimizer to determine the best way to resolve a query. In many cases, MySQL can calculate the best possible query plan, but sometimes MySQL doesn't have enough - information about the data at hand and has to make ``educated'' - guesses about the data. + information about the data at hand and has to make + <quote>educated</quote> guesses about the data. </para> <para> @@ -4996,15 +5001,15 @@ <listitem> <para> <literal>BLOB</literal> and <literal>TEXT</literal> values - can't ``reliably'' be used in <literal>GROUP BY</literal>, - <literal>ORDER BY</literal> or <literal>DISTINCT</literal>. - Only the first <literal>max_sort_length</literal> bytes are - used when comparing <literal>BLOB</literal> values in these - cases. The default value of - <literal>max_sort_length</literal> value is 1024 and can be - changed at server startup time. As of MySQL 4.0.3, it can be - changed at runtime. For older versions, a workaround is to - use a substring. For example: + can't <quote>reliably</quote> be used in <literal>GROUP + BY</literal>, <literal>ORDER BY</literal> or + <literal>DISTINCT</literal>. Only the first + <literal>max_sort_length</literal> bytes are used when + comparing <literal>BLOB</literal> values in these cases. The + default value of <literal>max_sort_length</literal> value is + 1024 and can be changed at server startup time. As of MySQL + 4.0.3, it can be changed at runtime. For older versions, a + workaround is to use a substring. For example: </para> <programlisting> @@ -5096,13 +5101,14 @@ <listitem> <para> The optimizer may handle <literal>DISTINCT</literal> - differently when you are using ``hidden'' columns in a join - than when you are not. In a join, hidden columns are counted - as part of the result (even if they are not shown), whereas - in normal queries, hidden columns don't participate in the - <literal>DISTINCT</literal> comparison. We will probably - change this in the future to never compare the hidden - columns when executing <literal>DISTINCT</literal>. + differently when you are using <quote>hidden</quote> columns + in a join than when you are not. In a join, hidden columns + are counted as part of the result (even if they are not + shown), whereas in normal queries, hidden columns don't + participate in the <literal>DISTINCT</literal> comparison. + We will probably change this in the future to never compare + the hidden columns when executing + <literal>DISTINCT</literal>. </para> <para> --- 1.2/refman/regexp.xml 2005-07-19 11:57:45 -04:00 +++ 1.3/refman/regexp.xml 2005-07-31 11:50:02 -04:00 @@ -220,9 +220,9 @@ <para> <literal>{n}</literal> or <literal>{m,n}</literal> notation provides a more general way of writing regular expressions that - match many occurrences of the previous atom (or ``piece'') of - the pattern. <literal>m</literal> and <literal>n</literal> are - integers. + match many occurrences of the previous atom (or + <quote>piece</quote>) of the pattern. <literal>m</literal> and + <literal>n</literal> are integers. </para> <itemizedlist> --- 1.7/refman/replication.xml 2005-07-19 11:57:45 -04:00 +++ 1.8/refman/replication.xml 2005-07-31 11:50:02 -04:00 @@ -683,7 +683,7 @@ <listitem> <para> When the size of the current relay log file becomes too - large. The meaning of ``too large'' is determined as + large. The meaning of <quote>too large</quote> is determined as follows: </para> @@ -1991,7 +1991,7 @@ MySQL only supports one master and many slaves. Later we will add a voting algorithm to automatically change master if something goes wrong with the current master. We will also - introduce ``agent'' processes to help do load balancing by + introduce <quote>agent</quote> processes to help do load balancing by sending <literal>SELECT</literal> queries to different slaves. </para> </listitem> @@ -2744,7 +2744,7 @@ <para> Places an upper limit on the total size of all relay logs on - the slave (a value of 0 means ``unlimited''). This is useful + the slave (a value of 0 means <quote>unlimited</quote>). This is useful for a slave server host that has limited disk space. When the limit is reached, the I/O thread stops reading binary log events from the master server until the SQL thread has caught @@ -2810,7 +2810,7 @@ </para> <para> - The main reason for this ``just-check-the-default-database'' + The main reason for this <quote>just-check-the-default-database</quote> behavior is that it's difficult from the statement alone to know whether or not it should be replicated (for example, if you are using multiple-table <literal>DELETE</literal> or @@ -3298,8 +3298,8 @@ sales SELECT * FROM prices</literal>: only <literal>sales</literal> are compared to the rules). If several tables are to be updated (multiple-table - statement), the first matching table (matching ``do'' or - ``ignore'') wins. That is, the first table is compared to + statement), the first matching table (matching <quote>do</quote> or + <quote>ignore</quote>) wins. That is, the first table is compared to the rules. Then, if no decision could be mad, the second table is compared to the rules, and so forth. </para> @@ -4324,7 +4324,7 @@ If you have a repeatable test case that demonstrates the bug, please enter it into our bugs database at <ulink url="http://bugs.mysql.com/"/>. If you have a phantom - problem (one that you cannot duplicate ``at will''), use the + problem (one that you cannot duplicate <quote>at will</quote>), use the following procedure: </para> --- 1.4/refman/spatial-extensions-in-mysql.xml 2005-07-19 11:57:45 -04:00 +++ 1.5/refman/spatial-extensions-in-mysql.xml 2005-07-31 11:50:02 -04:00 @@ -856,8 +856,8 @@ <para> The OpenGIS specification defines a simple <literal>Surface</literal> as a geometry that consists of a - single ``patch'' that is associated with a single exterior - boundary and zero or more interior boundaries. + single <quote>patch</quote> that is associated with a single + exterior boundary and zero or more interior boundaries. </para> </listitem> @@ -1109,10 +1109,11 @@ <listitem> <para> A <literal>MultiCurve</literal> boundary is obtained by - applying the ``mod 2 union rule'' (also known as the - ``odd-even rule''): A point is in the boundary of a - <literal>MultiCurve</literal> if it is in the boundaries of - an odd number of <literal>MultiCurve</literal> elements. + applying the <quote>mod 2 union rule</quote> (also known as + the <quote>odd-even rule</quote>): A point is in the + boundary of a <literal>MultiCurve</literal> if it is in the + boundaries of an odd number of <literal>MultiCurve</literal> + elements. </para> </listitem> @@ -1493,7 +1494,7 @@ <para> The Well-Known Binary (WKB) representation for geometric values is defined by the OpenGIS specifications. It is also defined in - the ISO ``SQL/MM Part 3: Spatial'' standard. + the ISO <quote>SQL/MM Part 3: Spatial</quote> standard. </para> <para> --- 1.26/refman/sql-syntax.xml 2005-07-30 03:47:31 -04:00 +++ 1.27/refman/sql-syntax.xml 2005-07-31 11:50:03 -04:00 @@ -1438,8 +1438,8 @@ if it contains only positive values. Inserting a negative number is regarded as inserting a very large positive number. This is done to avoid precision problems when - numbers ``wrap'' over from positive to negative and also to - ensure that you don't accidentally get an + numbers <quote>wrap</quote> over from positive to negative + and also to ensure that you don't accidentally get an <literal>AUTO_INCREMENT</literal> column that contains <literal>0</literal>. </para> @@ -1589,10 +1589,10 @@ <para> For date and time types other than <literal>TIMESTAMP</literal>, the default is the - appropriate ``zero'' value for the type. For the first - <literal>TIMESTAMP</literal> column in a table, the - default value is the current date and time. See - <xref linkend="date-and-time-types"/>. + appropriate <quote>zero</quote> value for the type. For + the first <literal>TIMESTAMP</literal> column in a + table, the default value is the current date and time. + See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -2336,17 +2336,18 @@ <para> This means that if you have many equal keys on two - consecutive rows, all following ``same'' keys usually only - take two bytes (including the pointer to the row). Compare - this to the ordinary case where the following keys takes - <literal>storage_size_for_key + pointer_size</literal> - (where the pointer size is usually 4). Conversely, you get a - big benefit from prefix compression only if you have many - numbers that are the same. If all keys are totally - different, you use one byte more per key, if the key isn't a - key that can have <literal>NULL</literal> values. (In this - case, the packed key length is stored in the same byte that - is used to mark if a key is <literal>NULL</literal>.) + consecutive rows, all following <quote>same</quote> keys + usually only take two bytes (including the pointer to the + row). Compare this to the ordinary case where the following + keys takes <literal>storage_size_for_key + + pointer_size</literal> (where the pointer size is usually + 4). Conversely, you get a big benefit from prefix + compression only if you have many numbers that are the same. + If all keys are totally different, you use one byte more per + key, if the key isn't a key that can have + <literal>NULL</literal> values. (In this case, the packed + key length is stored in the same byte that is used to mark + if a key is <literal>NULL</literal>.) </para> </listitem> @@ -4305,16 +4306,16 @@ ... SELECT</literal> statements, the column is set to the implicit default value for the column data type. This is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' - value for date and time types. <literal>INSERT INTO ... - SELECT</literal> statements are handled the same way as - multiple-row inserts because the server does not examine the - result set from the <literal>SELECT</literal> to see whether - it returns a single row. (For a single-row - <literal>INSERT</literal>, no warning occurs when - <literal>NULL</literal> is inserted into a <literal>NOT - NULL</literal> column. Instead, the statement fails with an - error.) + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. + <literal>INSERT INTO ... SELECT</literal> statements are + handled the same way as multiple-row inserts because the + server does not examine the result set from the + <literal>SELECT</literal> to see whether it returns a single + row. (For a single-row <literal>INSERT</literal>, no warning + occurs when <literal>NULL</literal> is inserted into a + <literal>NOT NULL</literal> column. Instead, the statement + fails with an error.) </para> </listitem> @@ -4622,10 +4623,11 @@ The following describes in detail what happens when you use the <literal>DELAYED</literal> option to <literal>INSERT</literal> or <literal>REPLACE</literal>. In - this description, the ``thread'' is the thread that received - an <literal>INSERT DELAYED</literal> statement and ``handler'' - is the thread that handles all <literal>INSERT - DELAYED</literal> statements for a particular table. + this description, the <quote>thread</quote> is the thread that + received an <literal>INSERT DELAYED</literal> statement and + <quote>handler</quote> is the thread that handles all + <literal>INSERT DELAYED</literal> statements for a particular + table. </para> <itemizedlist> @@ -5516,10 +5518,10 @@ is used. With fixed-row format, no delimiters are used between fields (but you can still have a line terminator). Instead, column values are written and read using the - ``display'' widths of the columns. For example, if a column - is declared as <literal>INT(7)</literal>, values for the - column are written using seven-character fields. On input, - values for the column are obtained by reading seven + <quote>display</quote> widths of the columns. For example, + if a column is declared as <literal>INT(7)</literal>, values + for the column are written using seven-character fields. On + input, values for the column are obtained by reading seven characters. </para> @@ -5809,7 +5811,7 @@ <listitem> <para> For date and time types, the column is set to the - appropriate ``zero'' value for the type. See + appropriate <quote>zero</quote> value for the type. See <xref linkend="date-and-time-types"/>. </para> </listitem> @@ -7542,7 +7544,8 @@ <para> They are, in many people's opinion, readable. Indeed, it was the innovation of subqueries that gave people the original - idea of calling the early SQL ``Structured Query Language.'' + idea of calling the early SQL <quote>Structured Query + Language.</quote> </para> </listitem> @@ -7769,10 +7772,11 @@ <para> The <literal>ANY</literal> keyword, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ANY</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ANY</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7823,12 +7827,12 @@ <para> Use of the word <literal>SOME</literal> is rare, but this example shows why it might be useful. To most people's ears, - the English phrase ``a is not equal to any b'' means ``there - is no b which is equal to a,'' but that isn't what is meant by - the SQL syntax. The syntax means ``there is some b to which a - is not equal.'' Using <literal><> SOME</literal> instead - helps ensure that everyone understands the true meaning of the - query. + the English phrase <quote>a is not equal to any b</quote> + means <quote>there is no b which is equal to a,</quote> but + that isn't what is meant by the SQL syntax. The syntax means + <quote>there is some b to which a is not equal.</quote> Using + <literal><> SOME</literal> instead helps ensure that + everyone understands the true meaning of the query. </para> </section> @@ -7847,10 +7851,11 @@ <para> The word <literal>ALL</literal>, which must follow a - comparison operator, means ``return <literal>TRUE</literal> if - the comparison is <literal>TRUE</literal> for - <literal>ALL</literal> of the values in the column that the - subquery returns.'' For example: + comparison operator, means <quote>return + <literal>TRUE</literal> if the comparison is + <literal>TRUE</literal> for <literal>ALL</literal> of the + values in the column that the subquery returns.</quote> For + example: </para> <programlisting> @@ -7965,9 +7970,9 @@ <para> The normal use of row constructors, though, is for comparisons with subqueries that return two or more columns. For example, - the following query answers the request, ``find all rows in - table <literal>t1</literal> that also exist in table - <literal>t2</literal>'': + the following query answers the request, <quote>find all rows + in table <literal>t1</literal> that also exist in table + <literal>t2</literal></quote>: </para> <programlisting> @@ -8059,11 +8064,11 @@ The last example is a double-nested <literal>NOT EXISTS</literal> query. That is, it has a <literal>NOT EXISTS</literal> clause within a <literal>NOT EXISTS</literal> - clause. Formally, it answers the question ``does a city exist - with a store that is not in <literal>Stores</literal>?'' But - it's easier to say that a nested <literal>NOT EXISTS</literal> - answers the question ``is x <literal>TRUE</literal> for all - y?'' + clause. Formally, it answers the question <quote>does a city + exist with a store that is not in + <literal>Stores</literal>?</quote> But it's easier to say that + a nested <literal>NOT EXISTS</literal> answers the question + <quote>is x <literal>TRUE</literal> for all y?</quote> </para> </section> @@ -8182,8 +8187,8 @@ <literal>FROM</literal> clause must have a name. Any columns in the <replaceable>subquery</replaceable> select list must have unique names. You can find this syntax described - elsewhere in this manual, where the term used is ``derived - tables.'' + elsewhere in this manual, where the term used is + <quote>derived tables.</quote> </para> <!-- TODO: figure out what the "elsewhere" in previous sentence refers to. --> @@ -8632,10 +8637,11 @@ </itemizedlist> <para> - There is a chapter titled ``How MySQL Transforms Subqueries'' - in the MySQL Internals Manual. You can obtain this document by - downloading the MySQL source package and looking for a file - named <filename>internals.texi</filename> in the + There is a chapter titled <quote>How MySQL Transforms + Subqueries</quote> in the MySQL Internals Manual. You can + obtain this document by downloading the MySQL source package + and looking for a file named + <filename>internals.texi</filename> in the <filename>Docs</filename> directory. </para> @@ -8983,8 +8989,8 @@ is set to the default value appropriate for the column type and the warning count is incremented. The default value is <literal>0</literal> for numeric types, the empty string - (<literal>''</literal>) for string types, and the ``zero'' value - for date and time types. + (<literal>''</literal>) for string types, and the + <quote>zero</quote> value for date and time types. </para> <indexterm type="function"> @@ -10604,7 +10610,7 @@ </row> <row> <entry><literal>USAGE</literal></entry> - <entry>Synonym for ``no privileges''</entry> + <entry>Synonym for <quote>no privileges</quote></entry> </row> <row> <entry><literal>GRANT OPTION</literal></entry> @@ -11801,10 +11807,11 @@ <para> <emphasis role="bold">Note</emphasis>: In some cases, <literal>CHECK TABLE</literal> changes the table. This happens - if the table is marked as ``corrupted'' or ``not closed - properly'' but <literal>CHECK TABLE</literal> doesn't find any - problems in the table. In this case, <literal>CHECK - TABLE</literal> marks the table as okay. + if the table is marked as <quote>corrupted</quote> or + <quote>not closed properly</quote> but <literal>CHECK + TABLE</literal> doesn't find any problems in the table. In + this case, <literal>CHECK TABLE</literal> marks the table as + okay. </para> <para> @@ -11821,8 +11828,9 @@ can take the very small risk that <literal>QUICK</literal> doesn't find an error in the data file. (In most cases, MySQL should find, under normal usage, any error in the data file. - If this happens, the table is marked as ``corrupted'' and - cannot be used until it's repaired.) + If this happens, the table is marked as + <quote>corrupted</quote> and cannot be used until it's + repaired.) </para> <para> @@ -12883,9 +12891,9 @@ <para> The maximum number of records to return from <literal>SELECT</literal> statements. The default value for - a new connection is ``unlimited.'' If you have changed the - limit, the default value can be restored by using a - <literal>SQL_SELECT_LIMIT</literal> value of + a new connection is <quote>unlimited.</quote> If you have + changed the limit, the default value can be restored by + using a <literal>SQL_SELECT_LIMIT</literal> value of <literal>DEFAULT</literal>. </para> @@ -15081,7 +15089,7 @@ <indexterm type="function"> <primary>SHOW TRIGGERS</primary> </indexterm> - + <para> <programlisting> SHOW TRIGGERS [FROM <replaceable>db_name</replaceable>] [LIKE <replaceable>expr</replaceable>] @@ -15095,8 +15103,8 @@ </para> <para> - For the trigger <literal>ins_sum</literal> as defined in - <xref linkend="using-triggers"/>, the output of this statement + For the trigger <literal>ins_sum</literal> as defined in + <xref linkend="using-triggers"/>, the output of this statement is as shown here: <programlisting> @@ -15108,15 +15116,15 @@ +---------+--------+---------+-------------------------------+--------+---------+ </programlisting> </para> - + <para> - <emphasis role="bold">Note</emphasis>: When using a - <literal>LIKE</literal> clause with <literal>SHOW + <emphasis role="bold">Note</emphasis>: When using a + <literal>LIKE</literal> clause with <literal>SHOW TRIGGERS</literal>, the expression to be matched - (<replaceable>expr</replaceable>) is compared with the name - of the table on which the trigger is declared, and not with - the name of the trigger: - + (<replaceable>expr</replaceable>) is compared with the name of + the table on which the trigger is declared, and not with the + name of the trigger: + <programlisting> mysql> SHOW TRIGGERS LIKE 'ins%'; Empty set (0.01 sec) @@ -15168,7 +15176,7 @@ <listitem> <para> - <literal>Created</literal>: Currently this value of this + <literal>Created</literal>: Currently this value of this column is always <literal>NULL</literal>. </para> </listitem> @@ -17263,7 +17271,7 @@ <para> The error number and error message returned by the most recently executed query. An error number of 0 and message - of the empty string mean ``no error.'' If the + of the empty string mean <quote>no error.</quote> If the <literal>Last_Error</literal> value is not empty, it also appears as a message in the slave's error log. </para> @@ -17448,12 +17456,12 @@ This field is present beginning with MySQL 4.1.1. It's been experimental and has been changed in MySQL 4.1.9. The following applies to slaves running MySQL 4.1.9 or newer. - This field is an indication of how ``late'' the slave is. - When the slave SQL thread is actively running (processing - updates), this field is the number of seconds that have - elapsed since the timestamp of the last master's event - executed by that thread. When that thread has caught up on - the slave I/O thread and goes idle waiting from more + This field is an indication of how <quote>late</quote> the + slave is. When the slave SQL thread is actively running + (processing updates), this field is the number of seconds + that have elapsed since the timestamp of the last master's + event executed by that thread. When that thread has caught + up on the slave I/O thread and goes idle waiting from more events from the I/O thread this field is zero. To sum up, this field measures in seconds the time difference between the slave SQL thread and the slave I/O thread. @@ -17479,14 +17487,14 @@ difference is computed when the slave I/O thread starts, and assumed to remain constant from then on). <literal>Seconds_Behind_Master</literal> is - <literal>NULL</literal> (which means ``unknown'') if the - slave SQL thread is not running, or if the slave I/O - thread is not running or not connected to master. For - example if the slave I/O thread is sleeping for - <literal>master-connect-retry</literal> seconds before - reconnecting, <literal>NULL</literal> is shown, as the - slave cannot know what the master is doing, and thus - cannot reliably say how late it is. + <literal>NULL</literal> (which means + <quote>unknown</quote>) if the slave SQL thread is not + running, or if the slave I/O thread is not running or not + connected to master. For example if the slave I/O thread + is sleeping for <literal>master-connect-retry</literal> + seconds before reconnecting, <literal>NULL</literal> is + shown, as the slave cannot know what the master is doing, + and thus cannot reliably say how late it is. </para> <para> --- 1.8/refman/storage-engines.xml 2005-07-29 13:18:12 -04:00 +++ 1.9/refman/storage-engines.xml 2005-07-31 11:50:03 -04:00 @@ -183,12 +183,12 @@ <listitem> <para> The <literal>EXAMPLE</literal> storage engine was added in MySQL - 4.1.3. It is a ``stub'' engine that does nothing. You can create - tables with this engine, but no data can be stored into them or - retrieved from them. The purpose of this engine is to serve as - an example in the MySQL source code that illustrates how to - begin writing new storage engines. As such, it is primarily of - interest to developers. + 4.1.3. It is a <quote>stub</quote> engine that does nothing. You + can create tables with this engine, but no data can be stored + into them or retrieved from them. The purpose of this engine is + to serve as an example in the MySQL source code that illustrates + how to begin writing new storage engines. As such, it is + primarily of interest to developers. </para> </listitem> @@ -1598,12 +1598,13 @@ <para> A <literal>MERGE</literal> table is a collection of identical <literal>MyISAM</literal> tables that can be used as one. - ``Identical'' means that all tables have identical column and - index information. You can't merge tables in which the columns are - listed in a different order, don't have exactly the same columns, - or have the indexes in different order. However, any or all of the - tables can be compressed with <command>myisampack</command>. See - <xref linkend="myisampack"/>. Differences in table options such as + <quote>Identical</quote> means that all tables have identical + column and index information. You can't merge tables in which the + columns are listed in a different order, don't have exactly the + same columns, or have the indexes in different order. However, any + or all of the tables can be compressed with + <command>myisampack</command>. See <xref linkend="myisampack"/>. + Differences in table options such as <literal>AVG_ROW_LENGTH</literal>, <literal>MAX_ROWS</literal>, or <literal>PACK_KEYS</literal> do not matter. @@ -1863,11 +1864,11 @@ <listitem> <para> - If the <literal>MERGE</literal> table is non-temporary, - all underlying <literal>MyISAM</literal> tables have to be + If the <literal>MERGE</literal> table is non-temporary, all + underlying <literal>MyISAM</literal> tables have to be permanent, too. If the <literal>MERGE</literal> table is - temporary, the <literal>MyISAM</literal> tables can be any - mix of temporary and non-temporary. + temporary, the <literal>MyISAM</literal> tables can be any mix + of temporary and non-temporary. </para> </listitem> @@ -1887,11 +1888,12 @@ Key reads are slower. When you read a key, the <literal>MERGE</literal> storage engine needs to issue a read on all underlying tables to check which one most closely - matches the given key. If you then do a ``read-next,'' the - <literal>MERGE</literal> storage engine needs to search the - read buffers to find the next key. Only when one key buffer is - used up, the storage engine needs to read the next key block. - This makes <literal>MERGE</literal> keys much slower on + matches the given key. If you then do a + <quote>read-next,</quote> the <literal>MERGE</literal> storage + engine needs to search the read buffers to find the next key. + Only when one key buffer is used up, the storage engine needs + to read the next key block. This makes + <literal>MERGE</literal> keys much slower on <literal>eq_ref</literal> searches, but not much slower on <literal>ref</literal> searches. See <xref linkend="explain"/> for more information about <literal>eq_ref</literal> and @@ -1945,12 +1947,12 @@ TABLE</literal>, <literal>TRUNCATE TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, or <literal>ANALYZE TABLE</literal> on any of the tables that are mapped into a - <literal>MERGE</literal> table that is ``open.'' If you do - this, the <literal>MERGE</literal> table may still refer to - the original table and you get unexpected results. The - easiest way to work around this deficiency is to issue a + <literal>MERGE</literal> table that is <quote>open.</quote> + If you do this, the <literal>MERGE</literal> table may still + refer to the original table and you get unexpected results. + The easiest way to work around this deficiency is to issue a <literal>FLUSH TABLES</literal> statement to ensure that no - <literal>MERGE</literal> tables remain ``open.'' + <literal>MERGE</literal> tables remain <quote>open.</quote> </para> </listitem> @@ -3187,10 +3189,10 @@ <para> The <literal>EXAMPLE</literal> storage engine was added in MySQL - 4.1.3. It is a ``stub'' engine that does nothing. Its purpose is - to serve as an example in the MySQL source code that illustrates - how to begin writing new storage engines. As such, it is primarily - of interest to developers. + 4.1.3. It is a <quote>stub</quote> engine that does nothing. Its + purpose is to serve as an example in the MySQL source code that + illustrates how to begin writing new storage engines. As such, it + is primarily of interest to developers. </para> <para> @@ -3409,8 +3411,8 @@ <para> Next, create a <literal>FEDERATED</literal> table for accessing the remote table. The server where you create the - <literal>FEDERATED</literal> table is the ``client server.'' On - this server, create the table as follows: + <literal>FEDERATED</literal> table is the <quote>client + server.</quote> On this server, create the table as follows: </para> <programlisting> @@ -3444,12 +3446,12 @@ <para> The remote host information indicates the remote server to which - your ``client'' server connects, and the database and table - information indicates which remote table to use as the ``data - file.'' In the example, the remote server is indicated to be - running as <literal>remote_host</literal> on port 9306, so you - want to start that server so that it is indeed listening to port - 9306. + your <quote>client</quote> server connects, and the database and + table information indicates which remote table to use as the + <quote>data file.</quote> In the example, the remote server is + indicated to be running as <literal>remote_host</literal> on + port 9306, so you want to start that server so that it is indeed + listening to port 9306. </para> <para> --- 1.9/refman/stored-procedures.xml 2005-07-19 15:01:44 -04:00 +++ 1.10/refman/stored-procedures.xml 2005-07-31 11:50:03 -04:00 @@ -690,11 +690,11 @@ <para> <literal>CALL</literal> can pass back values to its caller using parameters that are declared as <literal>OUT</literal> or - <literal>INOUT</literal> parameters. It also ``returns'' the - number of rows affected, which a client program can obtain at - the SQL level by calling the <literal>ROW_COUNT()</literal> - function and from C by calling the - <literal>mysql_affected_rows()</literal> C API function. + <literal>INOUT</literal> parameters. It also + <quote>returns</quote> the number of rows affected, which a + client program can obtain at the SQL level by calling the + <literal>ROW_COUNT()</literal> function and from C by calling + the <literal>mysql_affected_rows()</literal> C API function. </para> </section> @@ -1346,7 +1346,8 @@ <literal>ITERATE</literal> can only appear within <literal>LOOP</literal>, <literal>REPEAT</literal>, and <literal>WHILE</literal> statements. - <literal>ITERATE</literal> means ``do the loop again.'' + <literal>ITERATE</literal> means <quote>do the loop + again.</quote> </para> <para> --- 1.11/refman/triggers.xml 2005-07-22 19:48:43 -04:00 +++ 1.12/refman/triggers.xml 2005-07-31 11:50:03 -04:00 @@ -271,9 +271,9 @@ is a simple <literal>SET</literal> that accumulates the values inserted into the <literal>amount</literal> column. The statement refers to the column as - <literal>NEW.amount</literal> which means ``the value of the - <literal>amount</literal> column to be inserted into the new - row.'' + <literal>NEW.amount</literal> which means <quote>the value of + the <literal>amount</literal> column to be inserted into the + new row.</quote> </para> </listitem> --- 1.7/refman/tutorial.xml 2005-07-19 11:57:47 -04:00 +++ 1.8/refman/tutorial.xml 2005-07-31 11:50:03 -04:00 @@ -34,12 +34,13 @@ This chapter provides a tutorial introduction to MySQL by showing how to use the <command>mysql</command> client program to create and use a simple database. <command>mysql</command> (sometimes referred - to as the ``terminal monitor'' or just ``monitor'') is an - interactive program that allows you to connect to a MySQL server, - run queries, and view the results. <command>mysql</command> may also - be used in batch mode: you place your queries in a file beforehand, - then tell <command>mysql</command> to execute the contents of the - file. Both ways of using <command>mysql</command> are covered here. + to as the <quote>terminal monitor</quote> or just + <quote>monitor</quote>) is an interactive program that allows you to + connect to a MySQL server, run queries, and view the results. + <command>mysql</command> may also be used in batch mode: you place + your queries in a file beforehand, then tell + <command>mysql</command> to execute the contents of the file. Both + ways of using <command>mysql</command> are covered here. </para> <para> @@ -269,8 +270,8 @@ idea of server performance. These values are imprecise because they represent wall clock time (not CPU or machine time), and because they are affected by factors such as server load and - network latency. (For brevity, the ``rows in set'' line is not - shown in the remaining examples in this chapter.) + network latency. (For brevity, the <quote>rows in set</quote> + line is not shown in the remaining examples in this chapter.) </para> </listitem> @@ -1198,9 +1199,10 @@ <para> <literal>what_to_select</literal> indicates what you want to see. This can be a list of columns, or <literal>*</literal> to - indicate ``all columns.'' <literal>which_table</literal> - indicates the table from which you want to retrieve data. The - <literal>WHERE</literal> clause is optional. If it's present, + indicate <quote>all columns.</quote> + <literal>which_table</literal> indicates the table from which + you want to retrieve data. The <literal>WHERE</literal> clause + is optional. If it's present, <literal>conditions_to_satisfy</literal> specifies conditions that rows must satisfy to qualify for retrieval. </para> @@ -2269,8 +2271,8 @@ <para> You could also write the previous query using the - '<literal>{n}</literal>' ``repeat-<literal>n</literal>-times'' - operator: + '<literal>{n}</literal>' + <quote>repeat-<literal>n</literal>-times</quote> operator: </para> <programlisting> @@ -2305,19 +2307,19 @@ </indexterm> <para> - Databases are often used to answer the question, ``How often - does a certain type of data occur in a table?'' For example, - you might want to know how many pets you have, or how many - pets each owner has, or you might want to perform various - kinds of census operations on your animals. + Databases are often used to answer the question, <quote>How + often does a certain type of data occur in a table?</quote> + For example, you might want to know how many pets you have, or + how many pets each owner has, or you might want to perform + various kinds of census operations on your animals. </para> <para> Counting the total number of animals you have is the same - question as ``How many rows are in the <literal>pet</literal> - table?'' because there is one record per pet. - <literal>COUNT(*)</literal> counts the number of rows, so the - query to count your animals looks like this: + question as <quote>How many rows are in the + <literal>pet</literal> table?</quote> because there is one + record per pet. <literal>COUNT(*)</literal> counts the number + of rows, so the query to count your animals looks like this: </para> <programlisting> @@ -3093,7 +3095,7 @@ <title id='title-example-maximum-column'>&title-example-maximum-column;</title> <para> - ``What's the highest item number?'' + <quote>What's the highest item number?</quote> </para> <programlisting> @@ -3113,8 +3115,8 @@ <title id='title-example-maximum-row'>&title-example-maximum-row;</title> <para> - ``Find number, dealer, and price of the most expensive - article.'' + <quote>Find number, dealer, and price of the most expensive + article.</quote> </para> <para> @@ -3197,7 +3199,7 @@ <title id='title-example-maximum-column-group'>&title-example-maximum-column-group;</title> <para> - ``What's the highest price per article?'' + <quote>What's the highest price per article?</quote> </para> <programlisting> @@ -3222,8 +3224,8 @@ <title id='title-example-maximum-column-group-row'>&title-example-maximum-column-group-row;</title> <para> - ``For each article, find the dealer or dealers with the most - expensive price.'' + <quote>For each article, find the dealer or dealers with the + most expensive price.</quote> </para> <para> @@ -3288,12 +3290,12 @@ </para> <para> - ``Can it be done with a single query?'' + <quote>Can it be done with a single query?</quote> </para> <para> Yes, but only by using a quite inefficient trick called the - ``MAX-CONCAT trick'': + <quote>MAX-CONCAT trick</quote>: </para> <programlisting> --- 1.3/refman/using-mysql-programs.xml 2005-07-19 11:57:47 -04:00 +++ 1.4/refman/using-mysql-programs.xml 2005-07-31 11:50:04 -04:00 @@ -219,10 +219,10 @@ shell or command prompt), enter the program name followed by any options or other arguments needed to instruct the program what you want it to do. The following commands show some sample program - invocations. ``<literal>shell></literal>'' represents the - prompt for your command interpreter; it is not part of what you - type. The particular prompt you see depends on your command - interpreter. Typical prompts are <literal>$</literal> for + invocations. <quote><literal>shell></literal></quote> + represents the prompt for your command interpreter; it is not part + of what you type. The particular prompt you see depends on your + command interpreter. Typical prompts are <literal>$</literal> for <command>sh</command> or <command>bash</command>, <literal>%</literal> for <command>csh</command> or <command>tcsh</command>, and <literal>C:\></literal> for @@ -283,12 +283,13 @@ You may find it necessary to invoke MySQL programs using the pathname to the <filename>bin</filename> directory in which they are installed. This is likely to be the case if you get a - ``program not found'' error whenever you attempt to run a MySQL - program from any directory other than the <filename>bin</filename> - directory. To make it more convenient to use MySQL, you can add - the pathname of the <filename>bin</filename> directory to your - <literal>PATH</literal> environment variable setting. Then to run - a program you need only type its name, not its entire pathname. + <quote>program not found</quote> error whenever you attempt to run + a MySQL program from any directory other than the + <filename>bin</filename> directory. To make it more convenient to + use MySQL, you can add the pathname of the + <filename>bin</filename> directory to your <literal>PATH</literal> + environment variable setting. Then to run a program you need only + type its name, not its entire pathname. </para> <para> @@ -449,13 +450,13 @@ <para> MySQL 4.0 introduced some additional flexibility in the way you specify options. These changes were made in MySQL 4.0.2. Some of - them relate to the way you specify options that have ``enabled'' - and ``disabled'' states, and to the use of options that might be - present in one version of MySQL but not another. Those - capabilities are discussed in this section. Another change - pertains to the way you use options to set program variables. - <xref linkend="program-variables"/> discusses that topic - further. + them relate to the way you specify options that have + <quote>enabled</quote> and <quote>disabled</quote> states, and + to the use of options that might be present in one version of + MySQL but not another. Those capabilities are discussed in this + section. Another change pertains to the way you use options to + set program variables. <xref linkend="program-variables"/> + discusses that topic further. </para> <!-- TODO: also: can specify unambigious prefix of option - hm, but that's --> @@ -491,8 +492,8 @@ </para> <para> - The ``enabled'' form of the option may be specified in any of - these ways: + The <quote>enabled</quote> form of the option may be specified + in any of these ways: </para> <programlisting>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3144) | paul | 31 Jul |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.472 sec. using MySQL 5.1.14-beta-log