From: Leonardo Sandoval <[email protected]> Disadvantages of WAL journal mode are explained on [1], but the one affecting our case is "All processes using a database must be on the same host computer; WAL does not work over a network filesystem". Changing the Journal mode into DELETE which is the normal behavior for rollback journal.
[YOCTO #8215] [1] https://www.sqlite.org/wal.html Signed-off-by: Leonardo Sandoval <[email protected]> --- bitbake/lib/prserv/db.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bitbake/lib/prserv/db.py b/bitbake/lib/prserv/db.py index 4379580..b3e3a4f 100644 --- a/bitbake/lib/prserv/db.py +++ b/bitbake/lib/prserv/db.py @@ -245,7 +245,7 @@ class PRData(object): self.connection=sqlite3.connect(self.filename, isolation_level="EXCLUSIVE", check_same_thread = False) self.connection.row_factory=sqlite3.Row self.connection.execute("pragma synchronous = off;") - self.connection.execute("PRAGMA journal_mode = WAL;") + self.connection.execute("PRAGMA journal_mode = DELETE;") self._tables={} def __del__(self): -- 1.8.4.5 -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
