Author: paul
Date: 2006-03-24 20:03:32 +0100 (Fri, 24 Mar 2006)
New Revision: 1665
Log:
r4101@kite-hub: paul | 2006-03-24 12:35:28 -0600
Fold in proof corrections.
Modified:
trunk/
trunk/refman-4.1/data-types.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8925
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4100
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8925
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4101
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2006-03-24 19:03:17 UTC (rev 1664)
+++ trunk/refman-4.1/data-types.xml 2006-03-24 19:03:32 UTC (rev 1665)
@@ -876,6 +876,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>SUM()</literal> and <literal>AVG()</literal>
aggregate functions do not work with temporal values. (They
convert the values to numbers, which loses the part after the
@@ -2547,8 +2553,6 @@
<literal>'YYYY-MM-DD HH:MM:SS'</literal> format. The supported
range is <literal>'1000-01-01 00:00:00'</literal> to
<literal>'9999-12-31 23:59:59'</literal>.
- (<quote>Supported</quote> means that although earlier values
- might work, there is no guarantee)
</para>
<para>
@@ -2561,6 +2565,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>TIMESTAMP</literal> data type has varying
properties, depending on the MySQL version. These properties are
described later in this section.
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2006-03-24 19:03:17 UTC (rev 1664)
+++ trunk/refman-5.0/data-types.xml 2006-03-24 19:03:32 UTC (rev 1665)
@@ -912,6 +912,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>SUM()</literal> and <literal>AVG()</literal>
aggregate functions do not work with temporal values. (They
convert the values to numbers, which loses the part after the
@@ -1487,11 +1493,10 @@
</para>
<para>
- Starting from MySQL 5.0.3, <literal>VARCHAR</literal> is
- stored with a one-byte or two-byte length prefix plus data.
- The length prefix is two bytes if the
- <literal>VARCHAR</literal> column is declared with a length
- greater than 255.
+ <literal>VARCHAR</literal> values are stored using as many
+ characters as are needed, plus one byte to record the length
+ (two bytes for columns that are declared with a length
+ longer than 255).
</para>
<remark role="help-description-end"/>
@@ -2659,8 +2664,6 @@
<literal>'YYYY-MM-DD HH:MM:SS'</literal> format. The supported
range is <literal>'1000-01-01 00:00:00'</literal> to
<literal>'9999-12-31 23:59:59'</literal>.
- (<quote>Supported</quote> means that although earlier values
- might work, there is no guarantee)
</para>
<para>
@@ -2673,6 +2676,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>TIMESTAMP</literal> data type has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2006-03-24 19:03:17 UTC (rev 1664)
+++ trunk/refman-5.1/data-types.xml 2006-03-24 19:03:32 UTC (rev 1665)
@@ -868,6 +868,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>SUM()</literal> and <literal>AVG()</literal>
aggregate functions do not work with temporal values. (They
convert the values to numbers, which loses the part after the
@@ -2125,7 +2131,7 @@
<para>
The <literal>FLOAT</literal> and <literal>DOUBLE</literal> data
types are used to represent approximate numeric data values. For
- <literal>FLOAT</literal> the SQL standard allows an optional
+ <literal>FLOAT</literal>, the SQL standard allows an optional
specification of the precision (but not the range of the exponent)
in bits following the keyword <literal>FLOAT</literal> in
parentheses. MySQL also supports this optional precision
@@ -2325,7 +2331,7 @@
values, as well as a <quote>zero</quote> value that may be used
when you specify an illegal value that MySQL cannot represent. The
<literal>TIMESTAMP</literal> type has special automatic updating
- behavior, described later on. For temporary type storage
+ behavior, described later on. For temporal type storage
requirements, see <xref linkend="storage-requirements"/>.
</para>
@@ -2546,8 +2552,6 @@
<literal>'YYYY-MM-DD HH:MM:SS'</literal> format. The supported
range is <literal>'1000-01-01 00:00:00'</literal> to
<literal>'9999-12-31 23:59:59'</literal>.
- (<quote>Supported</quote> means that although earlier values
- might work, there is no guarantee)
</para>
<para>
@@ -2560,6 +2564,12 @@
</para>
<para>
+ For the <literal>DATETIME</literal> and <literal>DATE</literal>
+ range descriptions, <quote>supported</quote> means that although
+ earlier values might work, there is no guarantee.
+ </para>
+
+ <para>
The <literal>TIMESTAMP</literal> data type has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1665 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 24 Mar |
