zeitgeist team mailing list archive

[Markus Korn <thekorn@xxxxxx>]

Public bug reported:

For the time_range argument,  there are two ways to query for all events ever inserted in Zeitgeist,
  1.) using TimeRange.until_now(), which translates to (0, int(time.time()*1000))
  2.) (0,0)

Strictly speaking both intervals means sth. completely different, and we should only allow one way here.
I vote for 1.) as this is the most natural way.

As a side note: I *thought* we already decided to not allow (0,0) but I
might be wrong.

** Affects: zeitgeist
     Importance: Undecided
         Status: New

** Description changed:

  For the time_range argument,  there are two ways to query for all events ever inserted in Zeitgeist,
-   1.) using TimeRange.until_now(), which translates to (0, int(time.time()*1000))
-   2.) (0,0)
+   1.) using TimeRange.until_now(), which translates to (0, int(time.time()*1000))
+   2.) (0,0)
  
- Strictly speaking both intervalls means sth. completely different, and we should only allow one way here.
+ Strictly speaking both intervals means sth. completely different, and we should only allow one way here.
  I vote for 1.) as this is the most natural way.
+ 
+ As a side note: I *thought* we already decided to not allow (0,0) but I
+ might be wrong.

-- 
(0,0) vs. Timerange.until_now() in methods to find events to get all events ever inserted
https://bugs.launchpad.net/bugs/490242
You received this bug notification because you are a member of
Zeitgeist-Engine, which is the registrant for Zeitgeist Framework.

Status in Zeitgeist Framework: New

Bug description:
For the time_range argument,  there are two ways to query for all events ever inserted in Zeitgeist,
  1.) using TimeRange.until_now(), which translates to (0, int(time.time()*1000))
  2.) (0,0)

Strictly speaking both intervals means sth. completely different, and we should only allow one way here.
I vote for 1.) as this is the most natural way.

As a side note: I *thought* we already decided to not allow (0,0) but I might be wrong.