| List: | Internals | « Previous MessageNext Message » | |
| From: | stefan | Date: | June 23 2005 9:11am |
| Subject: | bk commit - mysqldoc@docsrva tree (stefan:1.2862) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of stefan. When stefan does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.2862 05/06/23 09:11:14 stefan@stripped +3 -0 column-types.xml: Sync with refman Emphasise that TIMESTAMP display widths are ignored as of 4.1; display width is fixed at 19 characters (Bug#11277) refman-5.0/column-types.xml 1.5 05/06/23 09:10:51 stefan@stripped +16 -13 Sync with refman refman-4.1/column-types.xml 1.5 05/06/23 09:10:49 stefan@stripped +16 -13 Sync with refman refman/column-types.xml 1.5 05/06/23 09:09:52 stefan@stripped +16 -13 Emphasise that TIMESTAMP display widths are ignored as of 4.1; display width is fixed at 19 characters (Bug#11277) # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: stefan # Host: apollon.site # Root: /home/stefan/bk/mysqldoc --- 1.4/refman-4.1/column-types.xml 2005-06-22 12:30:25 +02:00 +++ 1.5/refman-4.1/column-types.xml 2005-06-23 09:10:49 +02:00 @@ -104,7 +104,7 @@ Applies to floating-point and fixed-point types and indicates the number of digits following the decimal point. The maximum possible value is 30, but should be no greater than - <replaceable>M</replaceable>−2. + <replaceable>M</replaceable>-2. </para></listitem> <listitem><para> @@ -912,10 +912,11 @@ <para> From MySQL 4.1 on, <literal>TIMESTAMP</literal> is returned as a - string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. If - you want to obtain the value as a number, you should add - <literal>+0</literal> to the timestamp column. Different timestamp - display widths are not supported. + string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. + Display widths (used as described in the following paragraphs) are no + longer supported; the display width is fixed at 19 characters. + If you want to obtain the value as a number, you should add + <literal>+0</literal> to the timestamp column. </para> <para> @@ -1410,7 +1411,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 255 (2^8 - − 1) bytes. + - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1436,7 +1437,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 255 (2^8 - − 1) characters. + - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1462,7 +1463,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 65,535 - (2^16 − 1) bytes. + (2^16 - 1) bytes. </para> <para> @@ -1495,7 +1496,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 65,535 - (2^16 − 1) characters. + (2^16 - 1) characters. </para> <para> @@ -1528,7 +1529,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 16,777,215 (2^24 − 1) bytes. + 16,777,215 (2^24 - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1554,7 +1555,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 16,777,215 (2^24 − 1) characters. + 16,777,215 (2^24 - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1580,7 +1581,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) bytes. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) bytes. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGBLOB</literal> columns @@ -1611,7 +1612,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) characters. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) characters. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGTEXT</literal> columns @@ -2990,6 +2991,8 @@ <listitem><para> <literal>TIMESTAMP</literal> columns are displayed in the same format as <literal>DATETIME</literal> columns. + In other words, the display width is fixed at 19 characters, and + the format is <literal>YYYY-MM-DD HH:MM:SS</literal>. </para></listitem> <listitem><para> --- 1.4/refman-5.0/column-types.xml 2005-06-22 12:30:25 +02:00 +++ 1.5/refman-5.0/column-types.xml 2005-06-23 09:10:51 +02:00 @@ -104,7 +104,7 @@ Applies to floating-point and fixed-point types and indicates the number of digits following the decimal point. The maximum possible value is 30, but should be no greater than - <replaceable>M</replaceable>−2. + <replaceable>M</replaceable>-2. </para></listitem> <listitem><para> @@ -912,10 +912,11 @@ <para> From MySQL 4.1 on, <literal>TIMESTAMP</literal> is returned as a - string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. If - you want to obtain the value as a number, you should add - <literal>+0</literal> to the timestamp column. Different timestamp - display widths are not supported. + string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. + Display widths (used as described in the following paragraphs) are no + longer supported; the display width is fixed at 19 characters. + If you want to obtain the value as a number, you should add + <literal>+0</literal> to the timestamp column. </para> <para> @@ -1410,7 +1411,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 255 (2^8 - − 1) bytes. + - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1436,7 +1437,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 255 (2^8 - − 1) characters. + - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1462,7 +1463,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 65,535 - (2^16 − 1) bytes. + (2^16 - 1) bytes. </para> <para> @@ -1495,7 +1496,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 65,535 - (2^16 − 1) characters. + (2^16 - 1) characters. </para> <para> @@ -1528,7 +1529,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 16,777,215 (2^24 − 1) bytes. + 16,777,215 (2^24 - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1554,7 +1555,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 16,777,215 (2^24 − 1) characters. + 16,777,215 (2^24 - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1580,7 +1581,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) bytes. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) bytes. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGBLOB</literal> columns @@ -1611,7 +1612,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) characters. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) characters. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGTEXT</literal> columns @@ -2990,6 +2991,8 @@ <listitem><para> <literal>TIMESTAMP</literal> columns are displayed in the same format as <literal>DATETIME</literal> columns. + In other words, the display width is fixed at 19 characters, and + the format is <literal>YYYY-MM-DD HH:MM:SS</literal>. </para></listitem> <listitem><para> --- 1.4/refman/column-types.xml 2005-06-22 12:30:25 +02:00 +++ 1.5/refman/column-types.xml 2005-06-23 09:09:52 +02:00 @@ -104,7 +104,7 @@ Applies to floating-point and fixed-point types and indicates the number of digits following the decimal point. The maximum possible value is 30, but should be no greater than - <replaceable>M</replaceable>−2. + <replaceable>M</replaceable>-2. </para></listitem> <listitem><para> @@ -912,10 +912,11 @@ <para> From MySQL 4.1 on, <literal>TIMESTAMP</literal> is returned as a - string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. If - you want to obtain the value as a number, you should add - <literal>+0</literal> to the timestamp column. Different timestamp - display widths are not supported. + string with the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>. + Display widths (used as described in the following paragraphs) are no + longer supported; the display width is fixed at 19 characters. + If you want to obtain the value as a number, you should add + <literal>+0</literal> to the timestamp column. </para> <para> @@ -1410,7 +1411,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 255 (2^8 - − 1) bytes. + - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1436,7 +1437,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 255 (2^8 - − 1) characters. + - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1462,7 +1463,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of 65,535 - (2^16 − 1) bytes. + (2^16 - 1) bytes. </para> <para> @@ -1495,7 +1496,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of 65,535 - (2^16 − 1) characters. + (2^16 - 1) characters. </para> <para> @@ -1528,7 +1529,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 16,777,215 (2^24 − 1) bytes. + 16,777,215 (2^24 - 1) bytes. <!-- end_description_for_help_topic --> </para> @@ -1554,7 +1555,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 16,777,215 (2^24 − 1) characters. + 16,777,215 (2^24 - 1) characters. <!-- end_description_for_help_topic --> </para> @@ -1580,7 +1581,7 @@ <para> A <literal>BLOB</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) bytes. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) bytes. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGBLOB</literal> columns @@ -1611,7 +1612,7 @@ <para> A <literal>TEXT</literal> column with a maximum length of - 4,294,967,295 or 4GB (2^32 − 1) characters. Up to MySQL 3.23, the + 4,294,967,295 or 4GB (2^32 - 1) characters. Up to MySQL 3.23, the client/server protocol and <literal>MyISAM</literal> tables had a limit of 16MB per communication packet / table row. From MySQL 4.0, the maximum allowed length of <literal>LONGTEXT</literal> columns @@ -2990,6 +2991,8 @@ <listitem><para> <literal>TIMESTAMP</literal> columns are displayed in the same format as <literal>DATETIME</literal> columns. + In other words, the display width is fixed at 19 characters, and + the format is <literal>YYYY-MM-DD HH:MM:SS</literal>. </para></listitem> <listitem><para>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (stefan:1.2862) | stefan | 23 Jun |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.486 sec. using MySQL 5.1.14-beta-log