Re: Help: a boolean attribute always saves as null
Re: Help: a boolean attribute always saves as null
- Subject: Re: Help: a boolean attribute always saves as null
- From: Lachlan Deck <email@hidden>
- Date: Mon, 23 Apr 2007 20:14:11 +1000
Hello there,
embarrassing as it is, here's one for the record just in case someone
else assumes (for their own app) that this is not self-inflicted...
but just quietly ;-)
On 21/04/2007, at 12:35 AM, Lachlan Deck wrote:
On 20/04/2007, at 11:55 PM, Daniele Corti wrote:
2007/4/20, Lachlan Deck <email@hidden>:
On 20/04/2007, at 10:43 PM, Daniele Corti wrote:
> 2007/4/20, Lachlan Deck <email@hidden>:
>>
>> Okay, something might have changed with the model plist (with an
>> update from WOLips or something) but I can't see it :-/
Nope. It's not the model - though it certainly had some stuff that
needed cleaning out.
>> The data is being received via soap (and correctly applied to the
>> instance, as I've checked both the incoming and after setting the
>> value doing a valueForKey on the instance - which returns a
Boolean
>> that is *not* null.
That's all well and good but didn't take into account some other code
attempting to take care of legacy soap interfacing that was just
wrongly re-mapping some old keys to new without condition - and this
happened after the data had already been correctly set :-/
with regards,
--
Lachlan Deck
_______________________________________________
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