clubjudge / hari Goto Github PK

• Key
• String
• Finish Sorted Sets

also, for relation, optionally don't index one direction of the relationship (maybe another way or declaring when it's fully connected or not)

When creating a relation, today we do:

ZADD n1type#n1id:relation:out    n1type#n1id:relation:n2type#n2id
ZADD n2type#n2id:relation:in     n1type#n1id:relation:n2type#n2id

We should also include:

ZADD n1type#n1id:relation:out:n2type    n2id
ZADD n2type#n2id:relation:in:n1type     n1id

So it would be possible queries filtered by a type.

For nodes is alright, but not for a Hari::Serialization object in a list, for example.

Current delete just removes the node, not its relations.

• #count, to return all nodes in relation (9b0a558)
• #nodes_ids + #nodes_ids! (alias n_ids) (bdc0212)
• #nodes + #nodes! + #to_a (9d646cc)
• #relations_ids + #relations_ids! (alias rids, rel_ids) (81dcc7b)
• #limit (09d7d6d)

- [ ] #step

- [ ] #from

- [ ] be able to chain with a relation query and vice versa (out | in) (a level, and so on)

when per_page is 1 and direction is down, doesnt bring the element brought when per_page is 2

In order to fulfil Redis contracts for every key, there are still these commands missing:

• DUMP http://redis.io/commands/dump
• MIGRATE http://redis.io/commands/migrate
• MOVE http://redis.io/commands/move
• OBJECT http://redis.io/commands/object
• RENAME http://redis.io/commands/rename
• RENAMENX http://redis.io/commands/renamenx
• RESTORE http://redis.io/commands/restore
• SCAN http://redis.io/commands/scan

like User.index.clear

User.reindex could remake all indexes.

strings, hashes, lists, sets, sorted sets, and… relations!

It just needs to respond to #id for that and it's fine.

a .node seems a good idea to declare properties and external keys, or hari do … end