Pavel, > > 1) How "expensive" is a call to sqlite3_open. Does a call to > sqlite3_enable_shared_cache make it "cheaper"? > >Its cost depends on the size of your schema as it gets parsed during >open.
Isn't this contradictory with an answer by Igor made in a recent thread? >Subject: Re: [sqlite] sqlite3_open on non-DB files / corrupt DBs > > >Nick Shaw <nick.s...@citysync.co.uk> wrote: > > Is there a reason that sqlite3_open() will happily "open" a non-sqlite > > file, returning SQLITE_OK, instead of returning SQLITE_NOTADB, which > > would seem a more obvious return value? > >SQLite doesn't actually touch the file until the first "substantive" >statement is executed on the connection. This allows one to set >various PRAGMAs that can only be set before the database is created. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
