Bug report #20336
Updated by Jürgen Fischer over 5 years ago
Hi everyone,
When I load a polygon feature from my Oracle Database into QGIS 3.2.4 & 3.4 (Using Windows 7), the polygon records are filtered in the attribute table.
Please see !/attachments/download/13659/Filtered%20Records%201.JPG! !Filtered Records 1.JPG!
If I search for one of the hidden features using an Advanced Filter, I can find the feature successfully but the attribute table loads a completely different feature with entirely different attributes.
Please see !/attachments/download/13660/Filtered%20Records%202.JPG! !Filtered Records 2.JPG!
Strangely, if I pan / zoom the map view to this 'wrong' record, the map extent goes to the one I originally intended to find.
Please see !/attachments/download/13661/Filtered%20Records%203.JPG! !Filtered Records 3.JPG!
I don't have the same issue if I load the feature as a shapefile or perform the same feature load in the last QGIS LTR (2.18). I tried to research this topic a little bit but could not find a solution to the problem. I'm hoping someone can help. Just an FYI, this is my first time submitting a Bug report so my apologies if I've broken any reporting rules or omitted information.
Thanks,
Andrew
When I load a polygon feature from my Oracle Database into QGIS 3.2.4 & 3.4 (Using Windows 7), the polygon records are filtered in the attribute table.
Please see !/attachments/download/13659/Filtered%20Records%201.JPG! !Filtered Records 1.JPG!
If I search for one of the hidden features using an Advanced Filter, I can find the feature successfully but the attribute table loads a completely different feature with entirely different attributes.
Please see !/attachments/download/13660/Filtered%20Records%202.JPG! !Filtered Records 2.JPG!
Strangely, if I pan / zoom the map view to this 'wrong' record, the map extent goes to the one I originally intended to find.
Please see !/attachments/download/13661/Filtered%20Records%203.JPG! !Filtered Records 3.JPG!
I don't have the same issue if I load the feature as a shapefile or perform the same feature load in the last QGIS LTR (2.18). I tried to research this topic a little bit but could not find a solution to the problem. I'm hoping someone can help. Just an FYI, this is my first time submitting a Bug report so my apologies if I've broken any reporting rules or omitted information.
Thanks,
Andrew