StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POSQL sort by count with condition, show history
primarykey
Id
17238858
data
AcceptedAnswerId
17239483
AnswerCount
3
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-06-21T15:22:04.340
FavoriteCount
0
LastActivityDate
2013-06-21T17:32:23.360
LastEditDate
2013-06-21T15:54:43.737
LastEditorUserId
261638
OwnerUserId
261638
ParentId
0
PostTypeId
1
Score
1
ViewCount
166
LastEditorDisplayName
text
Body
Consider the following simple MySQL query: <pre><code>SELECT date, count(*) cnt, ip FROM fwlog GROUP BY ip, date HAVING cnt>100 ORDER BY date DESC, cnt DESC </code></pre> It gives me something like: <pre><code>date cnt src 2013-06-20 14441 172.16.a 2013-06-20 8887 172.16.b .... 2013-06-19 14606 172.16.b 2013-06-19 12455 172.16.a 2013-06-19 5205 172.16.c </code></pre> That is, it's sorting the IPs by date, then by count, as directed. Now I would like the result to be: <ul> <li>Show the IP with the highest count TODAY first,</li> <li>then show the counts for that IP for the last few days (independent of cnt),</li> <li>then show the IP with the second hightest count TODAY,</li> <li>then the history of that IP,</li> <li>etc.pp.</li> </ul> Example of desired result: <pre><code>date cnt src 2013-06-20 14441 172.16.a 2013-06-19 12455 172.16.a 2013-06-18 .... 172.16.a 2013-06-17 .... 172.16.a .... 2013-06-20 8887 172.16.b 2013-06-19 14606 172.16.b 2013-06-18 .... 172.16.b 2013-06-17 .... 172.16.b ... 2013-06-20 .... 172.16.c 2013-06-19 .... 172.16.c 2013-06-18 .... 172.16.c 2013-06-17 .... 172.16.c ... ... </code></pre> Can this even be done using plain SQL? Bye, Marki ========================================== @ Gordon Linoff: <pre><code>SELECT datex, cnt, ip FROM fwlog WHERE ... GROUP BY ip , datex ORDER BY SUM(case when datex = DATE(NOW()) then 1 else 0 end) DESC , src, date DESC, cnt DESC 2013-06-20 47 10.11.y 2013-06-19 47 10.11.y 2013-06-18 45 10.11.y 2013-06-17 42 10.11.y 2013-06-16 14 10.11.y .... 2013-06-20 592 172.16.a 2013-06-19 910 172.16.a 2013-06-18 594 172.16.a 2013-06-17 586 172.16.a 2013-06-20 299 172.16.b </code></pre> This is not quite right yet, the lower block should be at the top.
Tags
<mysql><sql>
Title
SQL sort by count with condition, show history
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMarki
UserOwnerUserId
1. USMarki
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POSQL sort by count with condition, show history
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.