I’m trying to set up a project using Doctrine 2.3.2 on a database-first implementation. after generating the xml and the mappings, then calling orm:validate-schema it shows me that the mapping is right but the database validation fails. In using the schema tool to find out where my issues I’m finding 2 issues are repeating over and over:
- change all my varchars that aren’t already at 255 to varchar(255)
- drop my primary key with for example the columns (A, B, C) and then create a new primary key with the same columns in a different order (B, A, C)
Both of these things seem meaningless to change. Why would Doctrine force me to change my schema in ways that seem meaningless?
The solution to both of these without changing the database schema is:
- the convert-mapping doesn’t appear to add the length property to the id field – add it to the xml
- This appears to be caused by a difference between the order of the columns in the table, and the order of the columns in the Primary Key. Re-order the order of the xml entries to match the order of the Primary Key.
Having to 2 #1 I’m assuming is a bug – which I will report soon. However, is #2 above a bug or does changing the order mess with Doctrine’s logic in some way?
The more I think about this the more I believe it to be an oversight and not done intentionally. I was thinking there was something I was missing but I think these are issues with the library and have added them doctrine’s JIRA.
EDIT: Links per request