Better recording of queries #37

tracend · 2013-06-12T02:36:43Z

A history of queries wasn't required till now and in fact the results of each query was just the update in the data.

Now with issues like #36 we'll need to keep a record of each query so it can be tracked down at a later time.

tracend added a commit that referenced this issue Jun 12, 2013

#37 query keys simplified, containing more info

c27f185

tracend added a commit that referenced this issue Jun 14, 2013

#37 new method queries() to set and get a query

778605e

tracend added a commit that referenced this issue Jun 14, 2013

#37 queries() supporting arrays

173d469

tracend added a commit that referenced this issue Jun 14, 2013

#37 queries are allowed to pass their own ids

f7e954b

tracend added a commit that referenced this issue Jun 14, 2013

#37 remove now supports queries

f1d8b28

tracend added a commit that referenced this issue Jun 15, 2013

#37 selectively adding attributes to new queries

e841e60

tracend added a commit that referenced this issue Jun 15, 2013

#37 new internal method _queryId to enhance the lookup of new ids

57a7caf

tracend added a commit that referenced this issue Jul 8, 2013

#37 not including filtering queries in amount()

a786bba

tracend mentioned this issue Jul 8, 2013

Removing query should also remove queries #42

Closed

tracend added a commit that referenced this issue Jul 19, 2013

#37 restoring existing queries

d41e4f2

Provide feedback