php - Why does the column order in a composite primary key matter to Doctrine? -
i'm trying set project using doctrine 2.3.2 on database-first implementation. after generating xml , mappings, calling orm:validate-schema shows me mapping right database validation fails. in using schema tool find out issues i'm finding 2 issues repeating on , over:
change varchars aren't @ 255 varchar(255) drop primary key illustration columns (a, b, c) , create new primary key same columns in different order (b, a, c)both of these things seem meaningless change. why doctrine forcefulness me alter schema in ways seem meaningless?
the solution both of these without changing database schema is:
the convert-mapping doesn't appear add together length property id field - add together xml this appears caused difference between order of columns in table, , order of columns in primary key. re-order order of xml entries match order of primary key.having 2 #1 i'm assuming bug - study soon. however, #2 above bug or changing order mess doctrine's logic in way?
the more think more believe oversight , not done intentionally. thinking there missing think these issues library , have added them doctrine's jira.
edit: links per request
http://www.doctrine-project.org/jira/browse/ddc-2280 http://www.doctrine-project.org/jira/browse/ddc-2281 php mysql doctrine2