Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SensorThings] Unexpected behaviour for rows deletion in expand table #59532

Open
1 of 2 tasks
lucagiovannini opened this issue Nov 20, 2024 · 0 comments
Open
1 of 2 tasks
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@lucagiovannini
Copy link

What is the bug or the crash?

SensorThings data provider should not allow to delete rows in expand table for the rows that have further active rows below.

Steps to reproduce the issue

Select Entity type = Locations
Expand to Things, Datastreams, Observations
Delete row Things.

This is currently possible though unexpected and wrong: an expansion from Locations directly to Datastreams can not exist.

image

Versions

QGIS version
3.38.2-Grenoble
QGIS code revision
130c432
Qt version
5.15.13
Python version
3.12.5
GDAL/OGR version
3.9.2
PROJ version
9.4.0
EPSG Registry database version
v11.004 (2024-02-24)
GEOS version
3.12.2-CAPI-1.18.2
SQLite version
3.45.1
PDAL version
2.6.3
PostgreSQL client version
16.2
SpatiaLite version
5.1.0
QWT version
6.2.0
QScintilla2 version
2.14.1
OS version
Windows 10 Version 2009

Active Python plugins
profiletool
4.1.8
QuickOSM
1.16.0
quick_map_services
0.19.26
SensorThingsAPI
1.1.12
SensorThingsAPI_2
1.0.1
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

Additional context

No response

@lucagiovannini lucagiovannini added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant