From 9f2fb49a3d81c362f52abb4842dc9b5de0817765 Mon Sep 17 00:00:00 2001 From: 77web Date: Tue, 30 Apr 2013 19:44:19 +0900 Subject: [PATCH 1/4] [cookbook][doctrine/reverse_engineering] fixed extension prefix for mapping file generated by doctrine:mapping:convert --- cookbook/doctrine/reverse_engineering.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cookbook/doctrine/reverse_engineering.rst b/cookbook/doctrine/reverse_engineering.rst index 7ac4b458208..af71cf777bf 100644 --- a/cookbook/doctrine/reverse_engineering.rst +++ b/cookbook/doctrine/reverse_engineering.rst @@ -71,7 +71,7 @@ folder of your bundle. 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 From 0eb5149b20b9cd6a759339d037e8faf426d31fc5 Mon Sep 17 00:00:00 2001 From: 77web Date: Tue, 30 Apr 2013 19:56:46 +0900 Subject: [PATCH 2/4] [cookbook][doctrine/reverse_engineering] fixed output path specification for yml or xml mapping file --- cookbook/doctrine/reverse_engineering.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cookbook/doctrine/reverse_engineering.rst b/cookbook/doctrine/reverse_engineering.rst index af71cf777bf..1e19166531e 100644 --- a/cookbook/doctrine/reverse_engineering.rst +++ b/cookbook/doctrine/reverse_engineering.rst @@ -60,10 +60,10 @@ 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:: From de792c4e7740f3968734c29b0ec0a58a6ecc33e6 Mon Sep 17 00:00:00 2001 From: 77web Date: Tue, 30 Apr 2013 20:57:57 +0900 Subject: [PATCH 3/4] [cookbook][doctrine/reverse_engineering] add description to insert namespace --- cookbook/doctrine/reverse_engineering.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/cookbook/doctrine/reverse_engineering.rst b/cookbook/doctrine/reverse_engineering.rst index 1e19166531e..3ca0133641a 100644 --- a/cookbook/doctrine/reverse_engineering.rst +++ b/cookbook/doctrine/reverse_engineering.rst @@ -92,6 +92,12 @@ The generated ``BlogPost.orm.xml`` metadata file looks as follows: +Then you should insert proper namespace in ``name`` attribute of ``entity`` element like this: + +.. code-block:: xml + + + .. note:: If you have ``oneToMany`` relationships between your entities, From 43b5306ece822edc1374b53821cd67d91fe744f4 Mon Sep 17 00:00:00 2001 From: 77web Date: Tue, 30 Apr 2013 19:58:53 +0900 Subject: [PATCH 4/4] [cookbook][doctrine/reverse_engineering]changed the second command to execute from doctrine:mapping:import to doctrine:mapping:convert --- cookbook/doctrine/reverse_engineering.rst | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/cookbook/doctrine/reverse_engineering.rst b/cookbook/doctrine/reverse_engineering.rst index 3ca0133641a..809c8a115c8 100644 --- a/cookbook/doctrine/reverse_engineering.rst +++ b/cookbook/doctrine/reverse_engineering.rst @@ -105,16 +105,14 @@ Then you should insert proper namespace in ``name`` attribute of ``entity`` elem 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