<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>(A little late).</p>
<p>TL;DR: at least for QGIS, is - never multi-user edit
SQLite/SpatiaLite/GeoPackages on network file systems.</p>
<p>SQLite, (and therefore SpatiaLite and GeoPackage) has quite a few
caveats when it comes to multiple users trying to edit it at once.
<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://www2.sqlite.org/howtocorrupt.html">https://www2.sqlite.org/howtocorrupt.html</a></p>
<p>(my bold)<br>
</p>
<p>"SQLite depends on the underlying filesystem to do locking as the
documentation says it will. But some filesystems contain bugs in
their locking logic such that the locks do not always behave as
advertised. <b>This is especially true of network filesystems and
NFS in particular.</b> If SQLite is used on a filesystem where
the locking primitives contain bugs, and if two or more threads or
processes try to access the same database at the same time, then
database corruption might result."<br>
</p>
<p>And there's also:</p>
<p><a class="moz-txt-link-freetext" href="https://www.sqlite.org/whentouse.html">https://www.sqlite.org/whentouse.html</a></p>
<p>Put simply (Note: I'm not an expert): It's fine to edit SQLite
databases if they're not on a network file system with as many
users as you want, or if they are on a network and you can
guarantee only one process is going to write. However if multiple
people/processes want to write to a network file system, you'll
need a piece of middleware to manage the process, otherwise
there's a good chance of corruption as Paul is seeing.</p>
<p>It may also be that QGIS is doing some of the other things on the
"how to corrupt" page too. I imagine it will only get worse if you
use multiple different software packages to edit simultaneously.<br>
</p>
<p>Cheers,</p>
<p>Jonathan<br>
</p>
<div class="moz-cite-prefix">On 2019-09-27 09:50, Tobias Wendorff
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:876DF374-8012-469B-921A-88E978C45FEB@tu-dortmund.de">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Am 27.09.2019 um 10:24 schrieb Andrea Peri <a class="moz-txt-link-rfc2396E" href="mailto:aperi2007@gmail.com"><aperi2007@gmail.com></a>:
Have you tried to use spatialite instead of geopackage. ?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Why not plain SQLite? Nobody needs and uses the spatial functions of Spatialite, they are even not part of bloatware GPKG (sorry, the created db-files are huge without any compression).
The only reason is indexing and this could be forked off GPGK and Spatialite.
To the topic: I think, it‘s always a bad idea to let multiple users work on a single SQLite-based database. It hasn‘t been created for this reason.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
</blockquote>
</body>
</html>