> On Sep 25, 2015, at 12:16 PM, Brendan Duddridge <[email protected]> wrote: > > What's strange is I did some testing with renaming the document file while it > was open and everything still worked fine as far as database reads and write. > I haven't started syncing things yet though. I figured renaming the document > while it was opened would have generated some sort of database access error, > but it didn't. Strange.
Both ForestDB and SQLite keep the database file open and just issue read/write calls on the file descriptor, for the most part. That works fine even if the file gets moved. The things that I believe will fail, for a ForestDB-based database, are - Compacting a database (this creates a new db file in the directory and eventually replaces the old file with the new one) - Querying or indexing a view whose backing db file wasn’t already open at the time - Reading or creating attachments I’d like to not have these problems, but they might be hard to fix. In particular, ForestDB has file paths baked into its implementation at a pretty deep level. —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/5AAD4CED-7E81-4EEA-B65C-1F39FE33C891%40mooseyard.com. For more options, visit https://groups.google.com/d/optout.
