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
Cursors would be preferable for offset/pages, especially for live data. However, need a way to distinguish between distinct events/cache partial results in memory.
Thinking about this further, the most obvious way to do this is to force the user to specify an attribute/dict key which acts as the hash.
Would have to split the code in the route generator to use the limit/act as a cursor, based on the presence of the hash/index GET arg, which seems feasible.
Hash the last item and return that as the cursor; if the user supplies the cursor consume the generator till you hit that value
Cursors would be preferable for offset/pages, especially for live data. However, need a way to distinguish between distinct events/cache partial results in memory.
See discussion here karlicoss/HPI#16 (comment)
The text was updated successfully, but these errors were encountered: