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

MySQL Bug#13813064 QUERY USING SPATIAL INDEX RETURNS EMPTY RESULT

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: 10.0.9
    • Fix Version/s: 10.0.10
    • Component/s: None
    • Labels:
      None

      Description

      Test result for main.gis-rt-precise in MariaDB differs from MySQL. Please verify if there is a real bug here.

      Result difference attached. Relevant 5.6 revision:
      revno: 4043
      committer: Nirbhay Choubey <nirbhay.choubey@oracle.com>
      branch nick: B13813064-5.6
      timestamp: Tue 2012-07-17 21:55:25 +0530
      message:
      Bug#13813064 QUERY USING SPATIAL INDEX RETURNS
      EMPTY RESULT
      Bug#14096685 WITHIN() YIELDS NO RESULTS WHEN
      SPATIAL INDEX IS USED

      The ST_Contains & Within() functions doesn't
      show correct result when executed with spatial
      index.

      The reason behind this problem is that the spatial
      index for Contains and Within class of functions in
      MyISAM is implemented in opposite order.

      Fixed by adjusting the flag that controls which
      implementation to use and item's rev_functype()
      for Contains & Within functions.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

              Hide
              holyfoot Alexey Botchkov added a comment -

              As far as I can see MariaDB returns the correct result.
              It's the MySQL who should be fixed.

              Show
              holyfoot Alexey Botchkov added a comment - As far as I can see MariaDB returns the correct result. It's the MySQL who should be fixed.

                People

                • Assignee:
                  holyfoot Alexey Botchkov
                  Reporter:
                  svoj Sergey Vojtovich
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 hours
                    2h