V Narayanan 148141fa70 Bug#45803 Inaccurate estimates for partial key values with IBMDB2I ... Some collations were causing IBMDB2I to report inaccurate key range estimations to the optimizer for LIKE clauses that select substrings. This can be seen by running EXPLAIN. This problem primarily affects multi-byte and unicode character sets. This patch involves substantial changes to several modules. There are a number of problems with the character set and collation handling. These problems have been or are being fixed, and a comprehensive test has been included which should provide much better coverage than there was before. This test is enabled only for IBM i 6.1, because that version has support for the greatest number of collations.		2009-07-06 14:19:32 +05:30
..
ibmdb2i_bug_44020.result	Importing test cases for IBMDB2I	2009-04-14 16:32:55 +05:30
ibmdb2i_bug_44025.result	Importing test cases for IBMDB2I	2009-04-14 16:32:55 +05:30
ibmdb2i_bug_44232.result	Bug#44232 Error msg should be improved when collation not supported.	2009-05-14 16:05:09 +05:30
ibmdb2i_bug_44610.result	Bug#44610 RCDFMT clause requested when creating DB2 table	2009-05-17 21:55:23 +05:30
ibmdb2i_bug_45196.result	Bug#45196 Some collations do not sort correctly with IBMDB2I	2009-06-29 07:32:17 +05:30
ibmdb2i_bug_45793.result	Bug#45793 macce charset causes error with IBMDB2I	2009-07-02 13:34:23 +05:30
ibmdb2i_collations.result	Bug#45803 Inaccurate estimates for partial key values with IBMDB2I	2009-07-06 14:19:32 +05:30