feature: Enable the max length of bit type to 64

[RingsC]

Is your feature request related to a problem? Please describe.

Now, the max length of bit is limited to 63, that is a wired length and not compatible with mysql dehavior. Therefore, we should support all the functions fully, bit(64).

 Bit-Value Type - BIT
The BIT data type is used to store bit values. A type of BIT(M) enables storage of M-bit values. M can range from 1 to 64.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[hustjieke]

ACK.

[hustjieke]

To support bit M=64, we need to do two things:

1. Expand TIANMU_BIT_MAX_PREC from 63 to 64, it is used in function GetAttrTypeInfo( ) to intercept invalid bit precison that over 63.

2. Expand max value during encode record EncodeRecord( ), otherwise the bit64 will be truncated. The code will be like:

-        if (v > common::TIANMU_BIGINT_MAX)  // v > bigint max when uint64_t is supported
-          v = common::TIANMU_BIGINT_MAX;    // TODO(fix with bit prec)
+        if (v > ULLONG_MAX)  // v > bigint max when uint64_t is supported
+          v = ULLONG_MAX;    // TODO(fix with bit prec)

3. Modify the fixmax for bit type with precision(M)

    case common::ColumnType::BIT:
      valtype = ValueType::VT_FIXED;
      fixmax = MAX(common::TIANMU_BIGINT_MAX,
                   -common::TIANMU_BIGINT_MIN);  // TODO(fix max value with common::TIANMU_BIT_MAX_PREC)

I impl a simple demo to verify my idea，it works！

mysql> create table bit64(a bit(64)) engine=tianmu;
Query OK, 0 rows affected (0.01 sec)

mysql> insert into bit64 values(0xFFFFFFFFFFFFFFFF);
Query OK, 1 row affected (0.01 sec)

mysql> select hex(a), bin(a), a+0 from bit64;
+------------------+------------------------------------------------------------------+----------------------+
| hex(a)           | bin(a)                                                           | a+0                  |
+------------------+------------------------------------------------------------------+----------------------+
| FFFFFFFFFFFFFFFF | 1111111111111111111111111111111111111111111111111111111111111111 | 18446744073709551615 |
+------------------+------------------------------------------------------------------+----------------------+
1 row in set (0.00 sec)

mysql> select a+0 from bit64 where a=0xFFFFFFFFFFFFFFFF;
+----------------------+
| a+0                  |
+----------------------+
| 18446744073709551615 |
+----------------------+
1 row in set (0.00 sec)

[hustjieke]

This depends on impl of unsigned bigint.