> I will try to understand the problem better and maybe in the future I > will open an issue.
I googled FileGDB as I don't know much about it, and came across this info: > The driver implements transactions at the database level, through an > emulation. This works by backing up the current state of the modified > parts of a geodatabase after StartTransaction(force=TRUE) is called. > If the transaction is committed, the backup copy is destroyed. If the > transaction is rolled back, the backup copy is restored. > > Note that this emulation has an unspecified behavior in case of > concurrent updates (with different connections in the same or another > process). This means that if you have more than one connection to the same file (e.g. perhaps two layers coming from the same file, or have it open in QGIS and another program at the same time), there is a risk of the file being corrupted upon write. It sounds like this data format might be one to avoid for datasets you want to modify with QGIS. Cheers, Adam. _______________________________________________ QGIS-User mailing list QGIS-User@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-user Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user