[docs] sqlite3 issue/bug

Thomas Michiels mi_thom at hotmail.com
Fri Jun 1 21:43:00 EDT 2018

Dear python developpers,

First of all, I wanna say thanks for the awesome language about which i am still learning new stuff each day.
Secondly, i wanne report a bug, I hope this is right adress. It is a bug in the sqlite3 package (using the 2.7.13 version).
Normally a timestamp (using the datetime converter/adapter*) is saved like:
2018-06-02 01:28:56.4610000+00:00
Now in the very rare case the save happens exactly at a round second, it will be saved like this:
2018-06-02 01:28:56+00:00
Without any miliseconds. The adapter/converter for reading in the values will give an error on this on line 71 of the dbapi2.py file
ValueError: invalid literal for int() with base 10: '56+00'

The chances of this error happening are very small, but with very frequent timestamp updates, that chance becomes bigger.
I hope you can confirm this

*connection made with option: detect_types=sqlite3.PARSE_DECLTYPES

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/docs/attachments/20180602/a9e3a4b8/attachment-0001.html>

More information about the docs mailing list