[ODBC-83] Min and Max value for time data type is getting processed incorrectly Created: 2017-01-30 Updated: 2017-04-03 Resolved: 2017-04-03 |
|
| Status: | Closed |
| Project: | MariaDB Connector/ODBC |
| Component/s: | None |
| Affects Version/s: | 2.0.13 |
| Fix Version/s: | 2.0.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | kriti suwalka | Assignee: | Lawrin Novitsky |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Windows-64 bit |
||
| Description |
|
Aurora supports -838:59:59 and 838:59:59 as min and max value respectively for time data types, same values are getting read/write as 22:59:59. |
| Comments |
| Comment by Lawrin Novitsky [ 2017-02-23 ] |
|
In ODBC valid values for hours are between 0 and 23 (please look at links in comment to |
| Comment by Lawrin Novitsky [ 2017-04-03 ] |
|
This is not quite a bug, but ODBC constraint. But I fixed support of SQL_INTERVAL_HOUR_TO_SECOND interval type - it allows to deal with time values >23:59:59 (or <-23:59:59). Thus people can deal with those values in their databases, and the bug can be closed with good conscience |