DDC-953: CLI tools orm:generate-entities --regenerate-entities=1 flag will generate empty entities 50% of time. #1193

Closed
opened 2026-01-22 13:05:31 +01:00 by admin · 4 comments
Owner

Originally created by @doctrinebot on GitHub (Dec 28, 2010).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user flynsarmy:

Running the command:
doctrine orm:generate-entities --regenerate-entities=1 --generate-annotations=1 ./

50% of the time my entity will appear as:

<?php namespace models; /**** - models\Role * - @Table(name="roles") - @Entity(repositoryClass="models\repositories\RoleRepository") */ class Role { } The other 50% everything will be in there. In addition, if the --regenerate-entities=1 argument is removed, if I change the data in my YAML schema file for a column (such as changing length=255 to length=50 on a string), the annotations won't be updated when the updated entity is generated. It seems only new fields are being added to the entity files which is why --regenerate-entities=1 was required in the first place.
Originally created by @doctrinebot on GitHub (Dec 28, 2010). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user flynsarmy: Running the command: doctrine orm:generate-entities --regenerate-entities=1 --generate-annotations=1 ./ 50% of the time my entity will appear as: <?php namespace models; /**** - models\Role * - @Table(name="roles") - @Entity(repositoryClass="models\repositories\RoleRepository") */ class Role { } The other 50% everything will be in there. In addition, if the --regenerate-entities=1 argument is removed, if I change the data in my YAML schema file for a column (such as changing length=255 to length=50 on a string), the annotations won't be updated when the updated entity is generated. It seems only new fields are being added to the entity files which is why --regenerate-entities=1 was required in the first place.
admin added the Bug label 2026-01-22 13:05:31 +01:00
admin closed this issue 2026-01-22 13:05:33 +01:00
Author
Owner

@doctrinebot commented on GitHub (Feb 2, 2011):

Comment created by @beberlei:

Fixed

@doctrinebot commented on GitHub (Feb 2, 2011): Comment created by @beberlei: Fixed
Author
Owner

@doctrinebot commented on GitHub (Feb 8, 2011):

Comment created by flynsarmy:

This issue is still not fixed in 2.0.1. Simply run orm:generate-entities --regenerate-entities=1 --generate-annotations=1 to replicate.

@doctrinebot commented on GitHub (Feb 8, 2011): Comment created by flynsarmy: This issue is still not fixed in 2.0.1. Simply run orm:generate-entities --regenerate-entities=1 --generate-annotations=1 to replicate.
Author
Owner

@doctrinebot commented on GitHub (Feb 8, 2011):

Comment created by @beberlei:

Yes, because this issue is fixed in 2.0.2 not in 2.0.1.

@doctrinebot commented on GitHub (Feb 8, 2011): Comment created by @beberlei: Yes, because this issue is fixed in 2.0.2 not in 2.0.1.
Author
Owner

@doctrinebot commented on GitHub (Feb 8, 2011):

Issue was closed with resolution "Fixed"

@doctrinebot commented on GitHub (Feb 8, 2011): Issue was closed with resolution "Fixed"
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#1193