Re: Another dumb ERRest question
Re: Another dumb ERRest question
- Subject: Re: Another dumb ERRest question
- From: Andrew Kinnie <email@hidden>
- Date: Tue, 29 Mar 2011 07:04:33 -0400
Well, that certainly seemed logical to me (and was my first guess), but I based my code on the example app, which does exactly what I did. Oddly, when I ran the example app, and deleted based on a plist I got the same result I do in mine (except with quotes around it) and if I did the same thing via json, I got a message that there is no object with that id. So apparently the example app does do much useful either.
For now I will return null. We are not going to do much deleting via this interface regardless.
Thanks
On Mar 29, 2011, at 4:15 AM, Farrukh Ijaz wrote:
> Hi Andrew,
>
> I think you shouldn't return a filtered response when you're deleting the object. Your response should indicate your operation was successful or not based on the editingContext().saveChanges() out come.
>
> response(entity, showFilter()) should be used for GET (fetch / select) and optionally in PUT (insert) and POST (update).
>
> Farrukh
_______________________________________________
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