[MDEV-5877] MySQL Bug#13813064 QUERY USING SPATIAL INDEX RETURNS EMPTY RESULT Created: 2014-03-17  Updated: 2014-03-20  Resolved: 2014-03-20

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 10.0.9
Fix Version/s: 10.0.10

Type: Bug Priority: Major
Reporter: Sergey Vojtovich Assignee: Alexey Botchkov
Resolution: Not a Bug Votes: 0
Labels: None

Attachments: Text File bug13813064.patch    
Issue Links:
PartOf
is part of MDEV-4784 merge test cases from 5.6 Stalled

 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.



 Comments   
Comment by Alexey Botchkov [ 2014-03-20 ]

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

Generated at Thu Feb 08 07:07:43 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.