I have a Class that used to be a final class, no subclasses, but then
I decided to I really needed two classes each one having some of the
original classes attributes/relationships along with some additional
ones.
If I make two sublcasses, then go into the superclass and delete any
attributes/relationships that the two subclasses no longer share, it
deletes them from both subclasses as well. I then have to go back
into each subclass and re-add the ones that are specific to that
subclass.
What would be easier is to shut off the propagation, then manually
delete the attributes/relationships that I don't want anymore from
the subclasses.
With that said, you were wrong about not being able to shut off the
propagation. I just make the subclasses, then set their Parent to
null, which in effect turns off the propagation. Once I'm done
modifying the superclass I re-set the Parent entity. Simple.
Dave
On Feb 12, 2008, at 12:14 PM, Mike Schrag wrote:
> In what case is this wrong?
>
> On Feb 12, 2008, at 11:38 AM, David Avendasora wrote:
>
>> Okay. Looks like it's diving into the .plist files for me. :)
>>
>> On Feb 12, 2008, at 10:05 AM, Mike Schrag wrote:
>>
>>> at the moment, no
>>>
>>> On Feb 12, 2008, at 9:20 AM, David Avendasora wrote:
>>>
>>>> Is there any way to keep Entity Modeler from propagating changes
>>>> in a superclass to it's subclasses? It's frustrating as often as
>>>> it is helpful for me.
>>>>
>>>> Thanks,
>>>>
>>>> Dave
>>>
>>>
>>>
>>>
>>
>
>
>
>
This archive was generated by hypermail 2.0.0 : Tue Feb 12 2008 - 12:29:55 EST