Hi list,I'm currently running into all kinds of weird problems while working with Spatialite-databases. For example:
> https://github.com/qgis/QGIS/issues/66329
I haven't even written down yet the issues I'm facing with foreign key constraints and triggers. Because I found already a solution: Don't use the Spatialite provider, but OGR. It will respect foreign key constraints and even load them while adding the layers. It also automatically sets up the autogenerate form with appropriate input fields like "range" for `INTEGER` and "text" for `NUMERIC`/`REAL`.
There are also other problems with the Spatialite data provider, that don't occur when using GDAL/OGR:
> https://github.com/qgis/QGIS/issues/48390Is there a reason QGIS is still carrying the Spatialite provider? Can it be fully replaced with OGR? OGR is coming with Spatialite support ootb anyway, why would QGIS bring two implementations?
Thus, I'd propose to remove the Spatialite provider, since OGR is offering a more mature solution and removing a different implementation with overlapping functionality would reduce the maintenance burden on you developers.
Best regards -- Tobias A Schula Forestry Expert [email protected]
OpenPGP_0x3B6BA2B3E91776FA.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
