Author: paul
Date: 2007-02-28 16:11:04 +0100 (Wed, 28 Feb 2007)
New Revision: 5110
Log:
r16856@frost: paul | 2007-02-28 08:19:56 -0600
More information about staying current for updated DST rules. (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:16855
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:16856
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:10:05 UTC (rev 5109)
+++ trunk/refman-4.1/database-administration.xml 2007-02-28 15:11:04 UTC (rev 5110)
Changed blocks: 2, Lines Added: 56, Lines Deleted: 6; 3096 bytes
@@ -22794,6 +22794,57 @@
</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> <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
+ -> <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
+ empty. The following query determines whether the table that
+ contains time zone names has any rows:
+ </para>
+
+<programlisting>
+mysql> <userinput>SELECT COUNT(*) FROM mysql.time_zone_name;</userinput>
++----------+
+| COUNT(*) |
++----------+
+| 0 |
++----------+
+</programlisting>
+
+ <para>
+ A count of zero indicates that the table is empty. In this case,
+ no one can be using named time zones, and you don't need to
+ update the tables. A count greater than zero indicates that the
+ table is not empty and that its contents are available to be
+ used for named time zone support. In this case, you should be
+ sure to reload your time zone tables so that anyone who uses
+ named time zones will get correct query results.
+ </para>
+
</section>
<section id="locale-support">
@@ -25598,20 +25649,19 @@
to 0 disables the query cache. The default size is 0, so the
query cache is disabled by default.
</para>
-
+
<formalpara role="mnmas">
-
+
<title>MySQL Enterprise</title>
-
+
<para>
- For expert advice on configuring the query cache subscribe to
+ For expert advice on configuring the query cache subscribe to
the MySQL Network Monitoring and Advisory Service. For more
information see,
<ulink url="&base-url-enterprise;advisors.html" />.
</para>
-
+
</formalpara>
-
<note>
<para>
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2007-02-28 15:10:05 UTC (rev 5109)
+++ trunk/refman-5.0/database-administration.xml 2007-02-28 15:11:04 UTC (rev 5110)
Changed blocks: 3, Lines Added: 62, Lines Deleted: 12; 3837 bytes
@@ -16518,20 +16518,19 @@
server must support older client programs. See
<xref linkend="password-hashing"/>.
</para>
-
+
<formalpara role="mnmas">
-
+
<title>MySQL Network</title>
-
+
<para>
- The MySQL Network Monitoring and Advisory Service
- offers advice on the security implications of using this option.
+ The MySQL Network Monitoring and Advisory Service offers
+ advice on the security implications of using this option.
For subscription information see
<ulink url="&base-url-enterprise;advisors.html"/>.
</para>
-
+
</formalpara>
-
</listitem>
<listitem>
@@ -26606,6 +26605,57 @@
</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> <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
+ -> <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
+ empty. The following query determines whether the table that
+ contains time zone names has any rows:
+ </para>
+
+<programlisting>
+mysql> <userinput>SELECT COUNT(*) FROM mysql.time_zone_name;</userinput>
++----------+
+| COUNT(*) |
++----------+
+| 0 |
++----------+
+</programlisting>
+
+ <para>
+ A count of zero indicates that the table is empty. In this case,
+ no one can be using named time zones, and you don't need to
+ update the tables. A count greater than zero indicates that the
+ table is not empty and that its contents are available to be
+ used for named time zone support. In this case, you should be
+ sure to reload your time zone tables so that anyone who uses
+ named time zones will get correct query results.
+ </para>
+
</section>
<section id="locale-support">
@@ -29305,18 +29355,18 @@
</para>
<formalpara role="mnmas">
-
+
<title>MySQL Enterprise</title>
-
+
<para>
- For expert advice on configuring the query cache subscribe to
+ For expert advice on configuring the query cache subscribe to
the MySQL Network Monitoring and Advisory Service. For more
information see
<ulink url="&base-url-enterprise;advisors.html" />.
</para>
-
+
</formalpara>
-
+
<note>
<para>
When using the Windows Configuration Wizard to install or
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2007-02-28 15:10:05 UTC (rev 5109)
+++ trunk/refman-5.1/database-administration.xml 2007-02-28 15:11:04 UTC (rev 5110)
Changed blocks: 3, Lines Added: 62, Lines Deleted: 12; 3867 bytes
@@ -16884,20 +16884,19 @@
server must support older client programs. See
<xref linkend="password-hashing"/>.
</para>
-
+
<formalpara role="mnmas">
-
+
<title>MySQL Network</title>
-
+
<para>
- The MySQL Network Monitoring and Advisory Service
- offers advice on the security implications of using this option.
+ The MySQL Network Monitoring and Advisory Service offers
+ advice on the security implications of using this option.
For subscription information see
<ulink url="&base-url-enterprise;advisors.html"/>.
</para>
-
+
</formalpara>
-
</listitem>
<listitem>
@@ -27045,6 +27044,57 @@
</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> <userinput>SELECT UNIX_TIMESTAMP('2007-03-11 02:00:00'),</userinput>
+ -> <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
+ empty. The following query determines whether the table that
+ contains time zone names has any rows:
+ </para>
+
+<programlisting>
+mysql> <userinput>SELECT COUNT(*) FROM mysql.time_zone_name;</userinput>
++----------+
+| COUNT(*) |
++----------+
+| 0 |
++----------+
+</programlisting>
+
+ <para>
+ A count of zero indicates that the table is empty. In this case,
+ no one can be using named time zones, and you don't need to
+ update the tables. A count greater than zero indicates that the
+ table is not empty and that its contents are available to be
+ used for named time zone support. In this case, you should be
+ sure to reload your time zone tables so that anyone who uses
+ named time zones will get correct query results.
+ </para>
+
</section>
<section id="locale-support">
@@ -30088,18 +30138,18 @@
to 0 disables the query cache. The default size is 0, so the
query cache is disabled by default.
</para>
-
+
<formalpara role="mnmas">
-
+
<title>MySQL Enterprise</title>
-
+
<para>
- For expert advice on configuring the query cache subscribe to
+ For expert advice on configuring the query cache subscribe to
the MySQL Network Monitoring and Advisory Service. For more
information see
<ulink url="&base-url-enterprise;advisors.html" />.
</para>
-
+
</formalpara>
<note>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5110 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 28 Feb |
