On Friday, 18 April 2014 18:09:11 UTC+2, Parsifal wrote: > > I guess doctrine actually requires an integer primary key? >
No, that is certainly not the case, fortunately. On Friday, 18 April 2014 18:09:11 UTC+2, Parsifal wrote: > or there should be some mistakes in $metadata->mapField? > Anyway, I did not write it myself it was generated by convert-mapping, I > just created a table with rule as primary key and generated > convert-mapping. what is wrong there? should I change something in > $metadata->mapField or in db? > Yes, but I don't know exactly what happens. A wild guess: making the rule-field the id in the mapField() makes that column already needing unique values. So there is no need for that uniqueConstraints-attribute in the Table-setting. Maybe by also defining that it wants to generate a rule-column besides the primary key. It's just a bit vague idea. I would first try to leave that uniqueConstraints-part out. Do you then still get the same error-message? -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
