Open GoogleCodeExporter opened 8 years ago
I added some changes today that might fix this. I overrode all the KV and KVO
methods in
SQLitePersistentObject, and marked the class as dirty before calling super. Can
you please check to see if this
fixes this problem when you get a chance?
Original comment by jeff.lam...@gmail.com
on 19 Feb 2009 at 1:05
Doesn't seem like the changes have fixed the problem.
Temporary work around is to always save the object if any property is a
collection.
===================================================================
--- SQLitePersistentObject.m (revision 76)
+++ SQLitePersistentObject.m (working copy)
@@ -707,6 +707,9 @@
}
else
{
+ dirty = YES;
+ break;
+
Original comment by amle...@gmail.com
on 19 Feb 2009 at 10:26
another approach I was trying was to subclass the NSMutableArray and have it
hold a reference to the
SQLite object. then intercept calls to objectAtIndex it and update the
reference to be dirty.I've found this
hard to implement because NSArray is a category and can't be subclassed easily.
Original comment by amle...@gmail.com
on 19 Feb 2009 at 9:09
Original issue reported on code.google.com by
amle...@gmail.com
on 5 Feb 2009 at 10:20