Hi,
Ok,from the source: ((realISO && (hh < 10)) ? "0" + hh : hh) I figure
this intended behaviour, and it looks like this:
>>> a = new Date(2006,5,26,7,2,4)
Mon Jun 26 2006 07:02:04 GMT-0700 (PDT)
>>> toISOTimestamp(a)
"2006-06-26 7:02:04"
Now, some parsers of the the not so standard timestring are picky about
the number of digits given in the string. In this case it should be
like this:
>>> toISOTimestamp(a)
"2006-06-26 07:02:04"
Is there a reason for handling it this way?
Oh, at least since it is inteded, the docs should be changed, since
they suggest, that we always get a double digit:
"However, we see junk in SQL and other places that looks like this:
YYYY-MM-DD hh:mm:ss
So, this function returns the latter form, despite its name, unless you
pass true for realISO"
cheers,
tobbi
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"MochiKit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/mochikit
-~----------~----~----~----~------~----~------~--~---
