Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-11829

Please add support for datetime with time zone literals (ISO 8601)

Details

    • New Feature
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • None

    Description

      This is a feature request requesting to please add support for datetime with time zone literals (ISO 8601).

      A valid value with this format would be:

      2016-12-10T10:10:10-05:00

      As far as I know, we do support part of ISO 8601, which is:

      2016-12-10T10:10:10

      However, we do not support the trailing time zone literal ("-05:00" in this case).

      For reference, this code revision is what mentions the partial support of ISO 8601:

      At least the following formats are recogniced (based on number of digits)
      ...
      YYYYMMDDTHHMMSS where T is a the character T (ISO 8601)

      https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269

      Also, this bug is spawned off of the following bug (which was designated "not a bug", thus I wanted to file a feature request for the future):

      MDEV-11576

      Thank you for your consideration.

      Attachments

        Issue Links

          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-4912 Data type plugin API version 1

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-13995 MAX(timestamp) returns a wrong result near DST change

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-16806 Add Type_handler::create_literal_item()

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-16852 Get rid of Item_temporal_hybrid_func::fix_temporal_type()

          • Major - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18125 JSON_VALUE broken in functions

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-10018 Timestamp with time zone

          • Major - Major loss of function.
          • Open

          Technical task - A technical task. MDEV-10575 sql_mode=ORACLE: Date and timestamp formats

          • Major - Major loss of function.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. MDEV-17448 Support DATETIME(6) for ROW START, ROW END

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          links to

          Web Link PR#290

          Web Link PR#330

          Activity

            Ascending order - Click to sort in descending order
            danblack Daniel Black added a comment -

            ccalender, as indicated the referenced pull request implements the form ...<time>(±hh:mm|Z)

            What isn't implemented is the ISO8601 representations of timezone offsets in these forms

            • ...<time>±hhmm
            • ....<time>±hh

            Are these important to you? Is it worth doing for completeness sake?

            Are the ordinal or week forms of ISO8601 important to you?

            danblack Daniel Black added a comment - ccalender , as indicated the referenced pull request implements the form ...<time>(±hh:mm|Z) What isn't implemented is the ISO8601 representations of timezone offsets in these forms ...<time>±hhmm ....<time>±hh Are these important to you? Is it worth doing for completeness sake? Are the ordinal or week forms of ISO8601 important to you?
            ccalender Chris Calender (Inactive) added a comment - - edited

            Hi Daniel,

            Yes, the following are important (specifically the first one):

            ...<time>±hhmm
            ....<time>±hh

            I think that part would be worth doing.

            ccalender Chris Calender (Inactive) added a comment - - edited Hi Daniel, Yes, the following are important (specifically the first one): ...<time>±hhmm ....<time>±hh I think that part would be worth doing.
            imanov Shahriyar Imanov added a comment -

            5 years....

            imanov Shahriyar Imanov added a comment - 5 years....
            bar Alexander Barkov added a comment -

            Hi Max,

            30 days should be enough.

            bar Alexander Barkov added a comment - Hi Max, 30 days should be enough.
            svoj Sergey Vojtovich added a comment -

            Resetting "contribution" label as there're no active pull requests.

            svoj Sergey Vojtovich added a comment - Resetting "contribution" label as there're no active pull requests.

            People

              bar Alexander Barkov
              ccalender Chris Calender (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              19 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

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