Author: jstephens
Date: 2005-12-16 10:41:58 +0100 (Fri, 16 Dec 2005)
New Revision: 575
Log:
Misc. remarks about working with BLOBs (response to user comments).
Modified:
trunk/refman-4.1/data-types.xml
trunk/refman-5.0/data-types.xml
trunk/refman-5.1/data-types.xml
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2005-12-16 08:17:32 UTC (rev 574)
+++ trunk/refman-4.1/data-types.xml 2005-12-16 09:41:58 UTC (rev 575)
@@ -4348,6 +4348,19 @@
in contrast to all other data types, for which storage is
allocated once per column when the table is opened.
</para>
+
+ <para>
+ In some cases, it may be desirable to store binary data such as
+ media files in <literal>BLOB</literal> or
+ <literal>TEXT</literal> columns. You may find MySQL's string
+ handling functions useful for working with such data. See
+ <xref linkend="string-functions"/>. For security and other
+ reasons, it is usually preferable to do so using application
+ code rather than allowing application users the
+ <literal>FILE</literal> privilege. You can discuss specifics for
+ various languages and platforms in the MySQL Forums
+ (<ulink url="http://forums.mysql.com/"/>).
+ </para>
</section>
Modified: trunk/refman-5.0/data-types.xml
===================================================================
--- trunk/refman-5.0/data-types.xml 2005-12-16 08:17:32 UTC (rev 574)
+++ trunk/refman-5.0/data-types.xml 2005-12-16 09:41:58 UTC (rev 575)
@@ -3995,9 +3995,7 @@
to fit. If the truncated characters are not spaces, a warning is
generated. You can cause an error to occur and the value to be
rejected rather than to be truncated with awarning by using
- strict SQL mode. See
- <xref
- linkend="server-sql-mode"/>.
+ strict SQL mode. See <xref linkend="server-sql-mode"/>.
</para>
<para>
@@ -4154,6 +4152,19 @@
in contrast to all other data types, for which storage is
allocated once per column when the table is opened.
</para>
+
+ <para>
+ In some cases, it may be desirable to store binary data such as
+ media files in <literal>BLOB</literal> or
+ <literal>TEXT</literal> columns. You may find MySQL's string
+ handling functions useful for working with such data. See
+ <xref linkend="string-functions"/>. For security and other
+ reasons, it is usually preferable to do so using application
+ code rather than allowing application users the
+ <literal>FILE</literal> privilege. You can discuss specifics for
+ various languages and platforms in the MySQL Forums
+ (<ulink url="http://forums.mysql.com/"/>).
+ </para>
</section>
Modified: trunk/refman-5.1/data-types.xml
===================================================================
--- trunk/refman-5.1/data-types.xml 2005-12-16 08:17:32 UTC (rev 574)
+++ trunk/refman-5.1/data-types.xml 2005-12-16 09:41:58 UTC (rev 575)
@@ -3993,6 +3993,19 @@
in contrast to all other data types, for which storage is
allocated once per column when the table is opened.
</para>
+
+ <para>
+ In some cases, it may be desirable to store binary data such as
+ media files in <literal>BLOB</literal> or
+ <literal>TEXT</literal> columns. You may find MySQL's string
+ handling functions useful for working with such data. See
+ <xref linkend="string-functions"/>. For security and other
+ reasons, it is usually preferable to do so using application
+ code rather than allowing application users the
+ <literal>FILE</literal> privilege. You can discuss specifics for
+ various languages and platforms in the MySQL Forums
+ (<ulink url="http://forums.mysql.com/"/>).
+ </para>
</section>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r575 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 16 Dec |
