Hello all, I think this is a simple question...
I am using the C api to open and read/write a SQLite database (ie. sqlite3_open_v2() etc.). I would like to have a function in my program to backup the database file (using the OSes copy command). I can guarentee that my program will not write to the database. Do I need to sync or lock the database file before I do the copy command? I believe that as long as I have no open write transactions the file should be fine to copy, is this correct? Is there a way to guarentee there are no open write transactions (I can guarentee there aren't any open transactions by going through my code, but I was just wondering if there is a way for SQLite to tell this as well)? Thanks for any thoughts. Josh _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
