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

2009-11-27 Thread Siegfried Gevatter
I've just fixed recent.py (we don't have information about the millisecond so we just use seconds*1000), but I'm not sure it's getting inserted correctly. ** Changed in: zeitgeist Importance: Undecided = Critical ** Changed in: zeitgeist Milestone: None = 0.3.0 -- Use timestamps with

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

2009-11-23 Thread Mikkel Kamstrup Erlandsen
Yes. Plugins *must* send the timestamps in millis since the Epoch. If apps only use second granularity then we will have three zeroes in the end of the timestamps. -- Use timestamps with milliseconds granularity (was: use REAL) https://bugs.launchpad.net/bugs/483603 You received this bug

[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