List:Commits« Previous MessageNext Message »
From:paul Date:February 28 2007 6:54pm
Subject:svn commit - mysqldoc@docsrva: r5113 - in trunk: . refman-4.1 refman-5.0 refman-5.1
View as plain text  
Author: paul
Date: 2007-02-28 19:52:46 +0100 (Wed, 28 Feb 2007)
New Revision: 5113

Log:
 r16997@frost:  paul | 2007-02-28 12:48:16 -0600
 Update time zone test with new one. (From Chris)


Modified:
   trunk/refman-4.1/database-administration.xml
   trunk/refman-5.0/database-administration.xml
   trunk/refman-5.1/database-administration.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:20600
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16858
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:20600
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16997
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593


Modified: trunk/refman-4.1/database-administration.xml
===================================================================
--- trunk/refman-4.1/database-administration.xml	2007-02-28 15:11:52 UTC (rev 5112)
+++ trunk/refman-4.1/database-administration.xml	2007-02-28 18:52:46 UTC (rev 5113)
Changed blocks: 2, Lines Added: 66, Lines Deleted: 24; 4624 bytes

@@ -22795,30 +22795,6 @@
       </itemizedlist>
 
       <para>
-        To check whether your MySQL installation is updated properly for
-        a change in Daylight Saving Time rules, ask for the
-        <literal>UNIX_TIMESTAMP()</literal> values of the times at which
-        the DST switch occurs. For example, in March 2007, the switch
-        occurs in the United States on March 11 at 2 a.m., so the
-        diagnostic query is as follows:
-      </para>
-
-<programlisting>
-mysql&gt; <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
-    -&gt; <userinput>UNIX_TIMESTAMP('2007-03-11 03:00:00')\G</userinput>
-*************************** 1. row ***************************
-UNIX_TIMESTAMP('2007-03-11 02:00:00'): 1173600000
-UNIX_TIMESTAMP('2007-03-11 03:00:00'): 1173600000
-1 row in set (0.00 sec)
-</programlisting>
-
-      <para>
-        The query should return two identical values, even though the
-        function arguments are different, because those arguments
-        indicate the exact time when the 1-hour change occurs.
-      </para>
-
-      <para>
         If you are uncertain whether named time zones are available, for
         use either as the server's time zone setting or by clients that
         set their own time zone, check whether your time zone tables are

@@ -22845,6 +22821,72 @@
         named time zones will get correct query results.
       </para>
 
+      <para>
+        To check whether your MySQL installation is updated properly for
+        a change in Daylight Saving Time rules, use a test like the one
+        following. The example uses values that are appropriate for the
+        2007 DST 1-hour change that occurs in the United States on March
+        11 at 2 a.m.
+      </para>
+
+      <para>
+        The test uses these two queries:
+      </para>
+
+<programlisting>
+SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');
+SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');
+</programlisting>
+
+      <para>
+        The two time values indicate the times at which the DST change
+        occurs, and the use of named time zones requires that the time
+        zone tables be used. The desired result is that both queries
+        return the same result (the input time, converted to the
+        equivalent value in the 'US/Central' time zone).
+      </para>
+
+      <para>
+        Before updating the time zone tables, you would see an incorrect
+        result like this:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 02:00:00                                        |
++------------------------------------------------------------+
+</programlisting>
+
+      <para>
+        After updating the tables, you should see the correct result:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+</programlisting>
+
     </section>
 
     <section id="locale-support">


Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml	2007-02-28 15:11:52 UTC (rev 5112)
+++ trunk/refman-5.0/database-administration.xml	2007-02-28 18:52:46 UTC (rev 5113)
Changed blocks: 2, Lines Added: 66, Lines Deleted: 24; 4624 bytes

@@ -26606,30 +26606,6 @@
       </itemizedlist>
 
       <para>
-        To check whether your MySQL installation is updated properly for
-        a change in Daylight Saving Time rules, ask for the
-        <literal>UNIX_TIMESTAMP()</literal> values of the times at which
-        the DST switch occurs. For example, in March 2007, the switch
-        occurs in the United States on March 11 at 2 a.m., so the
-        diagnostic query is as follows:
-      </para>
-
-<programlisting>
-mysql&gt; <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
-    -&gt; <userinput>UNIX_TIMESTAMP('2007-03-11 03:00:00')\G</userinput>
-*************************** 1. row ***************************
-UNIX_TIMESTAMP('2007-03-11 02:00:00'): 1173600000
-UNIX_TIMESTAMP('2007-03-11 03:00:00'): 1173600000
-1 row in set (0.00 sec)
-</programlisting>
-
-      <para>
-        The query should return two identical values, even though the
-        function arguments are different, because those arguments
-        indicate the exact time when the 1-hour change occurs.
-      </para>
-
-      <para>
         If you are uncertain whether named time zones are available, for
         use either as the server's time zone setting or by clients that
         set their own time zone, check whether your time zone tables are

@@ -26656,6 +26632,72 @@
         named time zones will get correct query results.
       </para>
 
+      <para>
+        To check whether your MySQL installation is updated properly for
+        a change in Daylight Saving Time rules, use a test like the one
+        following. The example uses values that are appropriate for the
+        2007 DST 1-hour change that occurs in the United States on March
+        11 at 2 a.m.
+      </para>
+
+      <para>
+        The test uses these two queries:
+      </para>
+
+<programlisting>
+SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');
+SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');
+</programlisting>
+
+      <para>
+        The two time values indicate the times at which the DST change
+        occurs, and the use of named time zones requires that the time
+        zone tables be used. The desired result is that both queries
+        return the same result (the input time, converted to the
+        equivalent value in the 'US/Central' time zone).
+      </para>
+
+      <para>
+        Before updating the time zone tables, you would see an incorrect
+        result like this:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 02:00:00                                        |
++------------------------------------------------------------+
+</programlisting>
+
+      <para>
+        After updating the tables, you should see the correct result:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+</programlisting>
+
     </section>
 
     <section id="locale-support">


Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml	2007-02-28 15:11:52 UTC (rev 5112)
+++ trunk/refman-5.1/database-administration.xml	2007-02-28 18:52:46 UTC (rev 5113)
Changed blocks: 2, Lines Added: 66, Lines Deleted: 24; 4624 bytes

@@ -27045,30 +27045,6 @@
       </itemizedlist>
 
       <para>
-        To check whether your MySQL installation is updated properly for
-        a change in Daylight Saving Time rules, ask for the
-        <literal>UNIX_TIMESTAMP()</literal> values of the times at which
-        the DST switch occurs. For example, in March 2007, the switch
-        occurs in the United States on March 11 at 2 a.m., so the
-        diagnostic query is as follows:
-      </para>
-
-<programlisting>
-mysql&gt; <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
-    -&gt; <userinput>UNIX_TIMESTAMP('2007-03-11 03:00:00')\G</userinput>
-*************************** 1. row ***************************
-UNIX_TIMESTAMP('2007-03-11 02:00:00'): 1173600000
-UNIX_TIMESTAMP('2007-03-11 03:00:00'): 1173600000
-1 row in set (0.00 sec)
-</programlisting>
-
-      <para>
-        The query should return two identical values, even though the
-        function arguments are different, because those arguments
-        indicate the exact time when the 1-hour change occurs.
-      </para>
-
-      <para>
         If you are uncertain whether named time zones are available, for
         use either as the server's time zone setting or by clients that
         set their own time zone, check whether your time zone tables are

@@ -27095,6 +27071,72 @@
         named time zones will get correct query results.
       </para>
 
+      <para>
+        To check whether your MySQL installation is updated properly for
+        a change in Daylight Saving Time rules, use a test like the one
+        following. The example uses values that are appropriate for the
+        2007 DST 1-hour change that occurs in the United States on March
+        11 at 2 a.m.
+      </para>
+
+      <para>
+        The test uses these two queries:
+      </para>
+
+<programlisting>
+SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');
+SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');
+</programlisting>
+
+      <para>
+        The two time values indicate the times at which the DST change
+        occurs, and the use of named time zones requires that the time
+        zone tables be used. The desired result is that both queries
+        return the same result (the input time, converted to the
+        equivalent value in the 'US/Central' time zone).
+      </para>
+
+      <para>
+        Before updating the time zone tables, you would see an incorrect
+        result like this:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 02:00:00                                        |
++------------------------------------------------------------+
+</programlisting>
+
+      <para>
+        After updating the tables, you should see the correct result:
+      </para>
+
+<programlisting>
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 2:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+
+mysql&gt; <userinput>SELECT CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central');</userinput>
++------------------------------------------------------------+
+| CONVERT_TZ('2007-03-11 3:00:00','US/Eastern','US/Central') |
++------------------------------------------------------------+
+| 2007-03-11 01:00:00                                        | 
++------------------------------------------------------------+
+</programlisting>
+
     </section>
 
     <section id="locale-support">


Thread
svn commit - mysqldoc@docsrva: r5113 - in trunk: . refman-4.1 refman-5.0 refman-5.1paul28 Feb