Details
Technical task
Minor
Description
As mentioned in this comment, SHOW TABLE STATUS for LevelDB tables is likely to be improved. I will file it as a feature request so it's not forgotten.
Currently the output looks like this:
mysql> create table t1 (pk int auto_increment primary key) engine=LevelDB;
Query OK, 0 rows affected (0.60 sec)
mysql> insert into t1 values (null);
Query OK, 1 row affected (0.01 sec)
mysql> show table status from test like 't1';
+------+---------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+-------------------+----------+----------------+---------+
| Name | Engine | Version | Row_format | Rows | Avg_row_length | Data_length | Max_data_length | Index_length | Data_free | Auto_increment | Create_time | Update_time | Check_time | Collation | Checksum | Create_options | Comment |
+------+---------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+-------------------+----------+----------------+---------+
| t1 | LEVELDB | 10 | Fixed | 1000 | 0 | 0 | 0 | 0 | 0 | 0 | NULL | NULL | NULL | latin1_swedish_ci | NULL | | |
+------+---------+---------+------------+------+----------------+-------------+-----------------+--------------+-----------+----------------+-------------+-------------+------------+-------------------+----------+----------------+---------+
1 row in set (0.00 sec)
That is, most values are zeros, including auto-increment (even although it's shown correctly in SHOW CREATE TABLE). Hopefully it will get better.
Test case:
create table t1 (pk int auto_increment primary key) engine=LevelDB;
insert into t1 values (null);
query_vertical show table status from test like 't1';
It is also covered in leveldb.autoincrement test.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions