What I note is that the problem is in MySQL, it doesn't support microsecond in version <5.6, in addition SQLAchemist had worked in this problem and seems to be a fix merged in version 0.8.0 (we are currently using 0.7.x).
Some Proposals to fix this issue are:
- Add an extra column to storage microseconds
- Storage in mySQL the DateTime as an string (like SQLite) and then parse it. (I like this more)
What I note is that the problem is in MySQL, it doesn't support microsecond in version <5.6, in addition SQLAchemist had worked in this problem and seems to be a fix merged in version 0.8.0 (we are currently using 0.7.x).
http:// www.sqlalchemy. org/trac/ ticket/ 2534
Some Proposals to fix this issue are:
- Add an extra column to storage microseconds
- Storage in mySQL the DateTime as an string (like SQLite) and then parse it. (I like this more)
Any suggest?