[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #18938] Wrong nullify in ToMany relationship
From: |
David Ayers |
Subject: |
[bug #18938] Wrong nullify in ToMany relationship |
Date: |
Mon, 05 Feb 2007 22:17:42 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.10) Gecko/20070116 Firefox/1.0.4 (Debian package 1.0.4-2sarge15) |
Update of bug #18938 (project gnustep):
Severity: 4 - Important => 3 - Normal
Assigned to: None => ayers
_______________________________________________________
Follow-up Comment #1:
IIUC, the behavior due to the entity definition may partly undefined as
primary and foreign keys should not be class properties.
http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/Developer/EnterpriseObjects/DevGuide/EOsI2.html#821
Eventhough they name exceptions to this rule, it's my experience that these
exceptions cause issues as you are refering to. I think GDL2 could try to
support primary keys as class attributes, but I don't think the hastle for
foreign keys is managable and a lot less useful. (Primary keys being
generally immuatable cause a lot less house keeping).
Yet when trying to create a test case, I noticed some issues with propagating
the foreign key with addObject:toBothSidesOfRelationshipWithKey: without
calling removeObject:fromBothSidesOfRelationshipWithKey: to clear the
previous relationship, which when fixed, may happen to resolve your issue
also. I just need to find some time to look at it a bit.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18938>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/