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

Support for periods operations

Details

    Description

      The spec should look like:

      period_expr ::= <period> <op> <period>
      		 
      period      ::= PERIOD(<datetime>, <datetime>) | <period_name>
      		 
      period_name ::= <ident>|<table_name>.<ident>
      		 
      op          ::= CONTAINS|OVERLAPS|EQUALS|PRECEDES|SUCCEEDS
      		 
                      |IMMEDIATELY PRECEDES|IMMEDIATELY SUCCEEDS

      Attachments

        Issue Links

          is duplicated by

          Task - A task that needs to be done. MDEV-28383 Implement SQL:2011 WHERE predicates for application-versioned tables (CONTAINS, OVERLAPS, etc.)

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

          Task - A task that needs to be done. MDEV-16972 Application-time periods support (phase 1)

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

          Task - A task that needs to be done. MDEV-18928 Application-time periods support (phase 2)

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

          Activity

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

            this certainly makes sense as an feature, it's in the standard, and it's reasonably easy to do. But I'm not sure it's a subtask of application-period tables, looks more like an independent feature to me.

            serg Sergei Golubchik added a comment - this certainly makes sense as an feature, it's in the standard, and it's reasonably easy to do. But I'm not sure it's a subtask of application-period tables, looks more like an independent feature to me.
            nikitamalyavin Nikita Malyavin added a comment - - edited

            to see also 4.14 Periods, 8.20 <period predicate>

            nikitamalyavin Nikita Malyavin added a comment - - edited to see also 4.14 Periods , 8.20 <period predicate>
            f_razzoli Federico Razzoli added a comment -

            This comment could come too late to be even considered, but...
            Wouldn't it be better to add range types, indexes and generic syntax to handle them, like PostgreSQL? (not necessarily compatible syntax, as pg syntax is a bit questionable)

            https://www.postgresql.org/docs/12/rangetypes.html

            f_razzoli Federico Razzoli added a comment - This comment could come too late to be even considered, but... Wouldn't it be better to add range types, indexes and generic syntax to handle them, like PostgreSQL? (not necessarily compatible syntax, as pg syntax is a bit questionable) https://www.postgresql.org/docs/12/rangetypes.html
            serg Sergei Golubchik added a comment -

            yes, it would be better. Periods are just coming together with SQL standard temporal features — system-versioned and application time period tables. On itself, standalone, they aren't a particularly useful feature.

            serg Sergei Golubchik added a comment - yes, it would be better. Periods are just coming together with SQL standard temporal features — system-versioned and application time period tables. On itself, standalone, they aren't a particularly useful feature.

            People

              nikitamalyavin Nikita Malyavin
              nikitamalyavin Nikita Malyavin
              Votes:
              2 Vote for this issue
              Watchers:
              9 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.