Author: paul
Date: 2005-12-10 19:02:13 +0100 (Sat, 10 Dec 2005)
New Revision: 536
Log:
r4670@frost: paul | 2005-12-10 12:00:56 -0600
4.1: Remove references to SQL modes that do not exist until MySQL 5.0.
Modified:
trunk/
trunk/refman-4.1/database-administration.xml
trunk/refman-4.1/problems.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4669
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1609
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4670
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1609
Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml 2005-12-10 18:01:51 UTC (rev 535)
+++ trunk/refman-4.1/database-administration.xml 2005-12-10 18:02:13 UTC (rev 536)
@@ -3994,8 +3994,7 @@
</para>
<para>
- Equivalent to <literal>NO_FIELD_OPTIONS</literal>,
- <literal>HIGH_NOT_PRECEDENCE</literal>.
+ Equivalent to <literal>NO_FIELD_OPTIONS</literal>.
</para>
</listitem>
@@ -4009,8 +4008,7 @@
</para>
<para>
- Equivalent to <literal>NO_FIELD_OPTIONS</literal>,
- <literal>HIGH_NOT_PRECEDENCE</literal>.
+ Equivalent to <literal>NO_FIELD_OPTIONS</literal>.
</para>
</listitem>
Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml 2005-12-10 18:01:51 UTC (rev 535)
+++ trunk/refman-4.1/problems.xml 2005-12-10 18:02:13 UTC (rev 536)
@@ -3533,35 +3533,6 @@
</para>
<para>
- If you are using the <literal>ALLOW_INVALID_DATES</literal> SQL
- mode, MySQL allows you to store dates that are given only
- limited checking: MySQL ensures only that the day is in the
- range from 1 to 31 and the month is in the range from 1 to 12.
- </para>
-
- <para>
- This makes MySQL very convenient for Web applications where you
- obtain year, month, and day in three different fields and you
- want to store exactly what the user inserted (without date
- validation).
- </para>
-
- <para>
- If you are not using the <literal>NO_ZERO_IN_DATE</literal> SQL
- mode, the day or month part can be zero. This is convenient if
- you want to store a birthdate in a <literal>DATE</literal>
- column and you know only part of the date.
- </para>
-
- <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 <quote>dummy date.</quote>
- This is in some cases more convenient than using
- <literal>NULL</literal> values.
- </para>
-
- <para>
If the date cannot be converted to any reasonable value, a
<literal>0</literal> is stored in the <literal>DATE</literal>
column, which is retrieved as <literal>'0000-00-00'</literal>.
@@ -3572,19 +3543,6 @@
server to check the dates.
</para>
- <para>
- If you want MySQL to check all dates and accept only legal dates
- (unless overriden by IGNORE), you should set
- <literal>sql_mode</literal> to
- <literal>"NO_ZERO_IN_DATE,NO_ZERO_DATE"</literal>.
- </para>
-
- <para>
- Date handling in MySQL 5.0.1 and earlier works like MySQL 5.0.2
- with the <literal>ALLOW_INVALID_DATES</literal> SQL mode
- enabled.
- </para>
-
</section>
<section id="problems-with-null">
@@ -4016,7 +3974,7 @@
<literal>FLOAT</literal> to a <literal>DOUBLE</literal>
fixes this. See <xref linkend="problems-with-float"/>.
</para>
-
+
<para>
Similar problems may be encountered when comparing
<literal>DECIMAL</literal> values.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r536 - in trunk: . refman-4.1 | paul | 10 Dec |
