Re: Bug in insert of bidirectionally mapped many-to-one relationships

2007-02-08 Thread Jeff Melching
s, and insert in the correct order (TEST_LOOKUP then TEST_DATATYPES). But if you then set the "TEST_LOOKUP_ID" column to be not-null, we go back to inserting in the wrong order. Is that correct? On Feb 8, 2007, at 6:56 AM, Jeff Melching wrote: > ok, that worked but only if i make t

Re: Bug in insert of bidirectionally mapped many-to-one relationships

2007-02-08 Thread Jeff Melching
e(ForeignKeys=true)". If that isn't the issue, can you clarify why this is causing problems? On Feb 7, 2007, at 9:09 AM, Jeff Melching wrote: > > > > > > > I have a bidirectional mapping of a many-to-one relationship as listed > below. If I have the following

Bug in insert of bidirectionally mapped many-to-one relationships

2007-02-07 Thread Jeff Melching
I have a bidirectional mapping of a many-to-one relationship as listed below. If I have the following code: TestDatatypes blob = new TestDatatypes(); TestLookup lookup = new TestLookup(); Set tdts = new HashSet(); tdts.add(blob);