Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You can sort by hash keys, without the complexity of Lua scripts, but you will have to duplicate the keys in your Json structure to Redis' hash keys.</p> <p>The below example has the following structure:</p> <p><strong>users</strong> is a set with the user id's in query.</p> <p><strong>user:X</strong> is the Redis hash which contains the duplicated <em>name</em> / <em>surname</em> data.</p> <p><strong>userdata:X</strong> is your original users Json hash.</p> <hr> <pre><code>redis&gt; hmset user:1 name First surname User OK redis&gt; set userdata:1 "{occupation: 'Tester'}" OK redis&gt; hmset user:2 name Last surname Violet OK redis&gt; set userdata:2 "{occupation: 'Bookseller'}" OK redis&gt; hmset user:3 name Middle surname Veredict OK redis&gt; set userdata:3 "{occupation: 'Judge'}" OK redis&gt; hmset user:4 name Ultimate surname Veredict OK redis&gt; set userdata:4 "{occupation: 'Ultimate Judge'}" OK redis&gt; sadd users 1 (integer) 1 redis&gt; sadd users 2 (integer) 1 redis&gt; sadd users 3 (integer) 1 redis&gt; sadd users 4 (integer) 1 redis&gt; sort users by user:*-&gt;surname get user:*-&gt;name get user:*-&gt;surname get userdata:* alpha 1) "First" 2) "User" 3) "{occupation: 'Tester'}" 4) "Middle" 5) "Veredict" 6) "{occupation: 'Judge'}" 7) "Ultimate" 8) "Veredict" 9) "{occupation: 'Ultimate Judge'}" 10) "Last" 11) "Violet" 12) "{occupation: 'Bookseller'}" </code></pre> <h2>Edit</h2> <p>I have overlooked that multiple <code>By</code> only consider the last clause. So you can't sort by more than one key in one command.</p> <p>Also the <code>SORT</code> command used for lexicographic ordering now requires <code>alpha</code> modifier.</p>
    singulars
    1. This table or related slice is empty.
    1. PORedis sorted set by string values
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNiloct
    1. USNiloct
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for you answer, Niloct. If I adopted your solution though, I'd have to add one hash per user, user:*, which is something I'm trying to avoid. If I were to do this I'd also merge the userdata hash with the user:* hashes. I'll run some tests to see the difference in memory usage between using many small hashes of JSON-encoded data (groups of users, in the example) and using one hash per item (one per user, in the example).
      singulars
      1. PO
      1. USidrarig
    2. COWell the difference in memory usage in my case is huge as expected. Meanwhile I figured out that what I'd really like to be able to do is SORT foobar BY weights->* GET table->* but alas it doesn't seem to be possible...
      singulars
      1. PO
      1. USidrarig
    3. CODid you notice that multiple `BY` and `GET` are allowed ? You would have to issue one per field as in the example.
      singulars
      1. PO
      1. USNiloct
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload