Bug report #17613
Spatial SQL queries are not working (wrong, empty result) in DB Manager for GeoPackage datasources
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||25510|
Affects both 2.18.14 and master.
The same spatial queries are ok for Spatialite datasources.
Also using virtual layers seems to work as expected.
A query like:
SELECT fid, ST_Buffer(geom,100) AS geom
for a GPKG datasource will result in a layer (loaded using the "load as new layer" option) that has the same geometry as the source one (and is empty).
I'm trying to apply some spatial SQL functions like ST_BUFFER in a point layer. The output is correct in the database manager but the representation is incorrect on the canvas.
The output is supposed to be a polygon layer.
#1 Updated by Giovanni Manghi over 3 years ago
- Subject changed from Error SQL spatial functions in DB Manager and GeoPakcage (QGIS v2.99) to Spatial SQL queries are not working DB Manager for GeoPackage datasources
- Crashes QGIS or corrupts data changed from Yes to No
- Operating System deleted (
Arch Linux x64)
- Description updated (diff)