Re: Re : Re : Re : EOGeneralAdaptorException : deleteRowDescribedByQualifierEntity
Re: Re : Re : Re : EOGeneralAdaptorException : deleteRowDescribedByQualifierEntity
- Subject: Re: Re : Re : Re : EOGeneralAdaptorException : deleteRowDescribedByQualifierEntity
- From: Chuck Hill <email@hidden>
- Date: Mon, 21 Mar 2005 20:26:51 -0800
That is just the (buggy) way that prototypes work. You want to set
them _first_ and then customize them. Otherwise the happily, and
silently, erase the prior settings.
Chuck
On Mar 21, 2005, at 8:23 PM, Marc-Alexis Côté wrote:
Ugh...
...
You nailed it right on the head. I know what to look for now and
noticed
this problem in other parts of my model.
I don't understand how this could have crept in there...
After playing around with the EOModeler, I just noticed that when I
change
the prototype, it changes the column name. I suppose I should have a
prototype for fid that has an empty column name?
Thanks to everyone who helped me find the problem; I learned a lot in
the
process!
Marc-Alexis
Le 21/03/05 22:36, « Christian Pekeler » <email@hidden> a
écrit :
----->Dealer.plist:
{name = administrativeAddressFid; prototypeName = id; },
{name = entityId; prototypeName = id; },
{name = shippingAddressFid; prototypeName = id; },
Here's a problem: your primary key and two foreign keys are all
pointing to the same column as specified by your prototype "id." You
need to give them unique column names.
Christian
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden