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
Description
Given that a sql_manipulation class is used within the oracle provider, the count query for "numberMatched" and the actual feature queries might be different queries. This can lead to wrong numberMatched and to wrong queries being executed.
Steps to Reproduce
Steps to reproduce the behavior: sql_manipulator that adds/removes something to the where clause
Expected behavior
Except the limit and offset params the where clauses should be the same for the count and the actual query.
Description
Given that a sql_manipulation class is used within the oracle provider, the count query for "numberMatched" and the actual feature queries might be different queries. This can lead to wrong numberMatched and to wrong queries being executed.
Steps to Reproduce
Steps to reproduce the behavior: sql_manipulator that adds/removes something to the where clause
Expected behavior
Except the limit and offset params the where clauses should be the same for the count and the actual query.
pygeoapi/pygeoapi/provider/oracle.py
Lines 696 to 700 in 3bdeefe
even if this changes the query:
pygeoapi/pygeoapi/provider/oracle.py
Lines 799 to 870 in 3bdeefe
Screenshots/Tracebacks
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Solution proposal is here:
https://github.com/totycro/pygeoapi/blob/e2ba2c79cdcbd1b23601fba9f7f555a8d6644353/pygeoapi/provider/oracle.py#L696-L736
The text was updated successfully, but these errors were encountered: