| enable_B_compatibility fix errors on set type in B compatibility, fix: alter_table_003, multi_update, hw_datatype_set fastcheck case fix: test_auto_increment fix auto increment id problems on auto parameterization with B compatibility(No dolphin) Basically, the reason is when reusing opfusion object, the estate from m_c_local is not reset, which made it failed to update m_c_local.m_estate->first_autoinc. Only when this value is 0 will the value be updated on insersion. Therefore, simply reuse the m_estate may not be a good choice. I only do the modification within auto parameterization part, so the fix now looks like this. This is a fix for one of the problem in test_binary when setting SET dolphin.sql_mode = 'sql_mode_strict, treat_bxconst_as_binary' the following case: CREATE TABLE t1 (s1 binary(2), s2 varbinary(2)); INSERT INTO t1 VALUES (0x4100, 0x4100); in auto parameterization and P/E process this will get an error. Dolphin has it own make_const dealing with the 0x4100 condition but the two routine above still use kenel's make_const which cause the error. So we add a hook to on transformExpr to force it enter dolphin's routine. This is a fix for database failed to call the B comp version of bpchar_launch under opfusion_bpchar. this is a fix for the routine failed to go to the right varchar_launch under sql bypass with B compatibility. Same as the bpchar_launch stuff. This is a fix for builtin_funcs/b_compatibility_time_funcs3, builtin_funcs/b_compatibility_time_funcs2 add B format GPC paramters remove guc param for auto parameterization: max_parameterization_query_stored auto parameterization enchance test case bypass some condition in B comp | 9 个月前 |
