Comment 1 for bug 651345

Revision history for this message
Seif Lotfy (seif) wrote : Re: [Bug 651345] [NEW] TimeRange should have values as DateTime internally

I disagree. Lets keep it all the same
python-zeitgeist = libzeitgeist = zeitgeist-sharp

On Wed, Sep 29, 2010 at 7:46 PM, Manish Sinha <email address hidden>wrote:

> Public bug reported:
>
> TimeRange should have values as DateTime internally
>
> Internally TimeRange stores values as Int64 only. It should store as
> DateTime and return Int64 only when needed. Plus when Int64 value is
> assigned, it should convert it to DateTime.
>
> Conversion log is already implemented in ZsUtils
>
> ** Affects: zeitgeist-sharp
> Importance: Undecided
> Status: New
>
> --
> TimeRange should have values as DateTime internally
> https://bugs.launchpad.net/bugs/651345
> You received this bug notification because you are a member of Zeitgeist
> Sharp, which is the registrant for Zeitgeist Sharp.
>
> Status in Zeitgeist Sharp: New
>
> Bug description:
> TimeRange should have values as DateTime internally
>
> Internally TimeRange stores values as Int64 only. It should store as
> DateTime and return Int64 only when needed. Plus when Int64 value is
> assigned, it should convert it to DateTime.
>
> Conversion log is already implemented in ZsUtils
>
>
>

--
This is me doing some advertisement for my blog http://seilo.geekyogre.com