You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering a virtual layer based on a PostgreSQL layer (with SELECT * FROM pglyr), when you try to select an entity in that virtual layer, by picking in the canvas, another entity is selected (wrong entity selected).
Steps to reproduce the issue
See the vidéo attached.
The PG layer I used contains 89305 entities.
241011-PbQGIS-PGVirtualLayer.mp4
Versions
Version de QGIS
3.34.10-Prizren
Révision du code 113de9e
Version de Qt
5.15.13
Version de Python
3.12.5
Version de GDAL/OGR
3.9.2
Version de Proj
9.4.0
Version de la base de données du registre EPSG
v11.004 (2024-02-24)
Version de GEOS
3.12.2-CAPI-1.18.2
Version de SQLite
3.45.1
Version de PDAL
2.6.3
Version du client PostgreSQL
16.2
Version de SpatiaLite
5.1.0
Version de QWT
6.2.0
Version de QScintilla2
2.14.1
Version de l'OS
Windows 10 Version 2009
What is the bug or the crash?
Considering a virtual layer based on a PostgreSQL layer (with SELECT * FROM pglyr), when you try to select an entity in that virtual layer, by picking in the canvas, another entity is selected (wrong entity selected).
Steps to reproduce the issue
See the vidéo attached.
The PG layer I used contains 89305 entities.
241011-PbQGIS-PGVirtualLayer.mp4
Versions
Version de QGIS
3.34.10-Prizren
Révision du code
113de9e
Version de Qt
5.15.13
Version de Python
3.12.5
Version de GDAL/OGR
3.9.2
Version de Proj
9.4.0
Version de la base de données du registre EPSG
v11.004 (2024-02-24)
Version de GEOS
3.12.2-CAPI-1.18.2
Version de SQLite
3.45.1
Version de PDAL
2.6.3
Version du client PostgreSQL
16.2
Version de SpatiaLite
5.1.0
Version de QWT
6.2.0
Version de QScintilla2
2.14.1
Version de l'OS
Windows 10 Version 2009
Extensions Python actives
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: