Do you have any mandatory to-one relationships to the entity in
question in your model? I think starting in WO 4.5, mandatory to-one
relationships were automatically created. This is the only way I
know of to get a completely empty EO.
Ken
On Mar 21, 2007, at 1:15 AM, Corin Lawson wrote:
Hi List,
I've run into a rather nasty little problem after making some
changes to my app recently. The problem never showed in testing and
is difficult to contrive (which is the nasty bit).
After an arbitrary and large number of requests, an arbitrary and
small proportion of fetches fail. That is to say that some fetches
give an object whose properties are all null.
For example I wish to fetch a Member with username 'x'. I use a
named EOFetchSpecification, specify the qualifier bindings and
fetch my EOs.
I most cases I receive the expected results, but in some the first
Member object in the NSArray has a null username, password, etc.
I think this is a known problem I remember something about a
locking issue. (?)
Please help.
Cheers,
Corin.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/kenlists%
40anderhome.com
