Thomas Tourlourat - Armetiz
added a comment - 20/Oct/11 2:58 PM I think I have find the problem.
See patch.
I have test the modification, it seem to be okay.
In the 2.1.2 version, If the first related object wasn't a "nonemptyComponents", the ObjectHydrator initialized the collection by a specific way.

Thomas Tourlourat - Armetiz
added a comment - 25/Oct/11 9:32 AM No problem, It was blocking for me.
But I don't understand why this bug doesn't appear to other users. Because of that, I'm wondering if it's a real bug or a miss configuration on my app.
To be sure, the best will be to create a new test, but I'm not really familiar to create ORM test case..
Thomas.

I have post all the mapping, but it's Doctrine compliant.
PlayerEntity extends PlayerBaseEntity, and Option is a standalone Entity.
All define an auto generated identifier.
The join table is correctly configured.

Do you need this mapping to create tests ?
To sum-up, this is a simply ManyToMany relation between an inheritance Entity & a simple Entity.