Skip to content

[cookbook][doctrine] fixed reverse_engineering doc #2578

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.

Sign up for GitHub

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 4 commits into from
Jun 4, 2013
Merged

[cookbook][doctrine] fixed reverse_engineering doc #2578

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9f2fb49
[cookbook][doctrine/reverse_engineering] fixed extension prefix for m…
77web Apr 30, 2013
0eb5149
[cookbook][doctrine/reverse_engineering] fixed output path specificat…
77web Apr 30, 2013
de792c4
[cookbook][doctrine/reverse_engineering] add description to insert na…
77web Apr 30, 2013
43b5306
[cookbook][doctrine/reverse_engineering]changed the second command to…
77web Apr 30, 2013
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
20 changes: 12 additions & 8 deletions cookbook/doctrine/reverse_engineering.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,18 +60,18 @@ tables fields.

.. code-block:: bash

$ php app/console doctrine:mapping:convert xml ./src/Acme/BlogBundle/Resources/config/doctrine/metadata/orm --from-database --force
$ php app/console doctrine:mapping:convert xml ./src/Acme/BlogBundle/Resources/config/doctrine --from-database --force

This command line tool asks Doctrine to introspect the database and generate
the XML metadata files under the ``src/Acme/BlogBundle/Resources/config/doctrine/metadata/orm``
the XML metadata files under the ``src/Acme/BlogBundle/Resources/config/doctrine``
folder of your bundle.

.. tip::

It's also possible to generate metadata class in YAML format by changing the
first argument to `yml`.

The generated ``BlogPost.dcm.xml`` metadata file looks as follows:
The generated ``BlogPost.orm.xml`` metadata file looks as follows:

.. code-block:: xml

Expand All @@ -92,23 +92,27 @@ The generated ``BlogPost.dcm.xml`` metadata file looks as follows:
</entity>
</doctrine-mapping>

Then you should insert proper namespace in ``name`` attribute of ``entity`` element like this:

.. code-block:: xml

<entity name="Acme\BlogBundle\BlogPost" table="blog_post">

.. note::

If you have ``oneToMany`` relationships between your entities,
you will need to edit the generated ``xml`` or ``yml`` files to add
a section on the specific entities for ``oneToMany`` defining the
``inversedBy`` and the ``mappedBy`` pieces.

Once the metadata files are generated, you can ask Doctrine to import the
schema and build related entity classes by executing the following two commands.
Once the metadata files are generated, you can ask Doctrine to build related entity classes by executing the following two commands.

.. code-block:: bash

$ php app/console doctrine:mapping:import AcmeBlogBundle annotation
$ php app/console doctrine:mapping:convert annotation ./src
$ php app/console doctrine:generate:entities AcmeBlogBundle

The first command generates entity classes with an annotations mapping, but
you can of course change the ``annotation`` argument to ``xml`` or ``yml``.
The first command generates entity classes with an annotations mapping. But if you want to use yml or xml mapping instead of annotations, you should execute the second command only.
The newly created ``BlogComment`` entity class looks as follow:

.. code-block:: php
Expand Down