Print the specific information of known exceptions to better understand the cause of the problem

[summary]
1. impl insert with mode delayed=0/1
2. impl simple select bit data from table

There is a problem with the judgment condition. You cannot ignore the case where the primary key value is 0

Delete the temporary directory to solve the copy problem

1.Repair the (ha_tianmu:: index_read) interface
2.Repair the (ha_tianmu:: position) interface
3.Repair the (ha_tianmu::rnd_pos) interface

The tianmu engine only supports primary keys,
and unique constraints and secondary indexes are not supported,
Therefore, only scanning with primary key scenarios is allowed here.

insert data for test
set tianmu_insert_delayed=OFF for test

    Cause of error:
        Update multiple values does not work with WHERE IN
        clause Update multiple values does not work with where in clause.
        Predicate push-down from TIANMU is used, and this process works fine.
        But when you get the direct result,
        it is not compatible with TIANMU's dimen_group concrete type.
        In the execution of a predicate push-down,
        must get the Filter so that the execution of the follow-up to value,
        namely DimensionGroupFilter,
        but the current statement USES the materialized DimensionGroupMaterialized operation

    Solution Strategy:
        If the query is executed by a predicate pushdown, materialization is not enabled

    What remains:
        When no materialization operation is used in predicate push-down,
        the impact on query performance of predicate push-down
        needs to be cross-checked against benchmarks

[summary]
1 turn on the HA_CREATE_USED_COMMENT switch;

[summary]
1. rename file name in handler, just like innodb, myisam ... does.
2. reorganize code about tianmu_handler.cpp & tianmu_handler_com.cpp into one.

feat(tianmu) Improve the performance of master slave synchronization and the performance of the execution interface for modifying data(889)
1.
When synchronizing data, push down the conditions for delete and update.
Only qualified data will be scanned to avoid full table scanning.
When executing the push down condition, tianmu will use metadata to perform rough filtering to determine the qualified packages.
In addition, when executing the push down condition, we only need to make a materialization comparison on the qualified records,
instead of making a materialization comparison on the unqualified records.
2.
Improve the execution speed of (delete_row) and (update_row) functions. At present, it is considered to parallelize the modification of each column

[summary]
1. "log/tianmu.log" --> "tianmu_engine.log"
2. "trace.log" --> "tianmu_trace.log"
3. "query.log" --> "tianmu_query.log"

fix some warnings
add/fix mtr for alter table
support alter table: mix add/drop column、order column and other syntaxs to use

[summary]
1. NULL-->nullptr
2. namespace "DBHandler"-->"handler"
3. class TianmuHandler-->ha_tianmu
4. sdb-->tianmu
5. functions in ha_my_tianmu.cpp all renamed with prefix "ha_my_tianmu_xxx"
6. add new enum 'QueryRouteTo' to replace magic number '0/1'
7. add new enum 'TableStatus' to replace magic number '0/1/-2'

support field properties from NULL to NOT NULL
support field properties from NOT NULL to NULL

[summary]
1 add implement in check_if_supported_inplace_alter of tianmu handler;
2 add implement in inplace_alter_table of tianmu handler;
3 add implement in commit_inplace_alter_table of tianmu handler;

fix 1:#818 Master slave synchronization - There will be too many tuples problem

Cause:
Tianmu::dbhandler::TianmuHandler::current_position This variable is not initialized. In some cases,
a large value may cause too many tuples problem.
Solution: Initialize the variable

fix 2:#819 Master slave synchronization - Primary key conflict problem

Solution: Modify the modification logic of master slave synchronization, so that the delete and update operations do not follow the primary key logic

Supplement

sql/sql_insert.cc
Fix the problem that the insert statement will not generate binlog in the delayed insert mode
storage/tianmu/handler/tianmu_handler.cpp
Fix the binlog error of the line format generated by the tianmu engine

[summary]

NULL-->nullptr
namespace "DBHandler"-->"handler"
class TianmuHandler-->ha_tianmu
sdb-->tianmu
functions in ha_my_tianmu.cpp all renamed with prefix "ha_my_tianmu_xxx"

class member variable refactor：handler directory

fix(tianmu): feature: The error display is too general, and the cause of the error cannot be clearly located #706

Cause of the problem:
In the mode where the type is ref, the line number returned by the tianmu engine is 10 by default.
Modify Scheme:
Delete the logic that returns 10 rows by default, and return the number of rows in the table instead.

[summary]
1 change tianmu status var scope from SHOW_SCOPE_UNDEF to SHOW_SCOPE_GLOBAL;

fix(handler): fix the bug for create table #mysql50#q.q should return failure and actually return success (#487)
	[summary]
	1.When creating a table in the tianmu engine, add code to determine whether the table name is empty.
	2.Add issue corresponding to mtr test case.

[summary]
1 innodb(in 5.7) system variable "innodb_large_prefix" default value is ON, follow it;

(1). implement tianmu's virtual function max_supported_key_part_length;
(2). enlarge max_supported_key_length's return value from 1024 to 16*1024;
Co-authored-by: Nmergify[bot] <37929162+mergify[bot]@users.noreply.github.com>