> Use transactions, ref: > http://www.sqlite.org/lang_transaction.html > and program proper lock/error handling. The archives of this > mailing list contain several good examples.
Yes, ok, I'll have to work that way... I believe there should also be some time spent on a good design for these locks... like to avoid congestion. But it'll be on my own for that one, shouldn't be difficult and it's not sqlite specific anyway. (However, i you do have a good url to such design, please tell me!) > You can ATTACH a second database (actually several databases > at the same time) to the same process. Then CREATE your > tables and use INSERT INTO .... (SELECT FROM ...) syntax to > populate tables in one database with the contents of another > one. > http://www.sqlite.org/lang_insert.html > > You even can CREATE tables semi-automatically using the > CREATE TABLE .... SELECT ... syntax, but this has the > disadvantage of not creating any indexes. > http://www.sqlite.org/lang_createtable.html I've read on ATTACH and it does seem to help a lot for my project. But if I understand right, if I'm copying data from db1 to db2 and the data is actually a blob... I would have to make my SQL QUERY, then bind the data in db1 to the query and then step through to actually copy it... right? The same method could be used regardless of datatype actually to make something simple. Thanks, Simon _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
