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
I was thinking about the meta header in each collection, and for each update the api push a new meta header with the revision (i think it´s for any replication or sync feature):
aside from changes api and ttl cache functionality, I don't think it's needed internally it would just take time to add options and update the various code paths.
another option might be similar to #557, which is to just to either call javascript array.map() on the results or for us to add a map or projection function to do similar functionality. This would add overhead (be a bit slower) depending on how large your resultset is.
Hello Guys,
I was thinking about the meta header in each collection, and for each update the api push a new meta header with the revision (i think it´s for any replication or sync feature):
{ "id": "zeoliveirajunior@gmail.com", "meta": { "revision": 0, "created": 1492782478178, "version": 0 }, "$loki": 1 },
Well, in my application i have my own sync mechanism and i do a lot of update operation, so maybe my database could quickly become huge.
Is there any way to disable this?
Thank in advance, sorry for my english.
The text was updated successfully, but these errors were encountered: