List:General Discussion« Previous MessageNext Message »
From:Russ Lavoie Date:December 27 2013 6:47pm
Subject:RE: MySQL Descending ORDER issue
View as plain text  
Sure thing!








table_foo | CREATE TABLE `table_foo` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `credential_id` int(10) unsigned NOT NULL,
  `status_id` bigint(20) unsigned NOT NULL,
  `date` int(10) unsigned NOT NULL,
  `in_reply_to` bigint(20) unsigned NOT NULL,
  `column1_foo` bigint(20) unsigned NOT NULL,
  `user_id` bigint(20) unsigned NOT NULL DEFAULT '0',
  `followers` int(10) unsigned NOT NULL DEFAULT '0',
  `column2_foo` varchar(32) COLLATE utf8_unicode_ci DEFAULT NULL,
  `column3_foo` tinyint(4) NOT NULL,
  `processed` tinyint(4) NOT NULL,
  `last_modified` int(10) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `status_id` (`credential_id`,`status_id`),
  KEY `column2_foo` (`credential_id`,`column2_foo`)
) ENGINE=InnoDB AUTO_INCREMENT=906839316 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
Updated query based on sanitizing above data.
SELECT `table_foo`.* FROM `table_foo` WHERE (credential_id IN (13528, 14906, 38845)) ORDER
BY `date` DESC LIMIT 1;
Thanks!

> From: myfriendvikas@stripped
> Date: Fri, 27 Dec 2013 10:27:28 -0800
> Subject: RE: MySQL Descending ORDER issue
> To: russ_lavoie@stripped; mysql@stripped
> 
> Hi Russ,
> 
> Please share with us the exact details of the table data as well as the
> o/p.
> 
> Regards,
> 
> ViXiD
> 
> Vikas Shukla
> Mail Sent from my Windows Phone From: Russ Lavoie
> Sent: 27-12-2013 23:32
> To: mysql@stripped
> Subject: MySQL Descending ORDER issue
> Hello,
> I am currently upgrading from mysql 5.1.72 -> mysql 5.6 and the
> migration and upgrade is sound (In a QA ENV). Queries work etc.
> However, when I run a query similar to "SELECT `table`.* FROM `table`
> WHERE (some_id IN (13528, 14906, 38845)) ORDER BY `date` DESC LIMIT
> 1;" on 5.1.72 and on 5.6.15 I get back different data.  The date for
> all of the data are exactly the same to the second.
> 
> However, if I run "SELECT `table`.* FROM `table` WHERE (some_id IN
> (13528, 14906, 38845)) ORDER BY `date` LIMIT 1;" it comes back with
> the exact same data that is expected.
> Is this a bug? Or am I missing here?
> Thanks!
> 
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql
> 
 		 	   		  
Thread
MySQL Descending ORDER issueRuss Lavoie27 Dec
  • Re: MySQL Descending ORDER issueDan Nelson27 Dec
RE: MySQL Descending ORDER issueVikas Shukla27 Dec
  • RE: MySQL Descending ORDER issueRuss Lavoie27 Dec