Useful Doctrine 2 Console Commands

Doctrine 2′s console is really powerful when you know how to use it. You can generate entity classes and their method stubs, reverse-engineer a database, validate your entity schemas, and much more. In this post, I’m going to cover some of the Doctrine console’s more useful commands and explain how you can use them to reduce development time. For a full overview of the Doctrine 2 console, read the Doctrine Tools documentation.


Validate that your mapping files are correct and that your database is in sync. Not only does it ensure that your database is up-to-date, it finds errors in your mapping files, detects invalid entity relationships, and even warns you when your naming conventions are inconsistent.

Usage: orm:validate-schema
Example output:

[Mapping]  FAIL - The entity-class 'modelsAlbum' mapping is invalid:
* The mappings modelsAlbum#tracks and modelsSong#album are incosistent with each other.

[Mapping]  FAIL - The entity-class 'modelsGenre' mapping is invalid:
* The field modelsGenre#related_genres is on the owning side of a bi-directional relationship, but the specified mappedBy association on the target-entity modelsGenre#
does not contain the required 'inversedBy' attribute.

[Mapping]  FAIL - The entity-class 'modelsSong' mapping is invalid:
* The association modelsSong#album refers to the inverse side field modelsAlbum#songs which does not exist.

[Mapping]  FAIL - The entity-class 'modelsSongFile' mapping is invalid:
* The association modelsSongFile#downloads is ordered by a foreign field COUNT(id) that is not a field on the target entity modelsDownload

[Database] FAIL - The database schema is not in sync with the current mapping file.


Convert a Doctrine 1 schema to Doctrine 2 format. This command can save you a lot of time and headaches when migrating projects from Doctrine 1 to Doctrine 2. The conversions I’ve tested are really accurate, but it would pay to check that everything looks okay after doing a conversion.

Usage: orm:convert-d1-schema from-path to-type dest-path
Example: orm:convert-d1-schema models/d1-models annotation models

In the above example, all of my Doctrine 1 schema files contained in ./models/d1-models will be converted to Doctrine 2 annotation format and saved in ./models. The original D1 schemas will not be modified.


Convert your mapping information between different formats. There probably aren’t many situations where you would need to convert your mapping information to a different format, but the feature that makes this command really useful is the --from-database flag. Using the --from-database flag allows you to essentially reverse-engineer a database by creating the mapping information from the database schema.

Usage: orm:convert-mapping to-type dest-path
Example: orm:convert-mapping --from-database annotation models/generated

The above example will read my database schema and create the entities with annotation mapping in my ./models/generated directory. Omitting the --from-database flag would cause the command to read my existing mapping information and convert it to annotation format in the ./models/generated directory.


Generate entity classes with getter and setter methods from your mapping information. The --regenerate-entities="1" flag will cause your entities to be re-generated even if they exist already. You can also use the --generate-annotations flag to automatically generate annotation metadata on your entities (only useful if your mapping information is not already in annotation format).

For a better idea of what this command can do, run orm:generate-entities --help.

Usage: orm:generate-entities dest-path
Example: orm:generate-entities --generate-annotations="true" models/generated

This example will read my mapping information and create the entity classes in ./models/generated. It will also generate annotation metadata for my entity classes.

Did you find this post useful?

  • Korede Lawrence Oluwafemi

    Thanks for this nice article, please I have an issue that I want you to help me with…. I created my mappings inside a directory called export, now I tried generating my entities using this command >php doctrine orm:generate-entities –generate-annotations=”true” src/entities, but it complains of no metadata classes to process. Please help me out

  • J. Fernando Galvez

    hi.. im learn how to work with a codeigniter and Doctrine and your
    tutorial is so greate but i can generate the methos with a commands,
    i follow that steps.

    1.- use orm:convert-mapping –from-database annotation models

    and generate a php file with the properties.. thats fine.

    2.- orm:generate-entities –generate-annotations=”true” models

    —>>now the error.

    C:xamppphpphp.exe C:xampphtdocscodeDoapplicationdoctrine
    –ansi orm:generate-entities –generate-annotations=true models

    No Metadata Classes to process.


    i wanna generate the methods for the properties… thk. a lot.. :D

  • Pingback: Zend Framework 2 : Generate Doctrine Entities from Existing Database using DoctrineModule and DoctrineORMModule | Welcome to Abdul Malik Ikhsan's Blog

  • annonymous

    Thanks a lot. Was really helpful

  • Mido

    Hi ,

    after writing this command

    php doctrine orm:convert-mapping –from-database annotation models/generated

    the class generated correctly from database but without any method,after that I write this command for generating entities

    php doctrine orm:generate-entities –regenerate-entities=”1″ models/generated

    but I find this error “No Metadata classes to process”


  • Pingback: Integrating Doctrine 2 with CodeIgniter 2 | Wildly Inaccurate

  • Coiby

    Another thing is how to generate procted properties of entity as disscussed @google group:

    Short question: will it be possible to tell Doctrine to generate the
    entities with protected class fields instead of private?

    The scenario:
    class UserGenerated{
    private $id; //<– option to generate them as protected
    private $username;
    private $password;

    class User extends UserGenerated{


    The problem is that when generating entities, doctrine makes the
    fields private, resulting in a fatal error: Fatal error: Uncaught
    exception 'ReflectionException' with message 'Property name does not

    What we would like to do:
    During development, the entities change frequently. We would like to
    regenerate the entities everytime the tableschema is changed. In our
    prototype we tell doctrine to generate the UserGenerated class (using
    the EntityGenerator). The developer creates the User class that
    doctrine actually uses for crud operations. So basicly we generate on
    the fly two different mappings: A "generation mapping" to generate the
    *Generated classes, en a "runtime mapping" so doctrine talks in the
    classnames we actually want to use. Reason for this setup is we can
    regenerate the entities at will everythime without having to worry
    about code the developer allready has written in the entities.

  • Coiby

    Hi, would you talk something on generating models from yamls? Thanks!

  • mahfuz

    php doctrine orm:generate-entities –generate-annotations “1″ “../generated”

    this works

  • John Burchell

    Great Article, it’s right up my alley… Now where do I go from here?

    I’ve followed your previous CI+Doctrine article, when I load doctrine library, I get a blank page even though it’s a simple echo hello from the controller.

    @Andrea – I think if you put an additional ../models/generated at the end it will put everything there. I haven’t tried the =true yet.

  • Andrea

    I also receive the message “Unkonown database type set requested, Doctrine May not support it”

    • Drew Spencer

      Hi Andrea, i think the “Not enough argument” problem is due to not putting =true on the additional parameters.

      I was getting the same error and put –generate-annotations=true instead of just –generate-annotations and that worked for me.

  • Andrea

    I tried orm:generate-entities –generate-annotations –regenerate-entities ../models/generated but I receive

    Not enough argument

    and if I pass argument I don’t receive errors but anything happen.

    • Jonathan

      I also get this error.

      • Joseph

        See Drew Spencer’s comment, above. I’ve corrected the post to show the correct use of these flags.