Author: paul
Date: 2008-10-29 21:09:05 +0100 (Wed, 29 Oct 2008)
New Revision: 12195
Log:
r35089@frost: paul | 2008-10-29 15:04:45 -0500
Add auto-link markup for integer data types
Modified:
trunk/dynamic-docs/changelog/connector-j.xml
trunk/dynamic-docs/changelog/connector-net.xml
trunk/dynamic-docs/changelog/connector-odbc.xml
trunk/dynamic-docs/changelog/mysqld-1.xml
trunk/dynamic-docs/changelog/mysqld.xml
trunk/refman-4.1/apis-c.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:35088
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:35089
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:33695
Modified: trunk/dynamic-docs/changelog/connector-j.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-j.xml 2008-10-29 20:08:50 UTC (rev 12194)
+++ trunk/dynamic-docs/changelog/connector-j.xml 2008-10-29 20:09:05 UTC (rev 12195)
Changed blocks: 6, Lines Added: 7, Lines Deleted: 7; 2276 bytes
@@ -2132,7 +2132,7 @@
<para>
Return <literal>java.lang.Integer</literal> for
- <literal>TINYINT</literal> and <literal>SMALLINT</literal> types
+ <literal role="type">TINYINT</literal> and <literal role="type">SMALLINT</literal> types
from <literal>ResultSetMetaData.getColumnClassName()</literal>.
</para>
@@ -7128,7 +7128,7 @@
<message>
<para>
- Unsigned <literal>SMALLINT</literal> treated as signed for
+ Unsigned <literal role="type">SMALLINT</literal> treated as signed for
<literal>ResultSet.getInt()</literal>, fixed all cases for
<literal>UNSIGNED</literal> integer values and server-side
prepared statements, as well as
@@ -7443,7 +7443,7 @@
<para>
<literal>ResultSet.getObject()</literal> on
- <literal>TINYINT</literal> and <literal>SMALLINT</literal>
+ <literal role="type">TINYINT</literal> and <literal role="type">SMALLINT</literal>
columns should return Java type <literal>Integer</literal>.
</para>
@@ -8401,8 +8401,8 @@
<para>
<literal>getObject()</literal> on <literal>ResultSet</literal>
correctly does
- <literal>TINYINT</literal>-><literal>Byte</literal> and
- <literal>SMALLINT</literal>-><literal>Short</literal>.
+ <literal role="type">TINYINT</literal>-><literal>Byte</literal> and
+ <literal role="type">SMALLINT</literal>-><literal>Short</literal>.
</para>
</message>
@@ -14564,7 +14564,7 @@
<para>
Fixed <literal>ResultSetMetaData.isSigned()</literal> for
- <literal>TINYINT</literal> and <literal>BIGINT</literal>.
+ <literal role="type">TINYINT</literal> and <literal role="type">BIGINT</literal>.
</para>
</message>
@@ -18110,7 +18110,7 @@
<para>
Java type conversion may be incorrect for
- <literal>MEDIUMINT</literal>.
+ <literal role="type">MEDIUMINT</literal>.
</para>
</message>
Modified: trunk/dynamic-docs/changelog/connector-net.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-net.xml 2008-10-29 20:08:50 UTC (rev 12194)
+++ trunk/dynamic-docs/changelog/connector-net.xml 2008-10-29 20:09:05 UTC (rev 12195)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1027 bytes
@@ -498,12 +498,12 @@
Performing <function>GetValue()</function> on a field
<literal>TINYINT(1)</literal> returned a
<literal>BOOLEAN</literal>. While not a bug, this caused
- problems in software that expected an <literal>INT</literal> to
+ problems in software that expected an <literal role="type">INT</literal> to
be returned. A new connection string option <literal>Treat Tiny
As Boolean</literal> has been added with a default value of
<literal>true</literal>. If set to <literal>false</literal> the
provider will treat <literal>TINYINT(1)</literal> as
- <literal>INT</literal>.
+ <literal role="type">INT</literal>.
</para>
</message>
Modified: trunk/dynamic-docs/changelog/connector-odbc.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc.xml 2008-10-29 20:08:50 UTC (rev 12194)
+++ trunk/dynamic-docs/changelog/connector-odbc.xml 2008-10-29 20:09:05 UTC (rev 12195)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 681 bytes
@@ -450,7 +450,7 @@
<para>
Using a linked table in Access 2003 where the table has a
- <literal>BIGINT</literal> column as the first column in the
+ <literal role="type">BIGINT</literal> column as the first column in the
table, and is configured as the primary key, shows
<literal>#DELETED</literal> for all rows of the table.
</para>
Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-29 20:08:50 UTC (rev 12194)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml 2008-10-29 20:09:05 UTC (rev 12195)
Changed blocks: 3, Lines Added: 13, Lines Deleted: 4; 1657 bytes
@@ -11712,9 +11712,9 @@
<firstterm>attribute promotion</firstterm>; that is, data from a
column of a given type can be restored to a column using a
<quote>larger</quote> type. For example, Cluster backup data
- taken from a <literal>SMALLINT</literal> column can be restored
- to a <literal>MEDIUMINT</literal>, <literal>INT</literal>, or
- <literal>BIGINT</literal> column.
+ taken from a <literal role="type">SMALLINT</literal> column can be restored
+ to a <literal role="type">MEDIUMINT</literal>, <literal role="type">INT</literal>, or
+ <literal role="type">BIGINT</literal> column.
</para>
<para>
@@ -14317,7 +14317,7 @@
<para>
On some 64-bit systems, inserting the largest negative value
- into a <literal>BIGINT</literal> column resulted in incorrect
+ into a <literal role="type">BIGINT</literal> column resulted in incorrect
data.
</para>
@@ -30077,6 +30077,15 @@
</para>
</listitem>
+ <listitem>
+ <para>
+A new statement, <literal>FLUSH BACKUP LOGS</literal>, closes and reopens the backup log files.
+A new option for
+ <literal role="cfunc">mysql_refresh()</literal>,
+<literal>REFRESH_BACKUP_LOG</literal>, performs the same operation.
+ </para>
+ </listitem>
+
</itemizedlist>
</message>
Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml 2008-10-29 20:08:50 UTC (rev 12194)
+++ trunk/dynamic-docs/changelog/mysqld.xml 2008-10-29 20:09:05 UTC (rev 12195)
Changed blocks: 26, Lines Added: 30, Lines Deleted: 30; 9849 bytes
@@ -3755,7 +3755,7 @@
<para>
Using <literal>SELECT</literal> on a table that uses two
- <literal>INT</literal> columns with a single index would fail to
+ <literal role="type">INT</literal> columns with a single index would fail to
return rows that queried both columns and complex comparison
operators.
</para>
@@ -8229,7 +8229,7 @@
<replaceable>integer_constant</replaceable></literal>, the
server created the column using the <literal>DECIMAL</literal>
data type for large negative values that are within the range of
- <literal>BIGINT</literal>.
+ <literal role="type">BIGINT</literal>.
</para>
</message>
@@ -8549,7 +8549,7 @@
<para>
For the <literal role="func">FLOOR()</literal> and
<literal role="func">CEILING()</literal> functions, the return
- type is no longer always <literal>BIGINT</literal>. For
+ type is no longer always <literal role="type">BIGINT</literal>. For
exact-value numeric arguments, the return value has an
exact-value numeric type. For string or floating-point
arguments, the return value has a floating-point type.
@@ -9503,7 +9503,7 @@
<message>
<para>
- A large <literal>BIGINT</literal> value specified in a
+ A large <literal role="type">BIGINT</literal> value specified in a
<literal>WHERE</literal> clause could be treated differently
depending on whether it is specified as a quoted string. (For
example, <literal>WHERE bigint_col =
@@ -11478,7 +11478,7 @@
<para>
<literal>libmysql</literal> crashed when attempting to fetch the
- value of a <literal>MEDIUMINT</literal> column.
+ value of a <literal role="type">MEDIUMINT</literal> column.
</para>
</message>
@@ -12758,7 +12758,7 @@
<para>
The <literal role="func">CONV()</literal> function returned an
- unsigned <literal>BIGINT</literal> number, which does not fit in
+ unsigned <literal role="type">BIGINT</literal> number, which does not fit in
32 bits.
</para>
@@ -33870,7 +33870,7 @@
<para>
Using the <function>TRUNCATE()</function> function with a
negative number for the second argument on a
- <literal>BIGINT</literal> column returned incorrect results.
+ <literal role="type">BIGINT</literal> column returned incorrect results.
</para>
</message>
@@ -49367,7 +49367,7 @@
<message>
<para>
- Signed <literal>BIGINT</literal> would not accept
+ Signed <literal role="type">BIGINT</literal> would not accept
<literal>-9223372036854775808</literal> as a
<literal>DEFAULT</literal> value.
</para>
@@ -49463,8 +49463,8 @@
<literal>NDB</literal> tables having <literal>MEDIUMINT
AUTO_INCREMENT</literal> columns were not restored correctly by
<command>ndb_restore</command>, causing spurious duplicate key
- errors. This issue did not affect <literal>TINYINT</literal>,
- <literal>INT</literal>, or <literal>BIGINT</literal> columns
+ errors. This issue did not affect <literal role="type">TINYINT</literal>,
+ <literal role="type">INT</literal>, or <literal role="type">BIGINT</literal> columns
with <literal>AUTO_INCREMENT</literal>.
</para>
@@ -50989,7 +50989,7 @@
<para>
The result for <literal role="func">CAST()</literal> when
casting a value to <literal>UNSIGNED</literal> was limited to
- the maximum signed <literal>BIGINT</literal> value
+ the maximum signed <literal role="type">BIGINT</literal> value
(9223372036854775808), rather than the maximum unsigned value
(18446744073709551615).
</para>
@@ -56800,7 +56800,7 @@
<literal>MAXIMUM_SIZE</literal>, and
<literal>AUTOEXTEND_SIZE</literal> columns incorrectly were
being stored as <literal>VARCHAR</literal> rather than
- <literal>BIGINT</literal>. .
+ <literal role="type">BIGINT</literal>. .
</para>
</message>
@@ -59070,7 +59070,7 @@
<para>
In addition, when the underlying tables contained a
- <literal>TINYINT</literal> or <literal>CHAR(1)</literal> column,
+ <literal role="type">TINYINT</literal> or <literal>CHAR(1)</literal> column,
the <literal>MERGE</literal> storage engine incorrectly reported
that they differed from the <literal>MERGE</literal> table in
certain cases.
@@ -65966,8 +65966,8 @@
<para>
Changed metadata for result of <literal>SHOW KEYS</literal>:
Data type for <literal>Sub_part</literal> column now is
- <literal>SMALLINT</literal> rather than
- <literal>TINYINT</literal> because key part length can be longer
+ <literal role="type">SMALLINT</literal> rather than
+ <literal role="type">TINYINT</literal> because key part length can be longer
than 255.
</para>
@@ -66571,9 +66571,9 @@
<para>
<literal>DESCRIBE</literal> returned the type
- <literal>BIGINT</literal> for a column of a view if the column
+ <literal role="type">BIGINT</literal> for a column of a view if the column
was specified by an expression over values of the type
- <literal>INT</literal>.
+ <literal role="type">INT</literal>.
</para>
</message>
@@ -69274,7 +69274,7 @@
<para>
<literal role="func">INET_ATON()</literal> returned a signed
- <literal>BIGINT</literal> value, not an unsigned value.
+ <literal role="type">BIGINT</literal> value, not an unsigned value.
</para>
</message>
@@ -72667,7 +72667,7 @@
The output from <command>ndb_restore
<option>--print_data</option></command> was incorrect for a
backup made of a database containing tables with
- <literal>TINYINT</literal> or <literal>SMALLINT</literal>
+ <literal role="type">TINYINT</literal> or <literal role="type">SMALLINT</literal>
columns.
</para>
@@ -73953,7 +73953,7 @@
<message>
<para>
- The semantics of <literal>BIGINT</literal> depended on
+ The semantics of <literal role="type">BIGINT</literal> depended on
platform-specific characteristics.
</para>
@@ -77849,7 +77849,7 @@
<message>
<para>
- <literal>TINYINT</literal> columns were not handled correctly in
+ <literal role="type">TINYINT</literal> columns were not handled correctly in
the binary protocol. The problem was specific to platforms where
the C compiler has the <literal>char</literal> data type
unsigned by default.
@@ -99787,7 +99787,7 @@
<para>
Storing values specified as hexadecimal values 64 or more bits
- long into <literal>BIGINT</literal> or <literal>BIGINT
+ long into <literal role="type">BIGINT</literal> or <literal>BIGINT
UNSIGNED</literal> columns did not raise any warning or error if
the value was out of range.
</para>
@@ -99798,7 +99798,7 @@
<para>
Storing values specified as hexadecimal values 64 or more bits
- long in <literal>BIT(64)</literal>, <literal>BIGINT</literal>,
+ long in <literal>BIT(64)</literal>, <literal role="type">BIGINT</literal>,
or <literal>BIGINT UNSIGNED</literal> columns did not raise any
warning or error if the value was out of range.
</para>
@@ -102370,8 +102370,8 @@
<literal>RENAME</literal> clause in combination with a
<literal>MODIFY</literal> or <literal>CHANGE</literal> that did
not actually change the table (for example, when it changed a
- column's type from <literal>INT</literal> to
- <literal>INT</literal>). The behavior caused by this bug
+ column's type from <literal role="type">INT</literal> to
+ <literal role="type">INT</literal>). The behavior caused by this bug
differed according to whether or not the storage engine used by
the table was transactional or non-transactional. For
transactional tables (such as those using the
@@ -108128,7 +108128,7 @@
<message>
<para>
- Unsigned <literal>BIGINT</literal> values treated as signed
+ Unsigned <literal role="type">BIGINT</literal> values treated as signed
values by the <literal role="func">MOD()</literal> function.
</para>
@@ -114004,7 +114004,7 @@
<message>
<para>
- <literal>MEDIUMINT</literal> columns were not handled in the
+ <literal role="type">MEDIUMINT</literal> columns were not handled in the
same way as other column types by partition pruning.
</para>
@@ -119503,7 +119503,7 @@
<para>
<literal>ORDER BY</literal> did not always work correctly with
- <literal>SMALLINT</literal> columns.
+ <literal role="type">SMALLINT</literal> columns.
</para>
</message>
@@ -126930,7 +126930,7 @@
<para>
<literal>mysqlbinlog</literal> was failing the test suite on
Windows due to <literal>BOOL</literal> being incorrectly cast to
- <literal>INT</literal>.
+ <literal role="type">INT</literal>.
</para>
</message>
@@ -139260,7 +139260,7 @@
<para>
The server crashed on optimizations involving a join of
- <literal>INT</literal> and <literal>MEDIUMINT</literal> columns
+ <literal role="type">INT</literal> and <literal role="type">MEDIUMINT</literal> columns
and a system variable in the <literal>WHERE</literal> clause.
</para>
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 104 bytes
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r12195 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-6.0 refman-common | paul.dubois | 29 Oct |
