1
0
mirror of https://github.com/MariaDB/server.git synced 2025-11-12 10:22:39 +03:00
Files
mariadb/mysql-test/t
gkodinov/kgeorge@macbook.gmz c606c63f0e Bug #21159: Optimizer: wrong result after AND with different data types
Disable const propagation for Item_hex_string.
This must be done because Item_hex_string->val_int() is not
the same as (Item_hex_string->val_str() in BINARY column)->val_int().
We cannot simply disable the replacement in a particular context (
e.g. <bin_col> = <int_col> AND <bin_col> = <hex_string>) since
Items don't know the context they are in and there are functions like 
IF (<hex_string>, 'yes', 'no').
Note that this will disable some valid cases as well 
(e.g. : <bin_col> = <hex_string> AND <bin_col2> = <bin_col>) but 
there's no way to distinguish the valid cases without having the
Item's parent say something like : Item->set_context(Item::STRING_RESULT)
and have all the Items that contain other Items do that consistently.
2006-08-15 10:13:17 +03:00
..
2006-05-29 16:27:45 +02:00
2006-05-01 21:30:09 +03:00
2006-06-17 02:57:50 +04:00
2006-06-17 02:57:50 +04:00
2006-03-01 15:50:15 +04:00
2006-06-27 00:47:52 +04:00
2006-05-24 17:21:35 +03:00
2006-06-14 23:54:08 +04:00
2006-06-20 00:52:26 +04:00
2006-04-11 15:26:18 +05:00
2006-06-27 17:00:24 +05:00
2006-07-21 11:59:46 +03:00
2006-05-06 23:48:13 -07:00
2006-05-17 20:48:48 -07:00
2006-03-06 23:43:47 +01:00
2006-05-29 19:07:35 +04:00
2006-05-01 22:10:50 -04:00
2006-07-17 14:22:21 +04:00
2006-01-06 00:47:49 +02:00
2006-02-20 15:03:16 +01:00
2006-02-07 19:57:31 +01:00
2006-06-12 15:36:12 +02:00
2006-07-13 16:35:25 -07:00
2006-07-01 09:28:41 +04:00
2006-06-17 02:57:50 +04:00
2006-03-08 10:40:29 +01:00
2006-04-27 21:59:04 +09:30
2006-04-26 17:09:41 -07:00