MySQL Bug#32426: FederatedX corrupt ORDER BY with TEXT
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Released
|
Medium
|
CaptTofu |
Bug Description
http://
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-
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/
Related branches
- Maria-captains: Pending requested
-
Diff: 784 lines (+308/-104)7 files modifiedmysql-test/suite/federated/federated_bug_32426.result (+30/-0)
mysql-test/suite/federated/federated_bug_32426.test (+24/-0)
storage/federated/ha_federated.cc (+1/-1)
storage/federatedx/federatedx_io_mysql.cc (+60/-8)
storage/federatedx/federatedx_io_null.cc (+22/-0)
storage/federatedx/ha_federatedx.cc (+140/-75)
storage/federatedx/ha_federatedx.h (+31/-20)
Changed in maria: | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → CaptTofu (capttofu) |
Changed in maria: | |
importance: | High → Medium |
Changed in maria: | |
status: | Confirmed → In Progress |
Changed in maria: | |
status: | Fix Committed → Fix Released |
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.