Author: paul
Date: 2008-05-28 20:33:13 +0200 (Wed, 28 May 2008)
New Revision: 10848
Log:
r31495@arctic: paul | 2008-05-28 11:33:35 -0500
Give exact end of TIMESTAMP range ('2038-01-19 03:14:07')
(Bug#36339)
Modified:
trunk/it/refman-5.1/data-types.xml
trunk/it/refman-5.1/events.xml
trunk/pt/refman-5.1/data-types.xml
trunk/pt/refman-5.1/events.xml
trunk/refman-4.1/data-types.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.1/events.xml
trunk/refman-6.0/data-types.xml
trunk/refman-6.0/events.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31708
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31488
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31708
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31495
Modified: trunk/it/refman-5.1/data-types.xml
===================================================================
--- trunk/it/refman-5.1/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/it/refman-5.1/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 9; 2365 bytes
@@ -1050,8 +1050,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2762,7 +2762,9 @@
</para>
<para>
- The <literal>TIMESTAMP</literal> data type has varying
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
this section.
@@ -3004,12 +3006,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/it/refman-5.1/events.xml
===================================================================
--- trunk/it/refman-5.1/events.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/it/refman-5.1/events.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 944 bytes
@@ -2064,10 +2064,10 @@
<para>
Events do not support times later than the end of the Unix
- Epoch; this is approximately the end of the year 2038. Prior to
- MySQL 5.1.8, handling in scheduled events of dates later than
- this was buggy; starting with MySQL 5.1.8, such dates are
- specifically disallowed by the Event Scheduler. (Bug #16396)
+ Epoch; this is approximately the beginning of the year 2038.
+ Prior to MySQL 5.1.8, handling in scheduled events of dates
+ later than this was buggy; starting with MySQL 5.1.8, such dates
+ are specifically disallowed by the Event Scheduler. (Bug #16396)
</para>
</formalpara>
Modified: trunk/pt/refman-5.1/data-types.xml
===================================================================
--- trunk/pt/refman-5.1/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/pt/refman-5.1/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 9; 2365 bytes
@@ -1050,8 +1050,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2762,7 +2762,9 @@
</para>
<para>
- The <literal>TIMESTAMP</literal> data type has varying
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
this section.
@@ -3004,12 +3006,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/pt/refman-5.1/events.xml
===================================================================
--- trunk/pt/refman-5.1/events.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/pt/refman-5.1/events.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 944 bytes
@@ -2064,10 +2064,10 @@
<para>
Events do not support times later than the end of the Unix
- Epoch; this is approximately the end of the year 2038. Prior to
- MySQL 5.1.8, handling in scheduled events of dates later than
- this was buggy; starting with MySQL 5.1.8, such dates are
- specifically disallowed by the Event Scheduler. (Bug #16396)
+ Epoch; this is approximately the beginning of the year 2038.
+ Prior to MySQL 5.1.8, handling in scheduled events of dates
+ later than this was buggy; starting with MySQL 5.1.8, such dates
+ are specifically disallowed by the Event Scheduler. (Bug #16396)
</para>
</formalpara>
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-4.1/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 14, Lines Deleted: 10; 2386 bytes
@@ -1067,8 +1067,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2791,8 +2791,11 @@
</para>
<para>
- <literal>TIMESTAMP</literal> data type properties depend on the
- MySQL version, as described later in this section.
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
+ properties that depend on the MySQL version, as described later
+ in this section.
</para>
<para>
@@ -3037,12 +3040,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-5.0/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 9; 2356 bytes
@@ -1107,8 +1107,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2924,7 +2924,9 @@
</para>
<para>
- The <literal>TIMESTAMP</literal> data type has varying
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
this section.
@@ -3171,12 +3173,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-5.1/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 9; 2356 bytes
@@ -1050,8 +1050,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2762,7 +2762,9 @@
</para>
<para>
- The <literal>TIMESTAMP</literal> data type has varying
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
this section.
@@ -3004,12 +3006,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-5.1/events.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 935 bytes
@@ -2064,10 +2064,10 @@
<para>
Events do not support times later than the end of the Unix
- Epoch; this is approximately the end of the year 2038. Prior to
- MySQL 5.1.8, handling in scheduled events of dates later than
- this was buggy; starting with MySQL 5.1.8, such dates are
- specifically disallowed by the Event Scheduler. (Bug #16396)
+ Epoch; this is approximately the beginning of the year 2038.
+ Prior to MySQL 5.1.8, handling in scheduled events of dates
+ later than this was buggy; starting with MySQL 5.1.8, such dates
+ are specifically disallowed by the Event Scheduler. (Bug #16396)
</para>
</formalpara>
Modified: trunk/refman-6.0/data-types.xml
===================================================================
--- trunk/refman-6.0/data-types.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-6.0/data-types.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 3, Lines Added: 12, Lines Deleted: 9; 2356 bytes
@@ -1050,8 +1050,8 @@
<para>
A timestamp. The range is <literal>'1970-01-01
- 00:00:01'</literal> UTC to partway through the year
- <literal>2038</literal>. <literal>TIMESTAMP</literal> values
+ 00:00:01'</literal> UTC to <literal>'2038-01-09
+ 03:14:07'</literal> UTC. <literal>TIMESTAMP</literal> values
are stored as the number of seconds since the epoch
(<literal>'1970-01-01 00:00:00'</literal> UTC). A
<literal>TIMESTAMP</literal> cannot represent the value
@@ -2759,7 +2759,9 @@
</para>
<para>
- The <literal>TIMESTAMP</literal> data type has varying
+ The <literal>TIMESTAMP</literal> data type has a range of
+ <literal>'1970-01-01 00:00:01'</literal> UTC to
+ <literal>'2038-01-09 03:14:07'</literal> UTC. It has varying
properties, depending on the MySQL version and the SQL mode the
server is running in. These properties are described later in
this section.
@@ -3001,12 +3003,13 @@
values all can be specified using the same set of formats,
the types do not all have the same range of values. For
example, <literal>TIMESTAMP</literal> values cannot be
- earlier than <literal>1970</literal> or later than
- <literal>2038</literal>. This means that a date such as
- <literal>'1968-01-01'</literal>, while legal as a
- <literal>DATETIME</literal> or <literal>DATE</literal>
- value, is not valid as a <literal>TIMESTAMP</literal> value
- and is converted to <literal>0</literal>.
+ earlier than <literal>1970</literal> UTC or later than
+ <literal>'2038-01-09 03:14:07'</literal> UTC. This means
+ that a date such as <literal>'1968-01-01'</literal>, while
+ legal as a <literal>DATETIME</literal> or
+ <literal>DATE</literal> value, is not valid as a
+ <literal>TIMESTAMP</literal> value and is converted to
+ <literal>0</literal>.
</para>
</listitem>
Modified: trunk/refman-6.0/events.xml
===================================================================
--- trunk/refman-6.0/events.xml 2008-05-28 12:35:03 UTC (rev 10847)
+++ trunk/refman-6.0/events.xml 2008-05-28 18:33:13 UTC (rev 10848)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 689 bytes
@@ -1882,9 +1882,9 @@
<para>
Events do not support times later than the end of the Unix
- Epoch; this is approximately the end of the year 2038. Such
- dates are specifically disallowed by the Event Scheduler. (Bug
- #16396)
+ Epoch; this is approximately the beginning of the year 2038.
+ Such dates are specifically disallowed by the Event Scheduler.
+ (Bug #16396)
</para>
</formalpara>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10848 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 28 May |
