Unverified Commit ad403747 authored by Marco Pivetta's avatar Marco Pivetta Committed by GitHub

Merge pull request #3027 from Jasu/docs-warn-against-object-in-mysql

Documentation: Warn against using object fields in MySQL and MariaDB
parents ef89ba84 dfaaf005
...@@ -479,6 +479,14 @@ using deserialization or ``null`` if no data is present. ...@@ -479,6 +479,14 @@ using deserialization or ``null`` if no data is present.
properly on vendors not supporting column comments and will fall back to properly on vendors not supporting column comments and will fall back to
``text`` type instead. ``text`` type instead.
.. warning::
While the built-in ``text`` type of MySQL and MariaDB can store binary data,
``mysqldump`` cannot properly export ``text`` fields containing binary data.
This will cause creating and restoring of backups fail silently. A workaround is
to ``serialize()``/``unserialize()`` and ``base64_encode()``/``base64_decode()``
PHP objects and store them into a ``text`` field manually.
.. warning:: .. warning::
Because the built-in ``text`` type of PostgreSQL does not support NULL bytes, Because the built-in ``text`` type of PostgreSQL does not support NULL bytes,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment