Author: paul
Date: 2007-07-25 19:13:09 +0200 (Wed, 25 Jul 2007)
New Revision: 7211
Log:
r27916@polar: paul | 2007-07-25 12:04:58 -0500
Minor wording revisions.
Modified:
trunk/refman-4.1/data-types.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.2/data-types.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27915
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23014
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27916
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23014
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2007-07-25 17:12:45 UTC (rev 7210)
+++ trunk/refman-4.1/data-types.xml 2007-07-25 17:13:09 UTC (rev 7211)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 599 bytes
@@ -2513,7 +2513,7 @@
<para>
MySQL also allows you to store <literal>'0000-00-00'</literal> as
a <quote>dummy date.</quote> This is in some cases more
- convenient, and uses less data and index space, than storing
+ convenient (and uses less data and index space) than storing
<literal>NULL</literal> values.
</para>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2007-07-25 17:12:45 UTC (rev 7210)
+++ trunk/refman-5.0/data-types.xml 2007-07-25 17:13:09 UTC (rev 7211)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 6; 1452 bytes
@@ -2632,18 +2632,21 @@
of the <literal>DATETIME</literal> value is ignored. Starting from
MySQL 5.0.42, a <literal>DATE</literal> value is coerced to the
<literal>DATETIME</literal> type by adding the time portion as
- <literal>'00:00:00'</literal>. To mimic the old behavior use the
- <literal>CAST()</literal> function in the following way:
- <literal>SELECT <replaceable>date_field</replaceable> = CAST(NOW()
- as DATE);</literal>.
+ <literal>'00:00:00'</literal>. To mimic the old behavior, use the
+ <literal>CAST()</literal> function to perform the comparison in
+ the following way:
</para>
+<programlisting>
+<replaceable>date_col</replaceable> = CAST(NOW() as DATE);
+</programlisting>
+
<para>
MySQL also allows you to store <literal>'0000-00-00'</literal> as
a <quote>dummy date</quote> (if you are not using the
<literal>NO_ZERO_DATE</literal> SQL mode). This is in some cases
- is more convenient (and uses less space in data and index) than
- using <literal>NULL</literal> values.
+ more convenient (and uses less data and index space) than using
+ <literal>NULL</literal> values.
</para>
<para>
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2007-07-25 17:12:45 UTC (rev 7210)
+++ trunk/refman-5.1/data-types.xml 2007-07-25 17:13:09 UTC (rev 7211)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 6; 1452 bytes
@@ -2478,18 +2478,21 @@
of the <literal>DATETIME</literal> value is ignored. Starting from
MySQL 5.1.18, a <literal>DATE</literal> value is coerced to the
<literal>DATETIME</literal> type by adding the time portion as
- <literal>'00:00:00'</literal>. To mimic the old behavior use the
- <literal>CAST()</literal> function in the following way:
- <literal>SELECT <replaceable>date_field</replaceable> = CAST(NOW()
- as DATE);</literal>.
+ <literal>'00:00:00'</literal>. To mimic the old behavior, use the
+ <literal>CAST()</literal> function to perform the comparison in
+ the following way:
</para>
+<programlisting>
+<replaceable>date_col</replaceable> = CAST(NOW() as DATE);
+</programlisting>
+
<para>
MySQL also allows you to store <literal>'0000-00-00'</literal> as
a <quote>dummy date</quote> (if you are not using the
<literal>NO_ZERO_DATE</literal> SQL mode). This is in some cases
- is more convenient (and uses less space in data and index) than
- using <literal>NULL</literal> values.
+ more convenient (and uses less data and index space) than using
+ <literal>NULL</literal> values.
</para>
<para>
Modified: trunk/refman-5.2/data-types.xml
===================================================================
--- trunk/refman-5.2/data-types.xml 2007-07-25 17:12:45 UTC (rev 7210)
+++ trunk/refman-5.2/data-types.xml 2007-07-25 17:13:09 UTC (rev 7211)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 6; 1376 bytes
@@ -2475,18 +2475,21 @@
<para>
A <literal>DATE</literal> value is coerced to the
<literal>DATETIME</literal> type by adding the time portion as
- <literal>'00:00:00'</literal>. To mimic the old behavior use the
- <literal>CAST()</literal> function in the following way:
- <literal>SELECT <replaceable>date_field</replaceable> = CAST(NOW()
- as DATE);</literal>.
+ <literal>'00:00:00'</literal>. To mimic the old behavior, use the
+ <literal>CAST()</literal> function to perform the comparison in
+ the following way:
</para>
+<programlisting>
+<replaceable>date_col</replaceable> = CAST(NOW() as DATE);
+</programlisting>
+
<para>
MySQL also allows you to store <literal>'0000-00-00'</literal> as
a <quote>dummy date</quote> (if you are not using the
<literal>NO_ZERO_DATE</literal> SQL mode). This is in some cases
- is more convenient (and uses less space in data and index) than
- using <literal>NULL</literal> values.
+ more convenient (and uses less data and index space) than using
+ <literal>NULL</literal> values.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7211 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 25 Jul |
