[DDC-2281] Validation against database-first generated xml requires that the column order within a composite primary key match the order the columns are in in mapping xml Created: 06/Feb/13 Updated: 09/May/13
|Project:||Doctrine 2 - ORM|
|Reporter:||Aaron Moore||Assignee:||Benjamin Eberlei|
In using a database-first approach utilizing orm:convert-mapping to generate xml, the validation and schema-tool reports that my composite primary key (ex. Columns A, C, B) be dropped and added in the order in which the mapping appears in the xml (ex. Columns A, B, C).
These columns are not auto-increment and are simply a mixture of int and varchar.
|Comment by Benjamin Eberlei [ 09/May/13 ]|
Is the composite key a mix of association and field types?
|Comment by Aaron Moore [ 09/May/13 ]|
I'm trying to remember the usage as it was a short term project but I believe it is.
For example a user has a userid.
The table in question might have a primary key consisting of the userid and an int representing a year..