Author: paul
Date: 2007-07-24 22:09:14 +0200 (Tue, 24 Jul 2007)
New Revision: 7196
Log:
r27877@polar: paul | 2007-07-24 13:45:18 -0500
Add descriptions for what happens for truncation of BINARY/VARBINARY values.
Modified:
trunk/refman-4.1/data-types.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
trunk/refman-5.2/data-types.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27872
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22908
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27877
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22908
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2007-07-24 18:15:51 UTC (rev 7195)
+++ trunk/refman-4.1/data-types.xml 2007-07-24 20:09:14 UTC (rev 7196)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 677 bytes
@@ -4611,6 +4611,13 @@
of the <literal>BLOB</literal> data types instead.
</para>
+ <para>
+ If you assign a value to a <literal>BINARY</literal> or
+ <literal>VARBINARY</literal> column that exceeds the column's
+ maximum length, the value is truncated to fit. If the truncated
+ characters are not spaces, a warning is generated.
+ </para>
+
</section>
<section id="blob">
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2007-07-24 18:15:51 UTC (rev 7195)
+++ trunk/refman-5.0/data-types.xml 2007-07-24 20:09:14 UTC (rev 7196)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 870 bytes
@@ -4416,6 +4416,16 @@
<literal>BLOB</literal> data types instead.
</para>
+ <para>
+ If strict SQL mode is not enabled and you assign a value to a
+ <literal>BINARY</literal> or <literal>VARBINARY</literal>
column
+ that exceeds the column's maximum length, the value is truncated
+ to fit and a warning is generated. For cases of truncation, you
+ can cause an error to occur (rather than a warning) and suppress
+ insertion of the value by using strict SQL mode. See
+ <xref linkend="server-sql-mode"/>.
+ </para>
+
</section>
<section id="blob">
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2007-07-24 18:15:51 UTC (rev 7195)
+++ trunk/refman-5.1/data-types.xml 2007-07-24 20:09:14 UTC (rev 7196)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 870 bytes
@@ -4180,6 +4180,16 @@
<literal>BLOB</literal> data types instead.
</para>
+ <para>
+ If strict SQL mode is not enabled and you assign a value to a
+ <literal>BINARY</literal> or <literal>VARBINARY</literal>
column
+ that exceeds the column's maximum length, the value is truncated
+ to fit and a warning is generated. For cases of truncation, you
+ can cause an error to occur (rather than a warning) and suppress
+ insertion of the value by using strict SQL mode. See
+ <xref linkend="server-sql-mode"/>.
+ </para>
+
</section>
<section id="blob">
Modified: trunk/refman-5.2/data-types.xml
===================================================================
--- trunk/refman-5.2/data-types.xml 2007-07-24 18:15:51 UTC (rev 7195)
+++ trunk/refman-5.2/data-types.xml 2007-07-24 20:09:14 UTC (rev 7196)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 0; 870 bytes
@@ -4177,6 +4177,16 @@
<literal>BLOB</literal> data types instead.
</para>
+ <para>
+ If strict SQL mode is not enabled and you assign a value to a
+ <literal>BINARY</literal> or <literal>VARBINARY</literal>
column
+ that exceeds the column's maximum length, the value is truncated
+ to fit and a warning is generated. For cases of truncation, you
+ can cause an error to occur (rather than a warning) and suppress
+ insertion of the value by using strict SQL mode. See
+ <xref linkend="server-sql-mode"/>.
+ </para>
+
</section>
<section id="blob">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7196 - in trunk: . refman-4.1 refman-5.0 refman-5.1 refman-5.2 | paul | 24 Jul |