Temporal fields needs better conversions
Bug #509066 reported by
Geert JM Vanderkelen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MySQL Connector/Python |
Fix Released
|
High
|
Geert JM Vanderkelen | ||
Bug Description
DATE/DATETIME, TIME and TIMESTAMP need better conversions as strftime() is not good enough to go from Python to MySQL data types. Also TIME calculation still seems to be off..
Related branches
Revision history for this message
| Geert JM Vanderkelen (geertjmvdk) wrote | #1 |
| Changed in myconnpy: | |
| status: | Confirmed → Fix Committed |
| Changed in myconnpy: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
revno: 181
committer: Geert Vanderkelen <email address hidden>
branch nick: myconnpy-Alchemy
timestamp: Tue 2010-01-19 07:15:25 +0100
message:
Fixing Python to MySQL DATE/DATETIME conversions and throwing exceptions
* DATE/DATETIME conversions don't use strftime so MySQL ranges are respected.
* Methods should return or throw an exception; few change to that.
* No need for test case for bug as it will be part of newer tests cases.