Message182858
Serhiy Storchaka wrote:
> convert_timestamp() can silently return wrong result if seconds
> saved with more than millisecond precision (i.e. '2012-04-04
> 15:06:00.000123456'). I propose or truncate fractional part to 6
> digits ('{:0<6.6}') or explicitly raise an exception if
> len(timepart_full[1]) > 6.
That's a good point. Also, '2012-04-04 15:06:00.1234567' fails with a
ValueError when executing the SELECT statement, because the
microsecond part is not in range 0-999999.
Truncating the fractional part to 6 characters sounds good to me,
because that way we get the best possible precision without failing
abruptly. |
|
Date |
User |
Action |
Args |
2013-02-24 08:33:13 | petri.lehtinen | set | recipients:
+ petri.lehtinen, ghaering, pitrou, frankmillman, python-dev, serhiy.storchaka, thiderman |
2013-02-24 08:33:13 | petri.lehtinen | link | issue14720 messages |
2013-02-24 08:33:12 | petri.lehtinen | create | |
|