My suggestion is to have a sqlite_... table in which to start statements to run at DB open time, so as to:
- automatically CREATE temp tables, indexes, views - automatically ATTACH related DBs - automatically load extensions (this should require explicit acquiescence from the API caller though) This would allow the use of the sqlite3 shell with apps fully contained in the DB. This is almost what you want, but not quite. This is better because all it does is initial setup. Application logic would still be restricted to being in the schema, but now that could include temp schema that "persists" -- not entirely an oxymoron. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
