Bug #74764 Different results for same query when using "ts" literal in SELECT query
Submitted: 10 Nov 2014 12:48 Modified: 10 Dec 2014 13:48
Reporter: Petr Hanyáš Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: General Severity:S2 (Serious)
Version:5.6.16 OS:Linux (RedHat 6.4)
Assigned to: CPU Architecture:Any
Tags: different results, literal, order by, same query, ts

[10 Nov 2014 12:48] Petr Hanyáš
Description:
We have set of data which is not changed during time.
When running SELECT query with several LEFT OUTER JOINs and ts literal in WHERE clause, MySQL returns unpredictable results.

How to repeat:
Execute this query more than once (it will return different results on same data):
SELECT COUNT(*)
FROM   (((((`tietoprod_16000`.`task` `Task` LEFT OUTER JOIN `tietoprod_16000`.`sys_user_group` `Group` ON `Task`.`u_resolved_by_group`=`Group`.`sys_id`) LEFT OUTER JOIN `tietoprod_16000`.`core_company` `Company` ON `Task`.`company`=`Company`.`sys_id`) LEFT OUTER JOIN `tietoprod_16000`.`cmdb_ci` `AffectedCI` ON `Task`.`cmdb_ci`=`AffectedCI`.`sys_id`) LEFT OUTER JOIN `tietoprod_16000`.`cmdb_ci` `ServiceOffering` ON `Task`.`service_offering`=`ServiceOffering`.`sys_id`) LEFT OUTER JOIN `tietoprod_16000`.`sys_user_group` `HasBreachedGroup` ON `Task`.`u_breached_solving_sla_group`=`HasBreachedGroup`.`sys_id`) LEFT OUTER JOIN `tietoprod_16000`.`core_company` `TopCompany` ON `Company`.`u_top_company`=`TopCompany`.`sys_id`
WHERE  (`Task`.`u_resolved`>={ts '2014-05-30 00:00:00'} AND `Task`.`u_resolved`<{ts '2014-06-01 00:00:00'}) ORDER BY `Task`.`number`;
[10 Nov 2014 13:48] MySQL Verification Team
Thank you for the bug report. Please check with latest release 5.6.21 and if the issue continues provide a test case (dump with data, queries, real and expected result). Thanks.
[11 Dec 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".