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
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` bigi
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 5
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
Dear MySQL users,
MySQL Connector/C 6.1.3, a new version of the C API for client/server
communication for the MySQL database management system, has been
released.
This version of Connector/C provides full support for MySQL 5.6
protocol. Connector/C is compatible with the client libraries
(libmys
