I'm pleased to announce the release of Vertical Partitioning storage engine version 0.2.
http://launchpad.net/vpformysql
The main changes in this version are following.
- Support MySQL's table partitioning.
MySQL's table partitioning that is only introduced last release is now supported.
note: After this version, you need to apply a patch for installing Vertical Partitioning storage engine.
- After this version, the primary key part of InnoDB's secondary index is effectively used.
You can use the primary key columns with InnoDB's secondary index by using following statements.
create table tbl_b(
col_a int not null,
col_b varchar(20),
col_c int not null,
primary key(col_a),
key idx1(col_c)
)engine=InnoDB;
create table tbl_c(
col_a int not null,
col_b varchar(20),
col_c int not null,
primary key(col_a),
key idx1(col_c)
)engine=InnoDB;
create table tbl_a(
col_a int not null,
col_b varchar(20),
col_c int not null,
primary key(col_a),
key idx1(col_c, col_a)
)engine=VP comment='table_name_list "tbl_b tbl_c"';
note: Vertical Partitioning storage engine can use index with primary key together with index without primary key, because Vertical Partitioning storage engine can use different storage engines for child tables at same table. In this case, the purpose of writing the column of primary key to tbl_a's idx1 is to absorb the difference by this coexistence.
Please see "99_change_logs.txt" in the download documents for checking other changes.
Enjoy!
Subscribe to:
Post Comments (Atom)
Are VP/Spider the same thing?
ReplyDeleteNo. VP are Spider are different storage engine.
ReplyDeleteSpider is a storage engine for database sharding.
VP is a storage engine for vertical partitioning.
VP and Spider can cooperate with other storage engines.
cool!
ReplyDeleteLike to see more:-)
Cool!
ReplyDeleteI would like to see more :-)