This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author scoobydoo
Recipients Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, ethan.furman, goshawk, lemburg,, pitrou, pythonhacker, r.david.murray, scoobydoo, serhiy.storchaka, tim.peters, vstinner
Date 2015-04-08.02:29:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This issue is causing my organization problems. We are using python 2.7.9 with pyodbc 3.0.7
The application DB is SQL Server and they have started using Datetime2 (see:

They did this to ensure that transactions timestamps are more unique, specially when data is bulk uploaded into the DB.

Datetime2 supports to seven places. Our application is now getting timestamps that are truncated to 6 places, making them useless when comparing a timestamp >= to others in the db.

This is a real world issue and we really need a fix. We are not able to migrate at the moment to python 3 due to other constraints.
Any chance someone can take Matthieu's patch and retro fit it to 2.7.9 (if that makes sense)?
Date User Action Args
2015-04-08 02:29:51scoobydoosetrecipients: + scoobydoo, lemburg, tim.peters, belopolsky, pitrou, vstinner, pythonhacker, Arfrever, r.david.murray, andrewclegg, ethan.furman, Ramchandra Apte, serhiy.storchaka, goshawk, Niklas.Claesson,
2015-04-08 02:29:51scoobydoosetmessageid: <>
2015-04-08 02:29:51scoobydoolinkissue15443 messages
2015-04-08 02:29:50scoobydoocreate