On Jul 16, 2010, at 2:05 PM, JT Olds wrote: >> Unsafe. Using the authorizer callback instead to figure out if a >> statement may write the database is a better way: >> >> http://www.sqlite.org/c3ref/c_alter_table.html >> http://www.sqlite.org/c3ref/set_authorizer.html > > Beautiful Dan, thank you. That problem I think has been nailed. > > Any ideas on the shared cache issue? I went and reread the > documentation, and it's still unclear to me as to whether or not the > shared cache feature works across two database handles open to the > same database in non-concurrent sequence.
Within a process using shared-cache mode, all internal state related to a database is discarded when the number of connections to that database drops to zero. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
