As a result, I implemented a feature sooner than I had thought I'd get to it. Persistent objects now use KVO to determine when objects change, and when they change, the object is marked as "dirty". Only dirty objects get saved - if you call "save" on an object that's not dirty, it will result in a no-op. This should be a performance gain even for people who don't need the ability to let objects refer to each other.
SQLitePersistentObjects Update
As a result, I implemented a feature sooner than I had thought I'd get to it. Persistent objects now use KVO to determine when objects change, and when they change, the object is marked as "dirty". Only dirty objects get saved - if you call "save" on an object that's not dirty, it will result in a no-op. This should be a performance gain even for people who don't need the ability to let objects refer to each other.
Subscribe to:
Post Comments (Atom)












0 komentar:
Post a Comment