Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
http://bugs.mysql.com/bug.php?id=32426
mysql> select * from t1;
------
c1 |
------
abc |
gh |
f |
ijk |
de |
------
5 rows in set (0.00 sec)
mysql> select * from t1 order by c1;
------
c1 |
------
dek |
de |
d |
de |
dek |
------
5 rows in set (0.00 sec)
Check the MySQL bug link for how to repeat, or comment in the test from .mysql-test/suite/federated/federated.test
This bug was fixed in FEDERATED in MySQL, seems we need to port the fix to FEDERATEDX. The code is sufficiently different that porting the fix is not trivial.
Now that I merge MySQL 5.1.46, I get the test case and see the bug in the testsuite.
I will comment out the test in mysql-test/suite/federated/federated.test. The test needs to be re-enabled as part of this bug fix.
Re: MySQL Bug#32426: FederatedX corrupt ORDER BY with TEXT
apparently, this pertains to the how blobs are handled in Federated/FederatedX. I need to discuss with someone what exactly can be done to ensure correct ordering, even for BLOB-type fields.