Naming options for the orm:convert-mapping and orm:generate-entities commands #6164

Closed
opened 2026-01-22 15:28:04 +01:00 by admin · 1 comment
Owner

Originally created by @cooperll on GitHub (Jan 25, 2019).

Originally assigned to: @Ocramius on GitHub.

Feature Request

Q A
New Feature yes
RFC yes?
BC Break yes?

Summary

When reverse engineering a database for use with Doctrine, all of the xml and later the entities generated (by the orm:convert-mapping and orm:generate-entities commands respecitvely) do not respect camel case with regards to our table and column names.

An example column generated in one of the tables' XML files:




The "dateNum" column is clearly read just fine, but Doctrine doesn't appear to have any option in the documentation to let name="dateNum" instead of "datenum". The same applies to table names, and then later to .php models.

For our large database, the thought of writing a script to manually correct all of these issues in the XML so we can move to Doctrine is enough to turn people off of Doctrine, especially if we'd have to be running the convert-mapping command multiple times over a period while we move towards Doctrine entirely.

Originally created by @cooperll on GitHub (Jan 25, 2019). Originally assigned to: @Ocramius on GitHub. ### Feature Request <!-- Fill in the relevant information below to help triage your issue. --> | Q | A |------------ | ------ | New Feature | yes | RFC | yes? | BC Break | yes? #### Summary <!-- Provide a summary of the feature you would like to see implemented. --> When reverse engineering a database for use with Doctrine, all of the xml and later the entities generated (by the orm:convert-mapping and orm:generate-entities commands respecitvely) do not respect camel case with regards to our table and column names. An example column generated in one of the tables' XML files: <field name="datenum" type="integer" column="dateNum" nullable="true"> <options> <option name="unsigned"/> </options> </field> The "dateNum" column is clearly read just fine, but Doctrine doesn't appear to have any option in the documentation to let name="dateNum" instead of "datenum". The same applies to table names, and then later to .php models. For our large database, the thought of writing a script to manually correct all of these issues in the XML so we can move to Doctrine is enough to turn people off of Doctrine, especially if we'd have to be running the convert-mapping command multiple times over a period while we move towards Doctrine entirely.
admin added the ImprovementWon't Fix labels 2026-01-22 15:28:04 +01:00
admin closed this issue 2026-01-22 15:28:04 +01:00
Author
Owner

@Ocramius commented on GitHub (Jan 28, 2019):

Entity generation is deprecated is not going to be improved anymore, sorry.

@Ocramius commented on GitHub (Jan 28, 2019): Entity generation is deprecated is not going to be improved anymore, sorry.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: doctrine/archived-orm#6164