> Here is the model:
>
> ElectronicDocument <-->>TextblockReference<<-->Textblock. TextblockReference
> is more than a simple m:n join table. However I have a flattened m:n
> relationship between ElectronicDocument (called textblocks) and Textblock
> (called documents) across TextblockReference
On Apr 26, 2011, at 9:28 AM, David LeBer wrote:
>
> On 2011-04-26, at 9:08 AM, David Avendasora wrote:
>
>>
>> On Apr 26, 2011, at 8:20 AM, Markus Ruggiero wrote:
>>
>>> What confuses me is that there are delete rules for both directions of a
>>> relationship which makes no sense to me.
>>
On 2011-04-26, at 9:08 AM, David Avendasora wrote:
>
> On Apr 26, 2011, at 8:20 AM, Markus Ruggiero wrote:
>
>> What confuses me is that there are delete rules for both directions of a
>> relationship which makes no sense to me.
>
> Please give us more information about these two relationship
On Apr 26, 2011, at 8:20 AM, Markus Ruggiero wrote:
> What confuses me is that there are delete rules for both directions of a
> relationship which makes no sense to me.
Please give us more information about these two relationships. Cascade Delete
rules should not go in both directions. I can'
Hi,
I have a fairly complex structure of several entities (actually this is not so
complex after all). Eventually when I try to delete an ElectronicDocument (this
is a pure ERD2W app, no custom delete() stuff) my application throws up with
java.lang.IllegalStateException: A valid global ID coul