I've got this error again in another part of my schema. Since I don't
really understand what the cause is, I go through the attributes of
the DB entity switching off the "mandatory" option and seeing if the
problem goes away. Is there an easier way to recognise which attribute
is causing the problem? Is it a problem with the DB entity or with the
object entity?
Steve
On 4 Feb 2009, at 09:42, Andrus Adamchik wrote:
> Yes, the issues with auto-reverse relationships need to be fixed
> rather sooner than later, and to the best of my knowledge nobody is
> working on it right now. But this is certainly high on the list.
>
> Andrus
>
> On Feb 3, 2009, at 11:39 PM, Stephen Winnall wrote:
>
>> Is CAY-1009 (Bogus runtime relationships can mess up commit) due
>> for resolution any time soon? I think I've run into it whilst
>> modelling an m:n relationship. The work-around (making the
>> attributes in the intersect entity non-mandatory) works, but it
>> would be nice to do it properly.
>>
>> Steve
>>
>>
>
This archive was generated by hypermail 2.0.0 : Sat Feb 07 2009 - 20:04:08 EST