You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Relationship cache is currently invalidated by checking between CBLQueryEnumerator.lastSequence and database.lastSequence. As a result, the whole cache will be invalidated even though the changes to the database are not relevant to the cache. One way to improve this is to invalidate cache based on changes notified by the CBLDatabaseChangeNotification. Another way would be checking if the view is changed or not - this needs to call View.updateIndex first and check View.lastSequenceChangedAt to check. Note that View.updateIndex and View.lastSequenceChangedAtare all private.
The text was updated successfully, but these errors were encountered:
- Not using view prefix for relationship views.
- Call view's -updateIndex and check lastSequenceIndexed if the view index was changed or not. If not changed, return the cached result if it's available.
#960
- Not using view prefix for relationship views.
- Call view's -updateIndex and check lastSequenceIndexed if the view index was changed or not. If not changed, return the cached result if it's available.
#960
Relationship cache is currently invalidated by checking between
CBLQueryEnumerator.lastSequence
anddatabase.lastSequence
. As a result, the whole cache will be invalidated even though the changes to the database are not relevant to the cache. One way to improve this is to invalidate cache based on changes notified by theCBLDatabaseChangeNotification
. Another way would be checking if the view is changed or not - this needs to callView.updateIndex
first and checkView.lastSequenceChangedAt
to check. Note thatView.updateIndex
andView.lastSequenceChangedAt
are all private.The text was updated successfully, but these errors were encountered: