Hello, just wanted to make sure that this behavior we're seeing is intentional.

If we have a container with an open database and we call sqlite3_bcvfs_poll which pulls in new changes for that open database... Is it correct that the open database will continue to use the old version of the manifest until that database is closed and reopened? I've written a test which seems to confirm this but wanted to double check that was also true from your point of view. Along the same line of thinking, another question I have which I didn't confirm:

Will other unopened databases in that same container use the new version of the manifest if they're opened after the poll, but before the originally open database has been closed?

we were thinking of adding a line to our documentation something like:

* - any open database within the container at the time of calling checkForChanges will not reflect any new changes pulled in, if any, until the database is closed and reopened.

Ah okay, its totally possible that its transaction based. I went straight for closing and reopening, and never tested a new transaction. This is regular mode.

Changed my test to start a new transaction and you're correct. That is enough to see the new data.

Dan,

The question wasn't so much about whether the new data is visible to new transactions, but that an existing transaction will continue to download data from the "old" manifest indefintely.

Keith

Sorry - managed to miss that. Any existing transaction will continue to use the old manifest and may continue to download blocks corresponding to old data until it is finished. Or until it finds one of the blocks it needs has been deleted by a call to sqlite3_bcv_cleanup().

Thanks,

Dan.