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
I just found out my issue is caused by offset parameter being ignored while setting up cache key in cache. Basically first request with offset: 0 is cached. The query.offset is changed in result, but data keep cached for offset: 0.
krystian50
changed the title
Changing limit & offset occurs in upredictable data change
Redis omits query offset parameter in key
May 10, 2020
Describe the bug
I'm querying sorted data. Changing offset seems to be ignored by the query.
To Reproduce
Steps to reproduce the behavior:
{"dimensions":["Refunds.refundNumber"],"limit":10,"offset":0,"order":{"Refunds.refundNumber":"asc"}}
this query returns example data:
{"dimensions":["Refunds.refundNumber"],"limit":10,"offset":10,"order":{"Refunds.refundNumber":"asc"}}
this query returns:
Expected behavior
The query should return data window moved by 10
Screenshots
If applicable, add screenshots to help explain your problem.
Version:
[0.19.16] - server
[0.19.15] - postgres-driver
The text was updated successfully, but these errors were encountered: