Hi Pavel,
I can't answer this question. Maybe it's something like all operations
are successful but memory mapping is not actually shared between
processes. So every process sees its own copy and assumes that no
other process works with database, thus database can be corrupted in
many possible ways
Probably something like this.
In fact it did bite me but without too much consequence. Back in 2008
(before WAL birth) I parametrized the "root" of my data files tree so
that all files in the tree are relative to this root where the DB lies,
and all individual file relative paths are stored in a Paths table in
the DB itself. To make things more flexible I specified the root as an
UNC path, so I could move the whole tree around without change,
provided the target machine has the required netname.
Changing \\machine\dbPath\ to D:\dbPath\ fixed it.
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
