[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)

2009-11-17 Thread Mikkel Kamstrup Erlandsen
Siegfried stated on IRC yesterday that he was in favor of the milliesecond resolution using an INTEGER column (ie. what we have now). I think this means that we have rough consensus..? As for use cases with sub-second resolution think of messaging (IRC, IM). If I continuously say "spam" on IRC I c

[Zeitgeist] [Bug 483603] Re: Use timestamps with milliseconds granularity (was: use REAL)

2009-11-17 Thread Markus Korn
If we really need a millisecond accuracy in timestamps we should go with INTEGER an use int(time.time()*1000) in python code. But on the other hand I don't get why we need this at all. Events which happen at the same time for the user will have a different timestamp, one example is: A user opens

[Zeitgeist] [Bug 483550] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper unittests

2009-11-17 Thread Markus Korn
merged revno: 1299 [merge] committer: Markus Korn branch nick: zeitgeist-resonance timestamp: Tue 2009-11-17 09:11:04 +0100 message: * turned test/remote-test.py over to a proper unittest (LP: #483550)

[Zeitgeist] [Bug 483550] Re: [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper unittests

2009-11-17 Thread Launchpad Bug Tracker
** Branch linked: lp:~zeitgeist/zeitgeist/zeitgeist-resonance -- [lp:~zeitgeist/zeitgeist/zeitgeist-resonance] make test/remote-test.py proper unittests https://bugs.launchpad.net/bugs/483550 You received this bug notification because you are a member of Zeitgeist-Engine, which is the registrant