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

Oracle mode: EXTRACT() / XMLTYPE.extract() (phase 3 of MDEV-20658)

    XMLWordPrintable

Details

    Description

      Phase 3 of the split of MDEV-20658 (parent). Implement EXTRACT() / XMLTYPE.extract() in sql_mode=oracle. This is needed for the reporter's example (rtrim(xmlagg(xmlelement(...)).extract('//text()'), ',')). Estimate 12d.
      Dependency: the extract method is in the scope of MDEV-38690 (XMLTYPE methods step 2, in progress), not MDEV-38691 as previously stated. Gated on MDEV-38690.
      Open question: SYS_XMLAGG (raised by Sergei Golubchik, 2025-07-11) scope to be defined here or in phase 2.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. MDEV-38690 XMLTYPE: methods - step 2

          • Critical - Crashes, loss of data, severe memory leak.
          • In Progress
          split to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. MDEV-20658 sql_mode=oracle does not support XMLAGG(), XMLELEMENT() and EXTRACT() XML functions

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

          Activity

            People

              holyfoot Alexey Botchkov
              julien.fritsch Julien Fritsch
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:

                Time Tracking

                  Estimated:
                  Original Estimate - 12d
                  12d
                  Remaining:
                  Remaining Estimate - 12d
                  12d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified

                  Git Integration

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