Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Looks like <a href="http://redis.io/topics/data-types#sets" rel="nofollow"><code>SETS</code></a> is an good idea (<strong>if need location uniqueness</strong>):</p> <ul> <li>UserId as key.</li> <li><a href="http://redis.io/commands/sadd" rel="nofollow"><code>SADD</code></a> for <strong>set location</strong> (require O(N) where N is the number of members to be added) </li> <li><a href="http://redis.io/commands/smembers" rel="nofollow"><code>SMEMBERS</code></a> for <strong>get all locations</strong> feature.</li> <li>Hold long, lat as some delimiter separated string or serialized value (json for example).</li> </ul> <p>PHP sample </p> <pre><code>$location = json_encode(array('long' =&gt; '...', 'lat' =&gt; '...')); $redis-&gt;sAdd('locations:' . $userId, $location); ... $redis-&gt;sAdd('locations:' . $userId, $location2); ... $redis-&gt;sAdd('locations:' . $userId, $location2); ... $userLocations = $redis-&gt;sMembers('locations:' . $userId); </code></pre> <p>You did not say this, but <strong>if do not need uniqueness</strong> of locations the <a href="http://redis.io/topics/data-types#lists" rel="nofollow"><code>LISTS</code></a> would be best choise:</p> <ul> <li><a href="http://redis.io/commands/rpush" rel="nofollow"><code>RPUSH</code></a> for <strong>set location</strong> (require O(1)) </li> <li><a href="http://redis.io/commands/lrange" rel="nofollow">LRANGE</a> for <strong>get all locations</strong> feature. </li> <li>Key and value format like in <a href="http://redis.io/topics/data-types#sets" rel="nofollow"><code>SETS</code></a> case.</li> </ul> <p>PHP sample </p> <pre><code>$location = json_encode(array('long' =&gt; '...', 'lat' =&gt; '...')); $redis-&gt;rPush('locations:' . $userId, $location); ... $redis-&gt;rPush('locations:' . $userId, $location2); ... $redis-&gt;rPush('locations:' . $userId, $location2); ... $userLocations = $redis-&gt;lRange('locations:' . $userId, 0, -1); </code></pre> <p>If user has only one location <a href="http://redis.io/commands#hash" rel="nofollow"><code>HASH</code></a> would be best choise:</p> <ul> <li>One key for all users, for example <code>locations</code></li> <li><a href="http://redis.io/commands/hset" rel="nofollow"><code>HSET</code></a> where field is your userId and value is serialized data</li> </ul> <p>PHP sample </p> <pre><code>$location = json_encode(array('long' =&gt; '...', 'lat' =&gt; '...')); $redis-&gt;hSet('locations', $userId, $location); ... $userLocation = json_decode($redis-&gt;hGet('locations', $userId)); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PORedis store location of users strategy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmisterion
    1. USmisterion
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PORedis store location of users strategy
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    1. COI have many users each has it's own id and long lat. Can I just serialize json object of my user and store it in redis set?
      singulars
      1. PO
      1. USSlow Harry
    2. COHow can I store it as in map, ID => JSON Object?
      singulars
      1. PO
      1. USSlow Harry
    3. COEach user can have just one location or many locations?
      singulars
      1. PO
      1. USmisterion
 

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