On Wed, Apr 11, 2012 at 12:01 PM, Ian Katz <ifreeca...@gmail.com> wrote: > The Sqlite3 manual says that any locking operations affect the entire > database, not individual tables. > http://www.sqlite.org/lockingv3.html > > I was wondering if this effect could be compensated for by splitting > tables into separate databases and using the "attach database" option > outlined here: > http://stackoverflow.com/questions/6671678/objective-c-sqlite-join-tables-from-multiple-database > > I would assume that the databases will not become locked until the > statement is executed (i.e., preparing the statement won't lock it). > Is that correct?
Yes, that's correct, although I don't see a link between this statement and "attache database" discussion above. > If so, is there a significant disadvantage or > performance hit to using this workaround? The first performance hit that comes to mind is either you won't be able to use WAL mode (which is a significant performance hit) or you lose overall atomicity of transactions (see disadvantage point 3 here http://www.sqlite.org/wal.html). So I wouldn't do that if I were you. Pavel _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
