- 31 10月, 2022 1 次提交
-
-
由 lylth 提交于
[summary] 1.class member variable refactor:common directory;
-
- 30 10月, 2022 1 次提交
-
-
由 DandreChen 提交于
class member variable refactor:handler directory
-
- 28 10月, 2022 2 次提交
- 27 10月, 2022 3 次提交
-
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
- 26 10月, 2022 11 次提交
-
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
由 一位用户 提交于
-
由 一位用户 提交于
update Release Notes and Installation Package
-
由 shangyanwen 提交于
-
由 DandreChen 提交于
Eplain query Q4 lead to crash,because assert(join == NULL) in SELECT_LEX::optimize() function. the root cause is that the new join is not released. we can use sl->cleanup(true) to release it
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
由 shangyanwen 提交于
-
由 shizhao 提交于
-
- 25 10月, 2022 6 次提交
-
-
由 shizhao 提交于
-
由 shizhao 提交于
-
由 一位用户 提交于
Delete the incorrect configuration and modify the Chinese directory
-
由 一位用户 提交于
-
由 一位用户 提交于
-
由 lihongjian 提交于
Cause: When the date in MySQL is 0, the value is considered to be null. MySQL handles this problem. If you query the statement of isull, you will convert isnull to=0. This problem is that the value with the date of 0 is inserted into the table. The query and deletion results of the tianmu engine are not consistent. The reason for the inconsistency is that the syntax parsing logic of the query and deletion of tianmu is not the same Solution: Unified query logic and modification logic for date format processing. Keep the phenomenon of tianmu consistent with innodb.
-
- 24 10月, 2022 8 次提交
-
-
由 一位用户 提交于
-
由 一位用户 提交于
-
由 Nliver 提交于
-
由 Nliver 提交于
-
由 一位用户 提交于
-
由 zsp108 提交于
-
由 CodingSuen 提交于
fix(tianmu): feature: The error display is too general, and the cause of the error cannot be clearly located #706
-
由 CodingSuen 提交于
fix(tianmu): feature: The error display is too general, and the cause of the error cannot be clearly located #706
-
- 23 10月, 2022 1 次提交
-
-
由 悟世者 提交于
fix(tianmu): Fixed tianmu syntax compatibility issue when continuous equivalent predicates are eliminated (#733) The root cause is that the tianmu syntax tree conversion cannot support continuous null-value elimination, and the cleaned equal-value elimination items are retained to be compatible with the tianmu execution plan
-
- 21 10月, 2022 7 次提交
-
-
由 lihongjian 提交于
-
由 lihongjian 提交于
Cause: There is a problem with the corresponding table index when creating entity columns Solution: When creating an entity column, the table index you try to import corresponds to the position in the tables list one by one
-
由 悟世者 提交于
The cause of an error is that you need to identify the returned result of the exists subquery for sl->join->zero_result_cause Determines whether a return value exists. and format query.cpp : The exists subquery determines whether a value exists during the query optimization phase result is not set to zero only when a matching value is found in the query optimization phase When a field has an index, the optimization phase scans the table through the index The primary key implementation of the current column storage engine has a problem with the primary key index to scan the table for data As a result, the primary key index is used to obtain the exists subquery result in the query optimization phase. Therefore, the exists subquery is not executed in the query execution phase scan the table for data Remove the following temporary practices after primary key indexing is complete
-
由 悟世者 提交于
replace always true for examples: select * from t1 where b>2 or 1=2; select * from t1 where b>2 or 1<2; select * from t1 where b>2 or 1>2; select * from t1 where b>2 or 1=1; select * from t1 where b>2 or 1; select * from t1 where b>2 or 0; select * from t1 where ((((1=1) or (3=3)) and (3=3)) or ((1=100) and (5=a))); select * from t1 where ((((1=1) or (3=3)) and (3=4)) or ((1=100) and (5=a))); select * from t1 where ((((1=2) or (3=3)) and (3=3)) or ((1=100) and (5=a))); select * from t1 where ((((1>2) or (3=3)) and (3=3)) or ((1=1) and (5=a))); select * from t1 where ((((1=2) or (3<3)) and (3=3)) or ((1=1) and (5=a))); select * from t1 where ((((1=2) or (3<3)) and (3>1)) or ((1=1) and (5=a))); select * from t1 where ((((1=2) or (3=3)) and (3=1)) or ((1>1) and (5=a)));
-
由 lujiashun 提交于
[summary] 1 the root reason is because of the variable ‘tianmu_insert_delayed’,set it off; 2 in debug version, it crashes, fix it; 3 add mtr case for this issue;
-
由 lylth 提交于
Replace the function FindCurrentRowByVMTable that gets the current row to FindCurrentRow.
-
由 shizhao 提交于
-