advanced API, has_more: false

Ask Question

Asked 7 years, 4 months ago

Modified 7 years, 4 months ago

Viewed 95 times

I get some results (not important what) and at the end "has_more": false. -> This is unexpected behavior as I know there are more data.

If I modify the request by changing page parameter to 2, I get the second page of results and has_more is suddenly true. -> Correct

In other words, all requests except the first one return expected data.

I think it has something to do with todate parameter. If I remove it, it all works fine beginning with the first request (page).

Do you agree it's a bug or have I overlooked something?

asked Nov 30, 2016 at 18:26

rocky

1413 bronze badges

If you switch the order to asc it also works ...
– rene
Nov 30, 2016 at 18:39
Yup, but that's not what I need :)
– rocky
Nov 30, 2016 at 18:42
1

Make sure your todate is on the midnight of the next day. stackapps.com/a/6172/18722
– rene
Nov 30, 2016 at 18:45
Your query is also giving questions created after the todate (which is really a unix date+time). There are related unresolved bugs, IIRC.
– Awesome Poodles
Nov 30, 2016 at 18:47
@rene Thanks but I need the today field to be set to this exact value.
– rocky
Nov 30, 2016 at 18:51
@AwesomePoodles Thx, perhaps I could use min, max parameters in combination whit sort=creation.
– rocky
Nov 30, 2016 at 18:52
@rene, at least doing that "fixes" the has_more bug. Other bug is masked by the datetime chosen.
– Awesome Poodles
Nov 30, 2016 at 18:53
Rocky, yes setting max to the same as todate does seem to work around the wrong results bug. Alas, the has_more bug remains.
– Awesome Poodles
Nov 30, 2016 at 18:57
Yeah, I see that now :(
– rocky
Nov 30, 2016 at 18:57
Funny thing, if you change sort to activity it seems to work fine...
– rocky
Nov 30, 2016 at 18:59

Add a comment |

0