Chuck,
Thanks. It looks like it turned out to be my bug. I "crossed my
streams" (editing contexts).
- Joe
On Apr 15, 2008, at 14:03:30, Chuck Hill wrote:
On Apr 15, 2008, at 1:09 PM, Joe Moreno wrote:
Chuck,
Upon closer examination, I am seeing that if an EO field was null,
then up
On Apr 15, 2008, at 1:09 PM, Joe Moreno wrote:
Chuck,
Upon closer examination, I am seeing that if an EO field was null,
then updated, but not saved, it seems that the unsaved, previously
null value, gets pushed into the snapshot 'cause I see the new,
unsaved value, appear when getting
Chuck,
Upon closer examination, I am seeing that if an EO field was null,
then updated, but not saved, it seems that the unsaved, previously
null value, gets pushed into the snapshot 'cause I see the new,
unsaved value, appear when getting a local instance from a peer EC.
Does th
Chuck,
Yup, Sally is the new, unsaved, value. Somehow, I missed the fact
that localInstance only uses the snapshot values.
Thanks for pointing that out – it's a big help.
- Joe
On Apr 13, 2008, at 20:25:55, Chuck Hill wrote:
Is "Sally" a new (unsaved) value? localInstance uses th
Is "Sally" a new (unsaved) value? localInstance uses the last saved/
fetched values from the snapshot, NOT the values in the EO.
Chuck
On Apr 13, 2008, at 8:18 PM, Joe Moreno wrote:
Hi All,
Eclipse 3.3.2
WOLips 3.3.5047
Mac OS X 10.5.2
WO 5.3.3
Not using WOnder
In the process of moving an
Hi All,
Eclipse 3.3.2
WOLips 3.3.5047
Mac OS X 10.5.2
WO 5.3.3
Not using WOnder
In the process of moving an EO from one EC to another it seems to get
changed.
Am I overlooking something obvious, here?
The following code:
public void setPerson(Person newPerson)
{
NSLog.debug.appendln("1. Fi
