Portable general timestamp format, not 2038-limited

James Harris james.harris.1 at googlemail.com
Sat Jun 23 22:37:14 CEST 2007

On 22 Jun, 23:49, Roger Miller <roger.mil... at nova-sol.com> wrote:
> My rule of thumb in situations like this is "When in doubt store it as
> text".  The one format I am pretty sure we will still be able to deal
> with in 2039.

Interesting. I hadn't thought about using text. It would add to the
storage a bit as each record is otherwise quite short. But this sounds
like a good option and may help - at least while debugging - to see
the raw date and time as digits. I will consider using this, perhaps
as yyyymmddhhmmssttt.

More information about the Python-list mailing list