What should be the expected behavior of existing connections when sqlite3_enable_shared_cache() is enabled, and then another database is ATTACH'ed to the pre-cache-enabled connection?
And further complicate things by saying that the attached database is using vtables and the original connection is not. What I'm wondering is . could we enhance sqlite3_open_v2() to add a flag for shared cache enabled, rather than have it be a global setting? I'd like to have some connections on a shared cache, and some not . and be able to attach non-cache-enabled databases to existing connections and have fts3 work. Robert _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
