Uploaded image for project: 'MariaDB Connector/ODBC'
  1. MariaDB Connector/ODBC
  2. ODBC-83

Min and Max value for time data type is getting processed incorrectly

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 2.0.13
    • 2.0.14
    • None
    • None
    • 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.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          Lawrin Lawrin Novitsky added a comment -

          In ODBC valid values for hours are between 0 and 23 (please look at links in comment to ODBC-82)

          Lawrin Lawrin Novitsky added a comment - In ODBC valid values for hours are between 0 and 23 (please look at links in comment to ODBC-82 )
          Lawrin Lawrin Novitsky added a comment -

          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

          Lawrin Lawrin Novitsky added a comment - 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

          People

            Lawrin Lawrin Novitsky
            kriti kriti suwalka
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.