On Sat, Oct 9, 2010 at 11:28 AM, Jim Wilcoxson <[email protected]> wrote:
> This may be a bug in 3.7.1, or I may have been taking advantage of a flaw > in > 3.6.18: > > HashBackup uses SQLite to store backup data in a meta data db and file data > archive db. First I open the main database, then attach an archive > database. When the archive gets full, I detach it, create a new archive > db, > and attach that. This all worked fine with 3.6.18. > > With 3.7.1, I get an error on the detach: OperationalError: database arc > is > locked > > The database is not opened in Exclusive mode, and a commit gets executed > before the detach. What may be causing this - just a guess - is that there > are selects open on the main database at the time of the detach, but the > archive database is not referenced. > > Is this a bug in 3.7.1, or a correction to a flaw in 3.6.18? > Without more information about what your application is doing, we cannot reproduce the problem and cannot determine what is going on here. I'm guessing you still have a transaction active on the database you are trying to detach and you just don't realize it. > > Thanks, > Jim > -- > HashBackup: easy onsite and offsite Unix backup > http://sites.google.com/site/hashbackup > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
