-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
QGIS select by expression mismatch with MSSQL layers #25320
Comments
Author Name: Solution s (Solution s) Additional layer/field information: |
Author Name: Giovanni Manghi (@gioman) Does it happens for other providers (like PostGIS) or datasources? Can you test on a more recent release? Thanks.
|
Author Name: Solution s (Solution s) Works fine on this layer:
I will try as soon as I get my administrator to update QGIS. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Solution s (Solution s) I uninstalled QGIS 2.18.11 and installed 2.18.14. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Nyall Dawson (@nyalldawson) Can you provide a SQL dump of part of this layer?
|
Author Name: Jürgen Fischer (@jef-n) Please test with QGIS 3.4 - QGIS 2.18 reached it's end of life. |
Author Name: Giovanni Manghi (@gioman)
|
Author Name: Solution s (Solution s)
Original Redmine Issue: 17423
Affected QGIS version: 2.18.14
Redmine category:data_provider/mssql
When trying to select features using "select by expression", QGIS did select a wrong feature in this case.
I tried on two different days, same result (so I have restarted the PC and QGIS).
What i did was:
Instead it should have selected line 24 (ID = 8339), because as you can see that have '10ae' as the "matrikelnummer"
Interestingly, the layer filter is able to select/filter the correct features.
What i did to further test expressions was:
Some information about the layer:
** Interestingly nothing is shown in the layer properties window under "Data Source Encoding", and I'm not able to select any option (there is none).
The text was updated successfully, but these errors were encountered: