Memory error in API Live.getLastVisitsDetails when filter_offset is large #7596
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes #7458
Before, when
LIMIT 10 OFFSET 15
was requested we did fetch 25 records from the database to make sure theSort
andLimit
filter in GenericFilter works.Now we do directly in the API apply
filter_limit
andfilter_offset
to fetch only 10 records. This means we do no longer supportSort
for theLive.getLastVisitsDetails
API method. As the method name says we will always sort byvisit_last_action_time
.filter_sort_order
will still work.