"SAVEPOINT" fails after a first successfull released savepoint.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PBXT |
New
|
Undecided
|
Unassigned |
Bug Description
When using PBXT as a table's engine and also using SAVEPOINT, the second release call will fail. We believe that since PBXT doesn't support SAVEPOINT it should not raise an ERROR.
Here is a way to reproduce the bug (we used mysql console client):
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 36
Server version: 5.1.55 Source distribution
Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
This software comes with ABSOLUTELY NO WARRANTY. This is free software,
and you are welcome to modify and redistribute it under the GPL v2 license
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> create database pbxt_savepoint;
Query OK, 1 row affected (0,00 sec)
mysql> use pbxt_savepoint;
Database changed
mysql> create table pbxt_table (name varchar(80)) engine=pbxt;
Query OK, 0 rows affected (0,18 sec)
mysql> show tables;
+------
| Tables_
+------
| pbxt_table |
+------
1 row in set (0,00 sec)
mysql> show table status;
+------
| 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 |
+------
| pbxt_table | PBXT | 10 | Dynamic | 0 | 96 | 1024 | 16777215 | 4096 | 0 | NULL | NULL | NULL | NULL | latin1_swedish_ci | NULL | | |
+------
1 row in set (0,00 sec)
mysql> begin;
Query OK, 0 rows affected (0,00 sec)
mysql> savepoint here;
Query OK, 0 rows affected (0,00 sec)
mysql> insert into pbxt_table (name) values ('name');
Query OK, 1 row affected (0,00 sec)
mysql> release savepoint here;
Query OK, 0 rows affected (0,00 sec)
mysql> savepoint here;
ERROR 1178 (42000): The storage engine for the table doesn't support SAVEPOINT
mysql>