Hi Marco, I've been buzzy with this case for about 2 days now. I've come up with a function test class (12 tests so far) that reproduce the bug in several use-cases:
- OneToOne: normal, with composite id, with composite id including a foreign one) - OneToMany: " - ManyToMany: " - Removal of join-table rows (3 cases) There's also an issue with storing the values of the join-table of ManyToMany (fixed as well), and with storing the value of a foreign key which is itself also a foreign key (the "with composite id including a foreign one" case). I'm having some difficulties with the that last one, and can sure use some help! I'll do a PR tomorrow and explain things in more detail. PS: @Menno I have a "conditional join" (the relation_table + relation_id kind), which I want to be able to persist in a single flush. When using generated ids that's not possible, so I'm trying UUIDs. I want them stored as binary for performance reasons (mainly because string-compares are expensive). -- Jasper N. Brouwer (@jaspernbrouwer) On 5 November 2014 at 19:42:17, Menno Holtkamp ([email protected]) wrote: > And while you are at it, can you also describie why you want to uae the > UUIDs: > - as primary key > - stored in binary format > > Just being curious ;) > > Cheers! > On Nov 5, 2014 5:56 PM, "Marco Pivetta" wrote: > > > Hi Jasper, > > > > This looks like a bug to me: may want to abstract it into a test case and > > see if it's still there. > > > > Marco Pivetta > > > > http://twitter.com/Ocramius > > > > http://ocramius.github.com/ -- 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.
