Tag Info

Hot answers tagged

6

Dates increase as time advances, so 1293861600 (Jan. 1st 2011) is greater than 946706400 (Jan 1st. 2000). Thus, a descending ordering puts the most recent dates first. Because sorting by dates is much more common than by name, ordering is descending by default.


4

I don't follow, for date times the most recent date is the largest date. Sample return by events { "event_type": "question_posted", "event_id": 9369546, "creation_date": 1329777738 }, { "event_type": "comment_posted", "event_id": 11832402, "creation_date": 1329777736 } 1329777738 => Mon, 20 Feb 2012 22:42:18 GMT 1329777736 => Mon, 20 Feb 2012 ...


3

This is a classic "procedural" (or "row based" or "sequential") versus "set based" issue. See Understanding “Set based” and “Procedural” approaches in SQL or any one of thousands of similar articles. The API uses SQL to get its results and the idea of requiring an arbitrary order to results is anathema in SQL -- a sign of possible deficiencies in "set ...


3

Yep, sorts weren't being applied to that route. This should be fixed now.


3

This has been fixed.


2

That's a bug. a naked query should return all comments, you should not have to specify min=0 (which is basically a no-op).


2

Looks correct to me.


2

This is historical (and should probably be updated..., hmm). /questions is/was a window onto http://stackoverflow.com/questions ; notice that there sorting is by newest. Accordingly, sorts for /questions were once fixed and didn't support min, max, or order.


2

'hot', 'week', 'month' return questions with high activity and interest within a period of time relative to now. min/max further limit those results. see http://stackapps.com/questions/922 for more detail.


2

This isn't possible and isn't likely to be added. Post history is by a good clip the largest chunk of data in the system. Regularly sorting by it would be prohibitively expensive on the sites themselves, much less in the API. For queries like this, we have data.stackexchange. Here's a query for the most "revised" post on a site. We also provide data dumps ...


1

Use the /questions path and sort by: creation, desc. For example:     /2.1/questions?pagesize=15&order=desc&sort=creation&tagged=php&site=stackoverflow


1

This went out tonight.


1

No, this is not currently available. It is currently not slated for the next API release either... I'll look into what it would take to get it added though. If it's not too rough it might make it into V2. Time was found to implement this, and it's been deployed.


1

Its by design. Default order is descending across the board, this includes lexicographic sorts.


1

I believe the sort=votes parameter is for when you are retrieving multiple questions in one API call, such as with this URL - the questions in the response are ordered by vote. http://api.stackoverflow.com/0.8/questions/1429951;2383701;619895?sort=votes&type=jsontext In terms of how you could sort the responses - you do have the up + the down vote ...


1

Sorts are not guaranteed to be stable. Check the creation_date on each user to convince yourself they are in order.



Only top voted, non community-wiki answers of a minimum length are eligible