flavionegrao / apincrementalstore Goto Github PK

Since Core Data is at the base of this library it would be very convenient if it could be supported?

The way it should be implemented the APParseSyncOperation class would count the number of objects before start syncing to post a NSNotification to the interested consumers that information, then another NSNotification for each object synced. This behaviour allow for showing progress on screen if necessary. However I have just found out that Parse surprisingly limits the number of count requests to 160/minute/app...

EDIT:
To get things even worse it will execute one count operation per Core Data class, so that it turns out to be a serious bottleneck in oder to report the number of objects to be synced in advance.

More of a question than an issue, actually.

I haven't used either stores, but I was just wondering why the community is building two Parse-IncrementalStore implementations when all we really need is just one.

Cheers.

Dear Fellow Stackmob refugee:
I found your repo link in the Parse forums & have a similar situation - except I'm working on Android at the moment & would very much like to have local storage. Have you thought about and/or do you need this capability for Android?
Thanks!

I am having an issue when an object is deleted, either on the Parse Dashboard or on another device, the local copy of that object is not deleted from the local store. Is there a solution for this that I am overlooking?

Also, thank you SO much for this library!

The cached objects have their to-may relationship pointing to the root class of the destination entity of the relation.

Can't find the following file APWebServiceSyncOperation. Any idea ?

thanks

Hi,
It seems Parse SDK 1.6 broke the framework, starting the sync will result with error 'Couldn't create cache key from 16-12-2014 20:09:00'

Tracing the call stack indicates it's crashing when [query hasCachedResult] is called.