[MySQL][Spider]Spider storage engine 0.15 released

I'm pleased to announce the release of Spider storage engine version 0.15.(beta)
http://spiderformysql.com/

The main changes in this version are following.
- Add table parameter "auto_increment_mode".
- Add server parameter "spider_auto_increment_mode".
  Spider supports 3 modes.
  0:Use a count that Spider get from the remote server with exclusive lock for auto increment value.
  1:Use a count that Spider has internal for auto increment value.
  2:Auto increment value is given by the remote server.

- Add server parameter "spider_ping_interval_at_trx_start".
  Performance improvement by frequency decrease of checking broken connections.

Please see "99_change_logs.txt" in the download documents for checking other changes.

Enjoy!

[MySQL][Spider]Spider storage engine 0.14 released

I'm pleased to announce the release of Spider storage engine version 0.14.(beta)
http://spiderformysql.com/

The main changes in this version are following.
- The standalone compilation with Spider storage engine is now available.
Please see "03_install_spider_storage_engine.txt" for more detail.
Tatsuhiko and Tetsuro,
Thank you for your advice!

Please see "99_change_logs.txt" in the download documents for checking other changes.


Spider storage engine was introduced at following with the usage.

The Data Charmer(English)
http://datacharmer.blogspot.com/2009/04/test-driving-spider-storage-engine.html
http://datacharmer.blogspot.com/2009/07/sharding-for-masses-spider-storage.html
　Giuseppe,
　　Thank you for introducing Spider.

Unoh Labs(Japanese)
http://labs.unoh.net/2009/07/mysqlspider.html
Satoru,
　　Thank you for introducing Spider.

Enjoy!

[MySQL][Spider]Spider storage engine 0.13 released

I'm pleased to announce the release of Spider storage engine version 0.13.(beta)
http://spiderformysql.com/

The main changes in this version are following.
- Add table parameter "crd_bg_mode" and "sts_bg_mode".
- Add server parameter "spider_crd_bg_mode" and "spider_sts_bg_mode".
  MySQL needs table's analysis informations when select statement is executed. Spider storage engine gets this informations from remote table but this action often generates over-heads.
  This options remove generated over-heads by getting analysis informations at background but you must set this option to 0 if the table's analysis informations change frequently.
  * There are other options for the over-heads reduction of the analysis informations acquisition. I will introduce this at another time.

Please see "99_change_logs.txt" in the download documents for checking other changes.

Enjoy!

[MySQL][Other]Condition Pushdown for ha_partition 0.1 released

I'm pleased to announce the release of Condition Pushdown for ha_partition version 0.1.
http://launchpad.net/partitionconditionpushdownformysql

This release is a patch file for MySQL's table partitioning feature. (ndb is excluded)
This patch file works to add methods("cond_push" and "cond_pop") to ha_partition. As a result, every storage engine's table that use table partitioning can get condition-pushdown through ha_partition.

There was no problem because only ndb supported engine-condition-pushdown up to now.
This patch was needed because the Spider storage engine supported engine-condition-pushdown recently.

Enjoy!

[MySQL][VP]Vertical Partitioning storage engine 0.2 released

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!