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

Hybrid functions and UNION do not preserve spatial REF_SYSTEM_ID

    XMLWordPrintable

Details

    • Bug
    • Status: Confirmed (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.2(EOL), 10.3(EOL), 10.4(EOL)
    • 10.5, 10.6, 10.11, 11.4
    • Data types, GIS
    • None

    Description

      DROP TABLE IF EXISTS t1;
      CREATE TABLE t1 (g GEOMETRY REF_SYSTEM_ID=101);
      DROP TABLE IF EXISTS t2;
      CREATE TABLE t2 AS SELECT g AS g_column, COALESCE(g) AS g_coalesce FROM t1;
      DROP TABLE IF EXISTS t3;
      CREATE TABLE t3 AS SELECT g AS g_union FROM t1 UNION SELECT g FROM t1;
      SELECT G_TABLE_NAME, G_GEOMETRY_COLUMN, SRID FROM INFORMATION_SCHEMA.GEOMETRY_COLUMNS;

      returns

      +--------------+-------------------+------+
      | G_TABLE_NAME | G_GEOMETRY_COLUMN | SRID |
      +--------------+-------------------+------+
      | t1           | g                 |  101 |
      | t2           | g_column          |  101 |
      | t2           | g_coalesce        |    0 |
      | t3           | g_union           |    0 |
      +--------------+-------------------+------+

      Notice, g_column preserved the original REF_SYSTEM_ID, which is correct.
      More complex cases (e.g. g_coalesce and g_union) did not, as they should.

      Attachments

        Issue Links

          Activity

            People

              bar Alexander Barkov
              bar Alexander Barkov
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.