Checks related to API limit parameters shall do done at SQL side
Dedicated SQL exception shall be raised in case limits are exceeded. This way we will share logic and implementation to upcoming PostRest implementation.
This related to changes done below:
The following discussions from !10 (merged) should be addressed:
-
@bwrona started a discussion: _LIMIT value should be definitely constrained, let say to 150000. This should cover all pattern test cases like prevent passing really big values to retrieve big data packs. Also type change is not required then.
-
@bwrona started a discussion: Limit related checks shall be added to SQL code and raise exception.
-
@bwrona started a discussion: Limit related checks shall be added to SQL code and raise exception.
-
@bwrona started a discussion: Limit related checks shall be added to SQL code and raise exception.