dbTable: Row count and pagination ignores FilteredPost #177

New Issue

2024-09-02T18:01:25+02:00

jost commented

2024-09-02 18:01:25 +02:00

(Migrated from gitlab.uniworx.de)

Using dbtProj = dbtProjFilteredPostId and mkFilterProjectedPost is ignored in the calculation for the number of rows and the number of pages.

Example

The number of rows 7180 and pages 144 reported correspond to the number of pages ignoring all post filtering, but accounts for all DB filtering. In the picture below, the post filter condition results in no matching row:

If there are rows that pass the post filter condition, the count of rows and pages ignores the filtered rows either, i.e. the number is too hight.

Using `dbtProj = dbtProjFilteredPostId` and `mkFilterProjectedPost` is ignored in the calculation for the number of rows and the number of pages. ## Example The number of rows 7180 and pages 144 reported correspond to the number of pages ignoring all post filtering, but accounts for all DB filtering. In the picture below, the post filter condition results in no matching row: ![image](/uploads/b6f8a85c0d87bcc371e106b669870fcc/image.png) If there are rows that pass the post filter condition, the count of rows and pages ignores the filtered rows either, i.e. the number is too hight.

jost commented

2024-09-02 18:01:25 +02:00

(Migrated from gitlab.uniworx.de)

assigned to @savau

This repo is archived. You cannot comment on issues.

No Milestone

No project

No Assignees

1 Participants

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: fraport/fradrive-old#177