Grounded DB cleared on poor connection.

Nobody has claimed this yet.

I'm currently using GroundDB on tablets that are in various areas of connectivity on a 4G network.

What we are seeing is, if the tablet is offline, and a collection has been cached, everything works great.

If we have a tenuous 4G connection however, that makes a subscription, but the subscription is slow or never finishes, we end up with the DB getting cleared entirely. This means in the period between when the subscription starts, and when it receives 'ready', we have nothing in our collections.

The desired behavior would be for the cached data to be available until the new subscription is entirely ready, and especially for it to not lose all of the data in the event it happens to get a passing connection.

Start by reproducing the offline cached-collection scenario followed by a slow or incomplete subscription on a 4G connection. Trace where the cached database is cleared before the subscription reports ready. Done means cached data remains available during subscription startup and is preserved when the connection drops or the subscription never finishes.

Written by the indexing model from the issue text.