OK, Fixed the issue. Had a problem in the design of my model.
One more autosave question, since I used KVO, I see that the save is
getting called after every key press in a UITextField. I know there is the
delay value to help combine the saves. Do I need to worry about the long
term
On May 13, 2014, at 8:33 AM, Todd Freese to...@filmworkers.com wrote:
One more autosave question, since I used KVO, I see that the save is getting
called after every key press in a UITextField. I know there is the delay
value to help combine the saves. Do I need to worry about the long term
Thanks for the tip!
T
--
You received this message because you are subscribed to the Google Groups
Couchbase Mobile group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mobile-couchbase+unsubscr...@googlegroups.com.
To view this discussion on the web visit
On May 12, 2014, at 2:26 PM, Todd Freese to...@filmworkers.com wrote:
I set it in:
- (instancetype)initInDatabase:(CBLDatabase *)database
That's not an initializer implemented by CBLModel, so there's no way it'll get
called for you. The initializer you should override is:
/** Designated
On Mar 18, 2014, at 8:19 AM, Todd Freese to...@filmworkers.com wrote:
All of my CBLModels have autosave = YES. Do I need to worry about making sure
the model object does not get deallocated until the autoSave runs? Or does
autoSave keep a strong reference to the object until the autoSave
