| List: | Internals | « Previous MessageNext Message » | |
| From: | paul | Date: | September 8 2005 9:36pm |
| Subject: | bk commit - mysqldoc@docsrva tree (paul:1.3511) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of paul. When paul 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.3511 05/09/08 14:36:09 paul@stripped +5 -0 FLOAT(p) after the other FLOAT/DOUBLE descriptions. decimal digit -> digit. refman/column-types.xml 1.31 05/09/08 14:36:08 paul@stripped +64 -63 FLOAT(p) after the other FLOAT/DOUBLE descriptions. decimal digit -> digit. refman-5.1/column-types.xml 1.25 05/09/08 14:36:08 paul@stripped +134 -129 Sync. refman-5.0/column-types.xml 1.25 05/09/08 14:36:08 paul@stripped +129 -125 Sync. refman-4.1/column-types.xml 1.30 05/09/08 14:36:08 paul@stripped +59 -59 Sync. refman-common/news-5.0.xml 1.149 05/09/08 14:14:37 paul@stripped +8 -0 Document bugfix. (Bug #12922) # 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: paul # Host: kite-hub.kitebird.com # Root: /src/extern/MySQL/bk/mysqldoc --- 1.24/refman-5.1/column-types.xml 2005-09-06 16:15:54 -05:00 +++ 1.25/refman-5.1/column-types.xml 2005-09-08 14:36:08 -05:00 @@ -32,8 +32,8 @@ </para> <para> - MySQL ¤t-series; supports extensions for handing spatial data. Information - about spatial types is provided in + MySQL ¤t-series; supports extensions for handing spatial data. + Information about spatial types is provided in <xref linkend="spatial-extensions-in-mysql"/>. </para> @@ -466,8 +466,8 @@ </para> <para> - MySQL ¤t-series; can handle <literal>BIGINT</literal> in the - following cases: + MySQL ¤t-series; can handle + <literal>BIGINT</literal> in the following cases: </para> <itemizedlist> @@ -654,6 +654,43 @@ <listitem> <para> + <indexterm type="type"> + <primary>DOUBLE PRECISION data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>REAL data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>DOUBLE PRECISION</secondary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>REAL</secondary> + </indexterm> + + <literal>DOUBLE + PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> , + <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> + </para> + + <para> + These are synonyms for <literal>DOUBLE</literal>. Exception: + If the server SQL mode includes the + <literal>REAL_AS_FLOAT</literal> option, + <literal>REAL</literal> is a synonym for + <literal>FLOAT</literal> rather than + <literal>DOUBLE</literal>. + </para> + </listitem> + + <listitem> + <para> <indexterm> <primary>floating-point number</primary> </indexterm> @@ -705,43 +742,6 @@ </listitem> <listitem> - <para> - <indexterm type="type"> - <primary>DOUBLE PRECISION data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>REAL data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>DOUBLE PRECISION</secondary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>REAL</secondary> - </indexterm> - - <literal>DOUBLE - PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> , - <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> - </para> - - <para> - These are synonyms for <literal>DOUBLE</literal>. Exception: - If the server SQL mode includes the - <literal>REAL_AS_FLOAT</literal> option, - <literal>REAL</literal> is a synonym for - <literal>FLOAT</literal> rather than - <literal>DOUBLE</literal>. - </para> - </listitem> - - <listitem> <remark> description_for_help_topic DECIMAL ZEROFILL UNSIGNED NUMERIC DEC FIXED @@ -769,8 +769,8 @@ A packed <quote>exact</quote> fixed-point number. <replaceable>M</replaceable> is the total number of decimal digits (the precision) and <replaceable>D</replaceable> is - the number of decimal digits after the decimal point (the - scale). The decimal point and (for negative numbers) the + the number of digits after the decimal point (the scale). + The decimal point and (for negative numbers) the ‘<literal>-</literal>’ sign are not counted in <replaceable>M</replaceable>. If <replaceable>D</replaceable> is 0, values have no decimal @@ -791,7 +791,7 @@ <para> All basic calculations (<literal>+, -, *, /</literal>) with <literal>DECIMAL</literal> columns are done with a precision - of 64 decimal digits. + of 64 digits. </para> <para> @@ -803,17 +803,17 @@ <literal>CHAR</literal> column; <quote>unpacked</quote> means the number is stored as a string, using one character for each digit of the value. <replaceable>M</replaceable> is - the total number of decimal digits and - <replaceable>D</replaceable> is the number of decimal digits - after the decimal point. The decimal point and (for negative - numbers) the ‘<literal>-</literal>’ sign are not - counted in <replaceable>M</replaceable>, although space for - them is reserved. If <replaceable>D</replaceable> is 0, - values have no decimal point or fractional part. The maximum - range of <literal>DECIMAL</literal> values is the same as - for <literal>DOUBLE</literal>, but the actual range for a - given <literal>DECIMAL</literal> column may be constrained - by the choice of <replaceable>M</replaceable> and + the total number of digits and <replaceable>D</replaceable> + is the number of digits after the decimal point. The decimal + point and (for negative numbers) the + ‘<literal>-</literal>’ sign are not counted in + <replaceable>M</replaceable>, although space for them is + reserved. If <replaceable>D</replaceable> is 0, values have + no decimal point or fractional part. The maximum range of + <literal>DECIMAL</literal> values is the same as for + <literal>DOUBLE</literal>, but the actual range for a given + <literal>DECIMAL</literal> column may be constrained by the + choice of <replaceable>M</replaceable> and <replaceable>D</replaceable>. If <replaceable>D</replaceable> is omitted, the default is 0. If <replaceable>M</replaceable> is omitted, the default is @@ -994,8 +994,8 @@ </para> <para> - In MySQL ¤t-series;, <literal>TIMESTAMP</literal> is returned as a - string in the format <literal>'YYYY-MM-DD + In MySQL ¤t-series;, <literal>TIMESTAMP</literal> is + returned as a string in the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>whose 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. @@ -1098,9 +1098,9 @@ </para> <para> - MySQL ¤t-series; string data types include some features that you may - not have encountered in working with versions of MySQL prior to - 4.1: + MySQL ¤t-series; string data types include some features + that you may not have encountered in working with versions of + MySQL prior to 4.1: </para> <itemizedlist> @@ -1138,9 +1138,9 @@ <listitem> <para> - MySQL ¤t-series; interprets length specifications in character - column definitions in character units. (Some earlier MySQL - versions interpreted lengths in bytes.) + MySQL ¤t-series; interprets length specifications in + character column definitions in character units. (Some + earlier MySQL versions interpreted lengths in bytes.) </para> </listitem> @@ -1169,8 +1169,8 @@ </itemizedlist> <para> - For more about character set support in MySQL ¤t-series;, see - <xref linkend="charset"/>. + For more about character set support in MySQL ¤t-series;, + see <xref linkend="charset"/>. </para> <itemizedlist> @@ -1226,8 +1226,8 @@ A fixed-length string that is always right-padded with spaces to the specified length when stored. <replaceable>M</replaceable> represents the column length. - The range of <replaceable>M</replaceable> in MySQL ¤t-series; is 0 - to 255 characters. + The range of <replaceable>M</replaceable> in MySQL + ¤t-series; is 0 to 255 characters. </para> <para> @@ -1277,8 +1277,8 @@ <para> The <literal>UNICODE</literal> attribute can be specified in - MySQL ¤t-series; for <literal>CHAR</literal>. It assigns the - <literal>ucs2</literal> character set. + MySQL ¤t-series; for <literal>CHAR</literal>. It + assigns the <literal>ucs2</literal> character set. </para> <para> @@ -1358,12 +1358,12 @@ <para> A variable-length string. <replaceable>M</replaceable> - represents the maximum column length. In MySQL ¤t-series;, the - range of <replaceable>M</replaceable> is 0 to 255 before - MySQL 5.0.3, and 0 to 65,535 in MySQL 5.0.3 and later. (The - maximum actual length of a <literal>VARCHAR</literal> in - MySQL 5.0 is determined by the maximum row size and the - character set you use. The maximum + represents the maximum column length. In MySQL + ¤t-series;, the range of <replaceable>M</replaceable> + is 0 to 255 before MySQL 5.0.3, and 0 to 65,535 in MySQL + 5.0.3 and later. (The maximum actual length of a + <literal>VARCHAR</literal> in MySQL 5.0 is determined by the + maximum row size and the character set you use. The maximum <emphasis>effective</emphasis> length starting with MySQL 5.0.3 is 65,532 bytes.) </para> @@ -1394,10 +1394,10 @@ </para> <para> - In MySQL ¤t-series;, the <literal>BINARY</literal> attribute is - shorthand for specifying the binary collation of the column - character set. Sorting and comparison is based on numeric - character values. + In MySQL ¤t-series;, the <literal>BINARY</literal> + attribute is shorthand for specifying the binary collation + of the column character set. Sorting and comparison is based + on numeric character values. </para> <para> @@ -1551,9 +1551,9 @@ <para> An optional length <replaceable>M</replaceable> can be given - for this type in MySQL ¤t-series;. If this is done, then MySQL will - create the column as the smallest <literal>BLOB</literal> - type large enough to hold values of + for this type in MySQL ¤t-series;. If this is done, + then MySQL will create the column as the smallest + <literal>BLOB</literal> type large enough to hold values of <replaceable>M</replaceable> bytes. </para> @@ -1991,9 +1991,9 @@ Here, <quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote> means than values are displayed with up to - <replaceable>M</replaceable> decimal digits in total, of which - <replaceable>D</replaceable> decimal digits may be after the - decimal point. For example, a column defined as + <replaceable>M</replaceable> digits in total, of which + <replaceable>D</replaceable> digits may be after the decimal + point. For example, a column defined as <literal>FLOAT(7,4)</literal> will look like <literal>-999.9999</literal> when displayed. MySQL performs rounding when storing values, so if you insert @@ -2014,7 +2014,7 @@ For maximum portability, code requiring storage of approximate numeric data values should use <literal>FLOAT</literal> or <literal>DOUBLE PRECISION</literal> with no specification of - precision or number of decimal digits. + precision or number of digits. </para> <para> @@ -2033,9 +2033,9 @@ <para> In this example, <literal>5</literal> is the precision and <literal>2</literal> is the scale. The precision represents the - number of significant decimal digits that are stored for values, - and the scale represents the number of digits that can be stored - following the decimal point. + number of significant digits that are stored for values, and the + scale represents the number of digits that can be stored following + the decimal point. </para> <para> @@ -2057,9 +2057,9 @@ case, therefore, the range of values that can be stored in the <literal>salary</literal> column is from <literal>-999.99</literal> to <literal>999.99</literal>. MySQL - enforces this limit as of MySQL 5.0.3. Before 5.0.3, MySQL ¤t-series; - varied from this limit in that, on the positive end of the range, - the column could actually store numbers up to + enforces this limit as of MySQL 5.0.3. Before 5.0.3, MySQL + ¤t-series; varied from this limit in that, on the positive + end of the range, the column could actually store numbers up to <literal>9999.99</literal>. (For positive numbers, MySQL 5.0.2 and earlier used the byte reserved for the sign to extend the upper end of the range.) @@ -2075,8 +2075,8 @@ the implementation is allowed to decide the value of <replaceable>M</replaceable>. Both of these variant forms of the <literal>DECIMAL</literal> and <literal>NUMERIC</literal> data - types are supported in MySQL ¤t-series;. The default value of - <replaceable>M</replaceable> is 10. + types are supported in MySQL ¤t-series;. The default value + of <replaceable>M</replaceable> is 10. </para> <para> @@ -2728,16 +2728,17 @@ <literal>TIMESTAMP</literal> column type differed significantly in many ways from what is described in this section. If you need to convert older - <literal>TIMESTAMP</literal> data to work with MySQL ¤t-series;, be - sure to see the &title-refman-4-1; for details. + <literal>TIMESTAMP</literal> data to work with MySQL + ¤t-series;, be sure to see the &title-refman-4-1; for + details. </para> <para> - In MySQL ¤t-series;, <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>. + In MySQL ¤t-series;, <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> <para> @@ -2782,9 +2783,10 @@ </para> <para> - In MYSQL ¤t-series;, you have considerable flexibility in determining - when automatic <literal>TIMESTAMP</literal> initialization and - updating occur and which column should have those behaviors: + In MYSQL ¤t-series;, you have considerable flexibility + in determining when automatic <literal>TIMESTAMP</literal> + initialization and updating occur and which column should have + those behaviors: </para> <itemizedlist> @@ -2817,8 +2819,8 @@ above, <literal>MAXDB</literal> mode causes columns to be created as <literal>DATETIME</literal> columns.) The rules governing initialisation and updating of - <literal>TIMESTAMP</literal> columns in MySQL ¤t-series; are as - follows: + <literal>TIMESTAMP</literal> columns in MySQL ¤t-series; + are as follows: </para> <itemizedlist> @@ -2984,8 +2986,8 @@ </itemizedlist> <para> - In MySQL ¤t-series;, you can set the current time zone on a - per-connection basis, as described in + In MySQL ¤t-series;, you can set the current time zone + on a per-connection basis, as described in <xref linkend="time-zone-support"/>. <literal>TIMESTAMP</literal> values are stored in UTC, being converted from the current time zone for storage, and @@ -3440,11 +3442,12 @@ <para> Values in <literal>VARCHAR</literal> columns are variable-length - strings. In MySQL ¤t-series;, the length can be specified as 0 to 255 - before MySQL 5.0.3, and 0 to 65,535 in 5.0.3 and later versions. - (The maximum effective length of a <literal>VARCHAR</literal> in - MySQL ¤t-series; is determined by the maximum row size and the - character set used. The maximum length overall is 65,532 bytes.) + strings. In MySQL ¤t-series;, the length can be specified + as 0 to 255 before MySQL 5.0.3, and 0 to 65,535 in 5.0.3 and + later versions. (The maximum effective length of a + <literal>VARCHAR</literal> in MySQL ¤t-series; is + determined by the maximum row size and the character set used. + The maximum length overall is 65,532 bytes.) </para> <para> @@ -3810,12 +3813,12 @@ </itemizedlist> <para> - In MySQL ¤t-series;, <literal>LONG</literal> and <literal>LONG - VARCHAR</literal> map to the <literal>MEDIUMTEXT</literal> data - type. This is a compatibility feature. If you use the - <literal>BINARY</literal> attribute with a - <literal>TEXT</literal> column type, the column is assigned the - binary collation of the column character set. + In MySQL ¤t-series;, <literal>LONG</literal> and + <literal>LONG VARCHAR</literal> map to the + <literal>MEDIUMTEXT</literal> data type. This is a compatibility + feature. If you use the <literal>BINARY</literal> attribute with + a <literal>TEXT</literal> column type, the column is assigned + the binary collation of the column character set. </para> <para> @@ -4154,10 +4157,11 @@ <para> When retrieved, values stored into a <literal>SET</literal> column are displayed using the lettercase that was used in the - column definition. In MySQL ¤t-series;, <literal>SET</literal> columns - can be assigned a character set and collation. For binary or - case-sensitive collations, lettercase is taken into account when - assigning values to to the column. + column definition. In MySQL ¤t-series;, + <literal>SET</literal> columns can be assigned a character set + and collation. For binary or case-sensitive collations, + lettercase is taken into account when assigning values to to the + column. </para> <para> @@ -4485,8 +4489,8 @@ <para> As of MySQL 5.0.3, values for <literal>DECIMAL</literal> columns longer are represented using a binary format that packs nine - decimal digits into four bytes. Storage for the integer and - fractional parts of each value are determined separately. Each + decimal (base 10) digits into four bytes. Storage for the integer + and fractional parts of each value are determined separately. Each multiple of nine digits requires four bytes, and the "leftover" digits require some fraction of four bytes. The storage required for "leftover" digits is given by the following table: @@ -4728,9 +4732,9 @@ <literal>TEXT</literal> types, the values <replaceable>L</replaceable> and <replaceable>M</replaceable> in the preceding table should be interpreted as number of characters - in MySQL ¤t-series;, and lengths for these types in column specifications - indicate the number of characters. For example, to store a - <literal>TINYTEXT</literal> value requires + in MySQL ¤t-series;, and lengths for these types in column + specifications indicate the number of characters. For example, to + store a <literal>TINYTEXT</literal> value requires <replaceable>L</replaceable> characters + 1 byte. </para> @@ -4832,7 +4836,8 @@ format for <literal>DECIMAL</literal> columns. All basic calculation (<literal>+,-,*,/</literal>) with <literal>DECIMAL</literal> columns are done with precision of 64 - decimal digits. See <xref linkend="numeric-type-overview"/>. + decimal (base 10) digits. See + <xref linkend="numeric-type-overview"/>. </para> <para> --- 1.148/refman-common/news-5.0.xml 2005-09-08 12:19:52 -05:00 +++ 1.149/refman-common/news-5.0.xml 2005-09-08 14:14:37 -05:00 @@ -223,6 +223,14 @@ <listitem> <para> + Using <literal>GROUP BY</literal> when selecting from a view + in some cases could cause incorrect results to be returned. + (Bug #12922) + </para> + </listitem> + + <listitem> + <para> A lock wait timeout caused <literal>InnoDB</literal> to roll back the entire current transaction. Now it rolls back only the most recent SQL statement. (Bug #12308) --- 1.29/refman-4.1/column-types.xml 2005-09-06 16:15:45 -05:00 +++ 1.30/refman-4.1/column-types.xml 2005-09-08 14:36:08 -05:00 @@ -637,6 +637,47 @@ <listitem> <para> + <indexterm type="type"> + <primary>DOUBLE PRECISION data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>REAL data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>DOUBLE PRECISION</secondary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>REAL</secondary> + </indexterm> + + <literal>DOUBLE + PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> , + <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> + </para> + + <para> + These are synonyms for <literal>DOUBLE</literal>. Exception: + If the server SQL mode includes the + <literal>REAL_AS_FLOAT</literal> option, + <literal>REAL</literal> is a synonym for + <literal>FLOAT</literal> rather than + <literal>DOUBLE</literal>. + </para> + + <remark> + end_description_for_help_topic + </remark> + </listitem> + + <listitem> + <para> <indexterm> <primary>floating-point number</primary> </indexterm> @@ -695,47 +736,6 @@ </listitem> <listitem> - <para> - <indexterm type="type"> - <primary>DOUBLE PRECISION data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>REAL data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>DOUBLE PRECISION</secondary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>REAL</secondary> - </indexterm> - - <literal>DOUBLE - PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> , - <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> - </para> - - <para> - These are synonyms for <literal>DOUBLE</literal>. Exception: - If the server SQL mode includes the - <literal>REAL_AS_FLOAT</literal> option, - <literal>REAL</literal> is a synonym for - <literal>FLOAT</literal> rather than - <literal>DOUBLE</literal>. - </para> - - <remark> - end_description_for_help_topic - </remark> - </listitem> - - <listitem> <remark> description_for_help_topic DECIMAL ZEROFILL UNSIGNED NUMERIC DEC FIXED @@ -760,17 +760,17 @@ <literal>CHAR</literal> column; <quote>unpacked</quote> means the number is stored as a string, using one character for each digit of the value. <replaceable>M</replaceable> is - the total number of decimal digits and - <replaceable>D</replaceable> is the number of decimal digits - after the decimal point. The decimal point and (for negative - numbers) the ‘<literal>-</literal>’ sign are not - counted in <replaceable>M</replaceable>, although space for - them is reserved. If <replaceable>D</replaceable> is 0, - values have no decimal point or fractional part. The maximum - range of <literal>DECIMAL</literal> values is the same as - for <literal>DOUBLE</literal>, but the actual range for a - given <literal>DECIMAL</literal> column may be constrained - by the choice of <replaceable>M</replaceable> and + the total number of digits and <replaceable>D</replaceable> + is the number of digits after the decimal point. The decimal + point and (for negative numbers) the + ‘<literal>-</literal>’ sign are not counted in + <replaceable>M</replaceable>, although space for them is + reserved. If <replaceable>D</replaceable> is 0, values have + no decimal point or fractional part. The maximum range of + <literal>DECIMAL</literal> values is the same as for + <literal>DOUBLE</literal>, but the actual range for a given + <literal>DECIMAL</literal> column may be constrained by the + choice of <replaceable>M</replaceable> and <replaceable>D</replaceable>. If <replaceable>D</replaceable> is omitted, the default is 0. If <replaceable>M</replaceable> is omitted, the default is @@ -1993,9 +1993,9 @@ Here, <quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote> means than values are displayed with up to - <replaceable>M</replaceable> decimal digits in total, of which - <replaceable>D</replaceable> decimal digits may be after the - decimal point. For example, a column defined as + <replaceable>M</replaceable> digits in total, of which + <replaceable>D</replaceable> digits may be after the decimal + point. For example, a column defined as <literal>FLOAT(7,4)</literal> will look like <literal>-999.9999</literal> when displayed. MySQL performs rounding when storing values, so if you insert @@ -2016,7 +2016,7 @@ For maximum portability, code requiring storage of approximate numeric data values should use <literal>FLOAT</literal> or <literal>DOUBLE PRECISION</literal> with no specification of - precision or number of decimal digits. + precision or number of digits. </para> <para> @@ -2035,9 +2035,9 @@ <para> In this example, <literal>5</literal> is the precision and <literal>2</literal> is the scale. The precision represents the - number of significant decimal digits that are stored for values, - and the scale represents the number of digits that can be stored - following the decimal point. + number of significant digits that are stored for values, and the + scale represents the number of digits that can be stored following + the decimal point. </para> <para> --- 1.30/refman/column-types.xml 2005-09-06 16:12:17 -05:00 +++ 1.31/refman/column-types.xml 2005-09-08 14:36:08 -05:00 @@ -611,6 +611,45 @@ <listitem> <para> + <indexterm type="type"> + <primary>DOUBLE PRECISION data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>REAL data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>DOUBLE PRECISION</secondary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>REAL</secondary> + </indexterm> + + <literal>DOUBLE + PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> , + <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> + </para> + + <para> + These are synonyms for <literal>DOUBLE</literal>. Exception: + If the server SQL mode includes the + <literal>REAL_AS_FLOAT</literal> option, + <literal>REAL</literal> is a synonym for + <literal>FLOAT</literal> rather than + <literal>DOUBLE</literal>. + </para> + +<!-- end_description_for_help_topic --> + </listitem> + + <listitem> + <para> <indexterm> <primary>floating-point number</primary> </indexterm> @@ -669,45 +708,6 @@ </listitem> <listitem> - <para> - <indexterm type="type"> - <primary>DOUBLE PRECISION data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>REAL data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>DOUBLE PRECISION</secondary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>REAL</secondary> - </indexterm> - - <literal>DOUBLE - PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> , - <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> - </para> - - <para> - These are synonyms for <literal>DOUBLE</literal>. Exception: - If the server SQL mode includes the - <literal>REAL_AS_FLOAT</literal> option, - <literal>REAL</literal> is a synonym for - <literal>FLOAT</literal> rather than - <literal>DOUBLE</literal>. - </para> - -<!-- end_description_for_help_topic --> - </listitem> - - <listitem> <!-- description_for_help_topic DECIMAL ZEROFILL UNSIGNED NUMERIC DEC FIXED --> <para> @@ -732,8 +732,8 @@ A packed <quote>exact</quote> fixed-point number. <replaceable>M</replaceable> is the total number of decimal digits (the precision) and <replaceable>D</replaceable> is - the number of decimal digits after the decimal point (the - scale). The decimal point and (for negative numbers) the + the number of digits after the decimal point (the scale). + The decimal point and (for negative numbers) the ‘<literal>-</literal>’ sign are not counted in <replaceable>M</replaceable>. If <replaceable>D</replaceable> is 0, values have no decimal @@ -754,7 +754,7 @@ <para> All basic calculations (<literal>+, -, *, /</literal>) with <literal>DECIMAL</literal> columns are done with a precision - of 64 decimal digits. + of 64 digits. </para> <para> @@ -766,17 +766,17 @@ <literal>CHAR</literal> column; <quote>unpacked</quote> means the number is stored as a string, using one character for each digit of the value. <replaceable>M</replaceable> is - the total number of decimal digits and - <replaceable>D</replaceable> is the number of decimal digits - after the decimal point. The decimal point and (for negative - numbers) the ‘<literal>-</literal>’ sign are not - counted in <replaceable>M</replaceable>, although space for - them is reserved. If <replaceable>D</replaceable> is 0, - values have no decimal point or fractional part. The maximum - range of <literal>DECIMAL</literal> values is the same as - for <literal>DOUBLE</literal>, but the actual range for a - given <literal>DECIMAL</literal> column may be constrained - by the choice of <replaceable>M</replaceable> and + the total number of digits and <replaceable>D</replaceable> + is the number of digits after the decimal point. The decimal + point and (for negative numbers) the + ‘<literal>-</literal>’ sign are not counted in + <replaceable>M</replaceable>, although space for them is + reserved. If <replaceable>D</replaceable> is 0, values have + no decimal point or fractional part. The maximum range of + <literal>DECIMAL</literal> values is the same as for + <literal>DOUBLE</literal>, but the actual range for a given + <literal>DECIMAL</literal> column may be constrained by the + choice of <replaceable>M</replaceable> and <replaceable>D</replaceable>. If <replaceable>D</replaceable> is omitted, the default is 0. If <replaceable>M</replaceable> is omitted, the default is @@ -1949,9 +1949,9 @@ Here, <quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote> means than values are displayed with up to - <replaceable>M</replaceable> decimal digits in total, of which - <replaceable>D</replaceable> decimal digits may be after the - decimal point. For example, a column defined as + <replaceable>M</replaceable> digits in total, of which + <replaceable>D</replaceable> digits may be after the decimal + point. For example, a column defined as <literal>FLOAT(7,4)</literal> will look like <literal>-999.9999</literal> when displayed. MySQL performs rounding when storing values, so if you insert @@ -1972,7 +1972,7 @@ For maximum portability, code requiring storage of approximate numeric data values should use <literal>FLOAT</literal> or <literal>DOUBLE PRECISION</literal> with no specification of - precision or number of decimal digits. + precision or number of digits. </para> <para> @@ -1991,9 +1991,9 @@ <para> In this example, <literal>5</literal> is the precision and <literal>2</literal> is the scale. The precision represents the - number of significant decimal digits that are stored for values, - and the scale represents the number of digits that can be stored - following the decimal point. + number of significant digits that are stored for values, and the + scale represents the number of digits that can be stored following + the decimal point. </para> <para> @@ -4877,8 +4877,8 @@ <para> As of MySQL 5.0.3, values for <literal>DECIMAL</literal> columns longer are represented using a binary format that packs nine - decimal digits into four bytes. Storage for the integer and - fractional parts of each value are determined separately. Each + decimal (base 10) digits into four bytes. Storage for the integer + and fractional parts of each value are determined separately. Each multiple of nine digits requires four bytes, and the "leftover" digits require some fraction of four bytes. The storage required for "leftover" digits is given by the following table: @@ -5225,7 +5225,8 @@ format for <literal>DECIMAL</literal> columns. All basic calculation (<literal>+,-,*,/</literal>) with <literal>DECIMAL</literal> columns are done with precision of 64 - decimal digits. See <xref linkend="numeric-type-overview"/>. + decimal (base 10) digits. See + <xref linkend="numeric-type-overview"/>. </para> <para> --- 1.24/refman-5.0/column-types.xml 2005-09-06 16:15:51 -05:00 +++ 1.25/refman-5.0/column-types.xml 2005-09-08 14:36:08 -05:00 @@ -32,8 +32,8 @@ </para> <para> - MySQL ¤t-series; supports extensions for handing spatial data. Information - about spatial types is provided in + MySQL ¤t-series; supports extensions for handing spatial data. + Information about spatial types is provided in <xref linkend="spatial-extensions-in-mysql"/>. </para> @@ -466,8 +466,8 @@ </para> <para> - MySQL ¤t-series; can handle <literal>BIGINT</literal> in the - following cases: + MySQL ¤t-series; can handle + <literal>BIGINT</literal> in the following cases: </para> <itemizedlist> @@ -654,6 +654,43 @@ <listitem> <para> + <indexterm type="type"> + <primary>DOUBLE PRECISION data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>REAL data type</primary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>DOUBLE PRECISION</secondary> + </indexterm> + + <indexterm type="type"> + <primary>data type</primary> + <secondary>REAL</secondary> + </indexterm> + + <literal>DOUBLE + PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> , + <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] + [UNSIGNED] [ZEROFILL]</literal> + </para> + + <para> + These are synonyms for <literal>DOUBLE</literal>. Exception: + If the server SQL mode includes the + <literal>REAL_AS_FLOAT</literal> option, + <literal>REAL</literal> is a synonym for + <literal>FLOAT</literal> rather than + <literal>DOUBLE</literal>. + </para> + </listitem> + + <listitem> + <para> <indexterm> <primary>floating-point number</primary> </indexterm> @@ -705,43 +742,6 @@ </listitem> <listitem> - <para> - <indexterm type="type"> - <primary>DOUBLE PRECISION data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>REAL data type</primary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>DOUBLE PRECISION</secondary> - </indexterm> - - <indexterm type="type"> - <primary>data type</primary> - <secondary>REAL</secondary> - </indexterm> - - <literal>DOUBLE - PRECISION[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> , - <literal>REAL[(<replaceable>M</replaceable>,<replaceable>D</replaceable>)] - [UNSIGNED] [ZEROFILL]</literal> - </para> - - <para> - These are synonyms for <literal>DOUBLE</literal>. Exception: - If the server SQL mode includes the - <literal>REAL_AS_FLOAT</literal> option, - <literal>REAL</literal> is a synonym for - <literal>FLOAT</literal> rather than - <literal>DOUBLE</literal>. - </para> - </listitem> - - <listitem> <remark> description_for_help_topic DECIMAL ZEROFILL UNSIGNED NUMERIC DEC FIXED @@ -769,8 +769,8 @@ A packed <quote>exact</quote> fixed-point number. <replaceable>M</replaceable> is the total number of decimal digits (the precision) and <replaceable>D</replaceable> is - the number of decimal digits after the decimal point (the - scale). The decimal point and (for negative numbers) the + the number of digits after the decimal point (the scale). + The decimal point and (for negative numbers) the ‘<literal>-</literal>’ sign are not counted in <replaceable>M</replaceable>. If <replaceable>D</replaceable> is 0, values have no decimal @@ -791,7 +791,7 @@ <para> All basic calculations (<literal>+, -, *, /</literal>) with <literal>DECIMAL</literal> columns are done with a precision - of 64 decimal digits. + of 64 digits. </para> <para> @@ -803,17 +803,17 @@ <literal>CHAR</literal> column; <quote>unpacked</quote> means the number is stored as a string, using one character for each digit of the value. <replaceable>M</replaceable> is - the total number of decimal digits and - <replaceable>D</replaceable> is the number of decimal digits - after the decimal point. The decimal point and (for negative - numbers) the ‘<literal>-</literal>’ sign are not - counted in <replaceable>M</replaceable>, although space for - them is reserved. If <replaceable>D</replaceable> is 0, - values have no decimal point or fractional part. The maximum - range of <literal>DECIMAL</literal> values is the same as - for <literal>DOUBLE</literal>, but the actual range for a - given <literal>DECIMAL</literal> column may be constrained - by the choice of <replaceable>M</replaceable> and + the total number of digits and <replaceable>D</replaceable> + is the number of digits after the decimal point. The decimal + point and (for negative numbers) the + ‘<literal>-</literal>’ sign are not counted in + <replaceable>M</replaceable>, although space for them is + reserved. If <replaceable>D</replaceable> is 0, values have + no decimal point or fractional part. The maximum range of + <literal>DECIMAL</literal> values is the same as for + <literal>DOUBLE</literal>, but the actual range for a given + <literal>DECIMAL</literal> column may be constrained by the + choice of <replaceable>M</replaceable> and <replaceable>D</replaceable>. If <replaceable>D</replaceable> is omitted, the default is 0. If <replaceable>M</replaceable> is omitted, the default is @@ -994,8 +994,8 @@ </para> <para> - In MySQL ¤t-series;, <literal>TIMESTAMP</literal> is returned as a - string in the format <literal>'YYYY-MM-DD + In MySQL ¤t-series;, <literal>TIMESTAMP</literal> is + returned as a string in the format <literal>'YYYY-MM-DD HH:MM:SS'</literal>whose 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. @@ -1098,9 +1098,9 @@ </para> <para> - MySQL ¤t-series; string data types include some features that you may - not have encountered in working with versions of MySQL prior to - 4.1: + MySQL ¤t-series; string data types include some features + that you may not have encountered in working with versions of + MySQL prior to 4.1: </para> <itemizedlist> @@ -1138,9 +1138,9 @@ <listitem> <para> - MySQL ¤t-series; interprets length specifications in character - column definitions in character units. (Some earlier MySQL - versions interpreted lengths in bytes.) + MySQL ¤t-series; interprets length specifications in + character column definitions in character units. (Some + earlier MySQL versions interpreted lengths in bytes.) </para> </listitem> @@ -1169,8 +1169,8 @@ </itemizedlist> <para> - For more about character set support in MySQL ¤t-series;, see - <xref linkend="charset"/>. + For more about character set support in MySQL ¤t-series;, + see <xref linkend="charset"/>. </para> <itemizedlist> @@ -1226,8 +1226,8 @@ A fixed-length string that is always right-padded with spaces to the specified length when stored. <replaceable>M</replaceable> represents the column length. - The range of <replaceable>M</replaceable> in MySQL ¤t-series; is 0 - to 255 characters. + The range of <replaceable>M</replaceable> in MySQL + ¤t-series; is 0 to 255 characters. </para> <para> @@ -1277,8 +1277,8 @@ <para> The <literal>UNICODE</literal> attribute can be specified in - MySQL ¤t-series; for <literal>CHAR</literal>. It assigns the - <literal>ucs2</literal> character set. + MySQL ¤t-series; for <literal>CHAR</literal>. It + assigns the <literal>ucs2</literal> character set. </para> <para> @@ -1358,12 +1358,12 @@ <para> A variable-length string. <replaceable>M</replaceable> - represents the maximum column length. In MySQL ¤t-series;, the - range of <replaceable>M</replaceable> is 0 to 255 before - MySQL 5.0.3, and 0 to 65,535 in MySQL 5.0.3 and later. (The - maximum actual length of a <literal>VARCHAR</literal> in - MySQL 5.0 is determined by the maximum row size and the - character set you use. The maximum + represents the maximum column length. In MySQL + ¤t-series;, the range of <replaceable>M</replaceable> + is 0 to 255 before MySQL 5.0.3, and 0 to 65,535 in MySQL + 5.0.3 and later. (The maximum actual length of a + <literal>VARCHAR</literal> in MySQL 5.0 is determined by the + maximum row size and the character set you use. The maximum <emphasis>effective</emphasis> length starting with MySQL 5.0.3 is 65,532 bytes.) </para> @@ -1394,10 +1394,10 @@ </para> <para> - In MySQL ¤t-series;, the <literal>BINARY</literal> attribute is - shorthand for specifying the binary collation of the column - character set. Sorting and comparison is based on numeric - character values. + In MySQL ¤t-series;, the <literal>BINARY</literal> + attribute is shorthand for specifying the binary collation + of the column character set. Sorting and comparison is based + on numeric character values. </para> <para> @@ -1551,9 +1551,9 @@ <para> An optional length <replaceable>M</replaceable> can be given - for this type in MySQL ¤t-series;. If this is done, then MySQL will - create the column as the smallest <literal>BLOB</literal> - type large enough to hold values of + for this type in MySQL ¤t-series;. If this is done, + then MySQL will create the column as the smallest + <literal>BLOB</literal> type large enough to hold values of <replaceable>M</replaceable> bytes. </para> @@ -1991,9 +1991,9 @@ Here, <quote><literal>(<replaceable>M</replaceable>,<replaceable>D</replaceable>)</literal></quote> means than values are displayed with up to - <replaceable>M</replaceable> decimal digits in total, of which - <replaceable>D</replaceable> decimal digits may be after the - decimal point. For example, a column defined as + <replaceable>M</replaceable> digits in total, of which + <replaceable>D</replaceable> digits may be after the decimal + point. For example, a column defined as <literal>FLOAT(7,4)</literal> will look like <literal>-999.9999</literal> when displayed. MySQL performs rounding when storing values, so if you insert @@ -2014,7 +2014,7 @@ For maximum portability, code requiring storage of approximate numeric data values should use <literal>FLOAT</literal> or <literal>DOUBLE PRECISION</literal> with no specification of - precision or number of decimal digits. + precision or number of digits. </para> <para> @@ -2033,9 +2033,9 @@ <para> In this example, <literal>5</literal> is the precision and <literal>2</literal> is the scale. The precision represents the - number of significant decimal digits that are stored for values, - and the scale represents the number of digits that can be stored - following the decimal point. + number of significant digits that are stored for values, and the + scale represents the number of digits that can be stored following + the decimal point. </para> <para> @@ -2057,9 +2057,9 @@ case, therefore, the range of values that can be stored in the <literal>salary</literal> column is from <literal>-999.99</literal> to <literal>999.99</literal>. MySQL - enforces this limit as of MySQL 5.0.3. Before 5.0.3, MySQL ¤t-series; - varied from this limit in that, on the positive end of the range, - the column could actually store numbers up to + enforces this limit as of MySQL 5.0.3. Before 5.0.3, MySQL + ¤t-series; varied from this limit in that, on the positive + end of the range, the column could actually store numbers up to <literal>9999.99</literal>. (For positive numbers, MySQL 5.0.2 and earlier used the byte reserved for the sign to extend the upper end of the range.) @@ -2075,8 +2075,8 @@ the implementation is allowed to decide the value of <replaceable>M</replaceable>. Both of these variant forms of the <literal>DECIMAL</literal> and <literal>NUMERIC</literal> data - types are supported in MySQL ¤t-series;. The default value of - <replaceable>M</replaceable> is 10. + types are supported in MySQL ¤t-series;. The default value + of <replaceable>M</replaceable> is 10. </para> <para> @@ -2728,16 +2728,17 @@ <literal>TIMESTAMP</literal> column type differed significantly in many ways from what is described in this section. If you need to convert older - <literal>TIMESTAMP</literal> data to work with MySQL ¤t-series;, be - sure to see the &title-refman-4-1; for details. + <literal>TIMESTAMP</literal> data to work with MySQL + ¤t-series;, be sure to see the &title-refman-4-1; for + details. </para> <para> - In MySQL ¤t-series;, <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>. + In MySQL ¤t-series;, <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> <para> @@ -2782,9 +2783,10 @@ </para> <para> - In MYSQL ¤t-series;, you have considerable flexibility in determining - when automatic <literal>TIMESTAMP</literal> initialization and - updating occur and which column should have those behaviors: + In MYSQL ¤t-series;, you have considerable flexibility + in determining when automatic <literal>TIMESTAMP</literal> + initialization and updating occur and which column should have + those behaviors: </para> <itemizedlist> @@ -2817,8 +2819,8 @@ above, <literal>MAXDB</literal> mode causes columns to be created as <literal>DATETIME</literal> columns.) The rules governing initialisation and updating of - <literal>TIMESTAMP</literal> columns in MySQL ¤t-series; are as - follows: + <literal>TIMESTAMP</literal> columns in MySQL ¤t-series; + are as follows: </para> <itemizedlist> @@ -2984,8 +2986,8 @@ </itemizedlist> <para> - In MySQL ¤t-series;, you can set the current time zone on a - per-connection basis, as described in + In MySQL ¤t-series;, you can set the current time zone + on a per-connection basis, as described in <xref linkend="time-zone-support"/>. <literal>TIMESTAMP</literal> values are stored in UTC, being converted from the current time zone for storage, and @@ -3440,11 +3442,12 @@ <para> Values in <literal>VARCHAR</literal> columns are variable-length - strings. In MySQL ¤t-series;, the length can be specified as 0 to 255 - before MySQL 5.0.3, and 0 to 65,535 in 5.0.3 and later versions. - (The maximum effective length of a <literal>VARCHAR</literal> in - MySQL ¤t-series; is determined by the maximum row size and the - character set used. The maximum length overall is 65,532 bytes.) + strings. In MySQL ¤t-series;, the length can be specified + as 0 to 255 before MySQL 5.0.3, and 0 to 65,535 in 5.0.3 and + later versions. (The maximum effective length of a + <literal>VARCHAR</literal> in MySQL ¤t-series; is + determined by the maximum row size and the character set used. + The maximum length overall is 65,532 bytes.) </para> <para> @@ -3810,12 +3813,12 @@ </itemizedlist> <para> - In MySQL ¤t-series;, <literal>LONG</literal> and <literal>LONG - VARCHAR</literal> map to the <literal>MEDIUMTEXT</literal> data - type. This is a compatibility feature. If you use the - <literal>BINARY</literal> attribute with a - <literal>TEXT</literal> column type, the column is assigned the - binary collation of the column character set. + In MySQL ¤t-series;, <literal>LONG</literal> and + <literal>LONG VARCHAR</literal> map to the + <literal>MEDIUMTEXT</literal> data type. This is a compatibility + feature. If you use the <literal>BINARY</literal> attribute with + a <literal>TEXT</literal> column type, the column is assigned + the binary collation of the column character set. </para> <para> @@ -4485,8 +4488,8 @@ <para> As of MySQL 5.0.3, values for <literal>DECIMAL</literal> columns longer are represented using a binary format that packs nine - decimal digits into four bytes. Storage for the integer and - fractional parts of each value are determined separately. Each + decimal (base 10) digits into four bytes. Storage for the integer + and fractional parts of each value are determined separately. Each multiple of nine digits requires four bytes, and the "leftover" digits require some fraction of four bytes. The storage required for "leftover" digits is given by the following table: @@ -4730,9 +4733,9 @@ <literal>TEXT</literal> types, the values <replaceable>L</replaceable> and <replaceable>M</replaceable> in the preceding table should be interpreted as number of characters - in MySQL ¤t-series;, and lengths for these types in column specifications - indicate the number of characters. For example, to store a - <literal>TINYTEXT</literal> value requires + in MySQL ¤t-series;, and lengths for these types in column + specifications indicate the number of characters. For example, to + store a <literal>TINYTEXT</literal> value requires <replaceable>L</replaceable> characters + 1 byte. </para> @@ -4834,7 +4837,8 @@ format for <literal>DECIMAL</literal> columns. All basic calculation (<literal>+,-,*,/</literal>) with <literal>DECIMAL</literal> columns are done with precision of 64 - decimal digits. See <xref linkend="numeric-type-overview"/>. + decimal (base 10) digits. See + <xref linkend="numeric-type-overview"/>. </para> <para>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3511) | paul | 8 Sep |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.286 sec. using MySQL 5.1.14-beta-log