'/search' method mindate/maxdate constraints not working?

[Shannon Burns]

I've had a program for a while now that used the /search method to query for tweets that were written between two certain dates, and the mindate/maxdate optional parameters for this method used to work. In the last couple weeks though, I've noticed that the tweets I get in my JSON response are from seemingly random dates and not from the specified date range. Even when I do a basic request in my browser's url bar with the mindate/maxdate specifications, the tweet dates are all over the place. Anyone know what's going on, and how I can get back to specified dates? 

[Vipul Ved Prakash]

Shannon, 

Can you post a query that returns out of range results?  

cheers,

vipul

[Burns, Shannon]

Hi Vipul,

thanks for trying to help, but someone already found my bug a week ago. Thanks for reminding me about this thread though, I'll go update it so that it says the problem is solved. 

--
 
---
You received this message because you are subscribed to a topic in the Google Groups "Otter API to Topsy" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/otterapi/joBe8CTVqyI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to otterapi+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Shannon Burns]

Found the bug, somewhere along the line I changed the parameter name. It should be "mintime/maxtime" rather than mindate and maxdate. Thanks for your help you guys.