One page of daily history, as the server described it.
from/to are the park-local days this page actually covered, which is not
the range you asked for: a park call is capped, so a 50-day request comes
back as 31 days plus a next. next is the URL of the following page, or
null on the last one.
This exists for resumable downloads. A checkpoint taken from the ROWS is
wrong in both directions: the newest row's date can be earlier than the page
covered, since an entity that stopped reporting has no rows for the tail
days, so resuming there re-fetches days already written; and there is no way
to tell a complete page from one interrupted mid-write. The page boundary is
the server's own answer to "where do I carry on", so it is the only safe
checkpoint.
One page of daily history, as the server described it.
from/toare the park-local days this page actually covered, which is not the range you asked for: a park call is capped, so a 50-day request comes back as 31 days plus anext.nextis the URL of the following page, or null on the last one.This exists for resumable downloads. A checkpoint taken from the ROWS is wrong in both directions: the newest row's date can be earlier than the page covered, since an entity that stopped reporting has no rows for the tail days, so resuming there re-fetches days already written; and there is no way to tell a complete page from one interrupted mid-write. The page boundary is the server's own answer to "where do I carry on", so it is the only safe checkpoint.