mariadb/storage
Neeraj Bisht f7f21ee732 Bug#11758009 - UNION EXECUTION ORDER WRONG ?
Problem:-
In case of blob data field, UNION ALL doesn't give correct result.

Analysis:-
In MyISAM table, when we dont want to check for the distinct for particular 
key, we set the key_map to zero.

While writing record in MyISAM table, we check the distinct with the help 
of keys, by checking whether that key is active in key_map and then writing 
the record.

In case of blob field, we are checking for distinct by unique constraint, 
where we are not checking whether that unique key is active or not in key_map.

Solution:
Before checking for distinct, check whether any key is active in key_map.


storage/myisam/mi_write.c:
  check whether key_map is active before checking distinct.
2013-01-15 14:33:22 +05:30
..
archive Bug #13819630 ARCHIVE TABLE WITH 1000+ PARTITIONS CRASHES SERVER 2012-12-20 19:26:20 +05:30
blackhole Merge 5.5.24 back into main 5.5. 2012-05-07 22:20:42 +02:00
csv Updated/added copyright headers 2012-02-16 10:48:16 +01:00
example Bug#11815557 60269: MYSQL SHOULD REJECT ATTEMPTS TO CREATE SYSTEM 2012-04-11 15:53:17 +05:30
federated Bug #12876932 - INCORRECT SELECT RESULT ON FEDERATED TABLE 2012-07-26 15:29:19 +05:30
heap Bug #11759445: CAN'T DELETE ROWS FROM MEMORY TABLE WITH HASH KEY. 2012-11-07 09:03:33 +05:30
innobase Merge from mysql-5.1 to mysql-5.5 2013-01-14 10:57:04 +05:30
myisam Bug#11758009 - UNION EXECUTION ORDER WRONG ? 2013-01-15 14:33:22 +05:30
myisammrg
ndb
perfschema Bug#16060864 SEGMENTATION FAULT IN PERFORMANCE_SCHEMA WITH HISTORY SIZE 0 2013-01-02 11:00:55 +01:00