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

lead and lag don't support defaults

    XMLWordPrintable

Details

    Description

      ColumnStore and other database vendor implementations support a default parameter for the lead and lag window functions. The standard syntax is:
      LAG (value_expression [,offset] [,default])
      LEAD (value_expression [,offset] [,default])

      where the optional default is the value returned should the offset be outside of the window frame. If unspecified then NULL is used.

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. MCOL-646 MariaDB 10.2 WF Add the default option to LEAD/LAG

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • 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-12987 complete window function support for columnstore parity

          • Major - Major loss of function.
          • Open

          Task - A task that needs to be done. MDEV-28906 MySQL 8.0 desired compatibility

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

          Bug - A problem which impairs or prevents the functions of the product. MDEV-39358 MariaDB Rejects NULL Literal as Default Argument in LAG Window Function

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

          Activity

            People

              Unassigned Unassigned
              dthompson David Thompson (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              8 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.