Skip to content

[Doctrine] Restore tip regarding schema filtering during migrations #17299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 25, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions messenger.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1439,6 +1439,36 @@ a table named ``messenger_messages``.
Or, to create the table yourself, set the ``auto_setup`` option to ``false`` and
:ref:`generate a migration <doctrine-creating-the-database-tables-schema>`.

.. tip::

To avoid tools like Doctrine Migrations from trying to remove this table because
it's not part of your normal schema, you can set the ``schema_filter`` option:

.. configuration-block::

.. code-block:: yaml

# config/packages/doctrine.yaml
doctrine:
dbal:
schema_filter: '~^(?!messenger_messages)~'

.. code-block:: xml

# config/packages/doctrine.xml
<doctrine:dbal schema-filter="~^(?!messenger_messages)~"/>

.. code-block:: php

# config/packages/doctrine.php
$container->loadFromExtension('doctrine', [
'dbal' => [
'schema_filter' => '~^(?!messenger_messages)~',
// ...
],
// ...
]);

.. caution::

The datetime property of the messages stored in the database uses the
Expand Down