Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
D
doctrine-dbal
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Tomáš Trávníček
doctrine-dbal
Commits
dfaaf005
Unverified
Commit
dfaaf005
authored
Feb 19, 2018
by
Jasper Mattsson
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Documentation: Warn against using object fields in MySQL and MariaDB
parent
ef89ba84
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
0 deletions
+8
-0
types.rst
docs/en/reference/types.rst
+8
-0
No files found.
docs/en/reference/types.rst
View file @
dfaaf005
...
...
@@ -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
``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::
Because the built-in ``text`` type of PostgreSQL does not support NULL bytes,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment