As of version 2.2, "PRAGME optimize" is run when the database is closed.
This might cause errors because "PRAGMA optimize" requires a read/write connection to the database, whereas the fossil command that triggered the database open would otherwise have been fine in read-only mode. The use case is: $ echo foo > bar.txt $ fossil commit bar.txt -> editor opens to enter a commit message -> ctrl-z, put the editor in the background to review previous commits $ fossil timeline 12:27:16 [245e1ce25c] initial empty check-in (user: gahr tags: trunk) +++ no more data (2) +++ SQLITE_BUSY: statement aborts at 7: [PRAGMA optimize] database is locked The error is innocuous but i) it can cause confusion, and ii) it takes a few seconds to show up. Is there any way "PRAGMA optimize" could be run only when we know the database is open in read-write mode? Thanks, -- Pietro Cerutti g...@gahr.ch
signature.asc
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
