StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20570077
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-13T15:27:36.133
FavoriteCount
0
LastActivityDate
2013-12-13T15:41:11.467
LastEditDate
2013-12-13T15:41:11.467
LastEditorUserId
152016
OwnerUserId
152016
ParentId
20568896
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Well, there are a few things you must clear up about the solution: <h3>1) The kind of data structure you will use</h3> Before dealing with <code>SORT</code>, you must store the data in some Redis structure. You have plenty of options for this case. Redis native data structures are: hashes, lists, sets, sorted sets and simple key/value. You could use lists for this, like: <pre><code>lpush mylist "User Name" username2 username1 UserName username4 username3 </code></pre> Notice that you have to enclose spaces in values with double quotes. You could also use sets, the main difference between sets and lists is that sets only store distinct values (see the example below, in which a duplicated value is stored once): <pre><code>127.0.0.1:6379> sadd sample_set avalue avalue (integer) 1 127.0.0.1:6379> smembers sample_set 1) "avalue" </code></pre> So with sets, you would go like: <pre><code>sadd myset "User Name" username2 username1 UserName username4 username3 </code></pre> <h3>2) SORT lexicographically</h3> You will use <code>SORT</code>, now when you want to sort lexicographically you must use the <code>ALPHA</code> modifier: <pre><code>127.0.0.1:6379> sort mylist alpha 1) "User Name" 2) "UserName" 3) "username1" 4) "username2" 5) "username3" 6) "username4" </code></pre> The sorted order for <code>myset</code> elements is identical. <pre><code>127.0.0.1:6379> sort myset alpha 1) "User Name" 2) "UserName" 3) "username1" 4) "username2" 5) "username3" 6) "username4" </code></pre> So you may have noticed that the order you stated you wanted is not quite equal to the common lexicographic order: space, numbers, uppercase letters, lowercase letters which follows the <a href="http://www.asciitable.com" rel="nofollow">www.asciitable.com</a> order.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORedis: specific sorting results
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNiloct
UserOwnerUserId
1. USNiloct
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. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

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.