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

Timestamp with time zone

Details

    Description

      Original Description:

      Hi Team,

      Is there any alternative for "timestamp with timezone" columns in mariadb?

      Is it being developed or released anytime soon in future versions?

      Thanks & Regards,
      Manasa Tulluri.

      Implementation details

      TIMESTAMP WITH TIME ZONE should be implemented to support YEARs in the range at least -4713 .. +9999. See MDEV-32496 for details.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. MDEV-29564 please add Time format ISO 8601 to DATE_FORMAT

          • Major - Major loss of function.
          • Open
          duplicates

          Technical task - A technical task. MDEV-20657 sql_mode="oracle" does not support DATE/TIMESTAMP with TIMEZONE

          • Major - Major loss of function.
          • Closed
          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

          Task - A task that needs to be done. MDEV-12514 Split Item_temporal_func::fix_length_and_dec()

          • 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

          Task - A task that needs to be done. MDEV-16881 Remove Item::get_temporal_with_sql_mode() and val_xxx_from_date()

          • Major - Major loss of function.
          • Closed

          Task - A task that needs to be done. MDEV-16939 Move TIMESTAMP truncation code to Field_timestamp::store_TIME_with_warn

          • Major - Major loss of function.
          • Closed
          is part of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-11070 Providing compatibility to other databases - Phase 2

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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range

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

          New Feature - A new feature of the product, which has yet to be developed. MDEV-32496 TIMESTAMP variant to support YEAR range -4713 and +9999

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. MDEV-11829 Please add support for datetime with time zone literals (ISO 8601)

          • 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

          Activity

            Ascending order - Click to sort in descending order
            serg Sergei Golubchik added a comment -

            Yes, there are plans to do it. But at the moment there's nothing final yet.

            serg Sergei Golubchik added a comment - Yes, there are plans to do it. But at the moment there's nothing final yet.
            monty Michael Widenius added a comment -

            We are considering to add this to MariaDB 10.2 or 10.3

            monty Michael Widenius added a comment - We are considering to add this to MariaDB 10.2 or 10.3
            Shelnutt2 Seth Shelnutt added a comment -

            @cvicentiu As discussed at the developer unconference, I would like to contribute and have this issue assigned me to for the 10.4 milestone. Before I start I'll post a general design for review to make sure the approach is agreed upon.

            Shelnutt2 Seth Shelnutt added a comment - @cvicentiu As discussed at the developer unconference, I would like to contribute and have this issue assigned me to for the 10.4 milestone. Before I start I'll post a general design for review to make sure the approach is agreed upon.
            bar Alexander Barkov added a comment - - edited

            It seems TIMESTAMP WITH TIMEZONE will need changes in the client-server library:

            • either extend the existing MYSQL_TIME with a new field for time zone
            • or introduce a new C type for it, e.g. MYSQL_TIME_WITH_TIMEZONE.
            bar Alexander Barkov added a comment - - edited It seems TIMESTAMP WITH TIMEZONE will need changes in the client-server library: either extend the existing MYSQL_TIME with a new field for time zone or introduce a new C type for it, e.g. MYSQL_TIME_WITH_TIMEZONE.

            People

              bar Alexander Barkov
              Manasa ManasaTulluri
              Votes:
              7 Vote for this issue
              Watchers:
              14 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.