Re: MySQL Descending ORDER issue

2013-12-27 Thread Dan Nelson
In the last episode (Dec 27), Russ Lavoie said: > 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 (credential_id > IN (13528, 14906, 3884

RE: MySQL Descending ORDER issue

2013-12-27 Thread Russ Lavoie
T `table_foo`.* FROM `table_foo` WHERE (credential_id IN (13528, 14906, 38845)) ORDER BY `date` DESC LIMIT 1; Thanks! > From: myfriendvi...@gmail.com > Date: Fri, 27 Dec 2013 10:27:28 -0800 > Subject: RE: MySQL Descending ORDER issue > To: russ_lav...@hotmail.com; mysql@lists.mysql.com

RE: MySQL Descending ORDER issue

2013-12-27 Thread Vikas Shukla
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@lists.mysql.com Subject: MySQL Descending ORDER issue Hello, I am currently upgrading from mysql

MySQL Descending ORDER issue

2013-12-27 Thread Russ Lavoie
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