Hi Doug,
On 2012-06-08, at 9:35 AM, doug andrews wrote: > Most of my entities are of class EOGenericRecord. > I do have a few custom entity classes that extend EOGenericRecord. Either your app is really simple, or you are doing it wrong. :-) > Sometimes, not always, the accessor methods for the "to one" relationships > return null, even though I know the relationship exists. This usually only > occurs when the app has 70 or more sessions running. That sounds more like you are breaking EOF commandments and getting EOF state corruption due to concurrency conflicts. > The code for these custom entities was generated by the old EOModeler app. > They simply return storedValueForKey. That sounds correct. > The foreign key of the relationship is marked as "not null" in the model, but > the relationship is marked as "optional". I know this is probably wrong, but > the old EOModeler app let you get away with this, and i'm sure stuff would > break if i changed it now. > > To get the related entity from an EO that is of type EOGenericRecord, I > simply use valueForKey, and this never seems to return null. Since this > always works, should my accessor methods in my custom entity classes return > valueForKey instead of storedValueForKey? Would that fix my problem? No, that will cause infinite recursion as valueForKey will call your accessor methods which will call valueForKey which will call.... Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
