Weirdly the new check for SqliteConnectionManager::is_valid causes R2D2(Error(None)) when we are using the library with LiteFS. Reverting back to 0.37 stops the error. I haven't been able to solve why this is causing an issue, but can the new check for SqliteConnectionManager::is_valid be feature gated so that users can opt-in to the older behaviour if issues with incompatibility or performance reasons as noted in the initial issue #65
Weirdly the new check for
SqliteConnectionManager::is_validcausesR2D2(Error(None))when we are using the library with LiteFS. Reverting back to 0.37 stops the error. I haven't been able to solve why this is causing an issue, but can the new check forSqliteConnectionManager::is_validbe feature gated so that users can opt-in to the older behaviour if issues with incompatibility or performance reasons as noted in the initial issue #65