Bug #20444 Partitions: extra null with archive engine
Submitted: 13 Jun 2006 23:24 Modified: 15 Jun 2006 19:02
Reporter: Peter Gulutzan Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.1.12-beta-debug OS:Linux (SUSE 10.0 / 64-bit)
Assigned to: Mikael Ronström CPU Architecture:Any

[13 Jun 2006 23:24] Peter Gulutzan
Description:
I create a table with engine=archive and list partitioning.
I insert one row (null).
I select.
I see two rows.

How to repeat:
mysql> create table t6 (s1 int) engine=archive partition by list (s1) (partition p1 values in (null));
Query OK, 0 rows affected (0.05 sec)

mysql> insert into t6 values (null);
Query OK, 1 row affected (0.04 sec)

mysql> select * from t6;
+------+
| s1   |
+------+
| NULL |
+------+
1 row in set (0.00 sec)

mysql> delete from t6;
Query OK, 2 rows affected (0.00 sec)

mysql> insert into t6 values (null);
Query OK, 1 row affected (0.00 sec)

mysql> select * from t6;
+------+
| s1   |
+------+
| NULL |
| NULL |
+------+
2 rows in set (0.00 sec)
[14 Jun 2006 0:09] Miguel Solorzano
Thank you for the bug report. Verified as described:

mysql> create table t6 (s1 int) engine=archive partition by list (s1) (partition
    -> p1 values in (null));
Query OK, 0 rows affected (0.03 sec)

mysql> insert into t6 values (null);
Query OK, 1 row affected (0.01 sec)

mysql> delete from t6;
Query OK, 2 rows affected (0.00 sec)

mysql> insert into t6 values (null);
Query OK, 1 row affected (0.00 sec)

mysql> select * from t6;
+------+
| s1   |
+------+
| NULL | 
| NULL | 
+------+
2 rows in set (0.01 sec)

mysql>
[15 Jun 2006 18:49] Mikael Ronström
Archive engine doesn't support delete
[15 Jun 2006 18:58] Reggie Burnett
Make a note in the docs that while the archive engine does work under partitoining, the user should remember the limitations of the archive engine such as not being able to delete.

Pelase mark as ! bg when done with docs.