Skip to content

Explain that doctrine:mapping:import will be removed soon #9193

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

Closed
wants to merge 2 commits into from
Closed
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
14 changes: 8 additions & 6 deletions doctrine/reverse_engineering.rst
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,14 @@
How to Generate Entities from an Existing Database
==================================================

.. caution::

The feature explained in this article doesn't work in modern Symfony
applications that have no bundles. The workaround is to temporarily create
a bundle. See `doctrine/doctrine#729`_ for details. Moreover, this feature
to generate entities from existing databases will be completely removed in
the next Doctrine version.

When starting work on a brand new project that uses a database, two different
situations comes naturally. In most cases, the database model is designed
and built from scratch. Sometimes, however, you'll start with an existing and
Expand Down Expand Up @@ -54,12 +62,6 @@ is to ask Doctrine to introspect the database and generate the corresponding
metadata files. Metadata files describe the entity class to generate based on
table fields.

.. caution::

If your application has *no* bundles, then this command will currently fail!
The workaround, is to temporarily create a bundle. See `doctrine/doctrine#729`_
for details.

.. code-block:: terminal

$ php bin/console doctrine:mapping:import --force AppBundle xml
Expand Down