Caching tables with ED with dotConnect for SalesForce
Posted: Tue 05 Feb 2013 12:14
If a particular table's cache hasn't been updated for some time, or if there has been some form of maintenance that bulk updates a lot of records, this causes an error when accessing the entity (exception is raised saying that the retrieve() limit has been reached).
My guess is that the data replication api is being used under the covers.
The normal way this is done using the SOAP API would be to make multiple queries to the retrieve() function, but it looks like this check is not being done.
The only solution once this happens is to delete the DataCache SQLite database and start caching again.
This is very hard to catch and fix automatically though, and really affects performance.
It would be better if the cache update routine just cycled through in chunks no greater than the hard limit imposed by the provider.
Thanks...
Craig
My guess is that the data replication api is being used under the covers.
The normal way this is done using the SOAP API would be to make multiple queries to the retrieve() function, but it looks like this check is not being done.
The only solution once this happens is to delete the DataCache SQLite database and start caching again.
This is very hard to catch and fix automatically though, and really affects performance.
It would be better if the cache update routine just cycled through in chunks no greater than the hard limit imposed by the provider.
Thanks...
Craig