View Revisions: Issue #2437

Summary 0002437: Loading a 'timestamp with time zone' field into a 'timestamp' column appears to mangle the time.
Revision 2015-11-05 19:25 by mmichalek
Description The value in question comes across like this:
2015-11-03 01:35:03.714566 -05:00

There are 2 issues right now surrounding AbstractDatabasePlatform.parseDate:
1) The timezone is attempted to be parsed as a code, not offset.
2) The micro second value of 714566 is interpreted as milliseconds instead of microseconds, and that is what makes the resulting date appear to have a mangled time (714566 is interpreted as an absolute number of milliseconds, so almost 12 minutes is added to the time as it appears).
Revision 2015-11-05 15:34 by mmichalek
Description The value in quesiton comes across like this:
2015-11-03 01:35:03.714566 -05:00

There are 2 issues right now surrounding AbstractDatabasePlatform.parseDate:
1) The timezone is attempted to be parsed as a code, not offest.
2) The micro second value of 714566 is interpreted as milliseconds instead of microseconds, and that is what makes the resluting date appear to have a mangled time.