Bug #29342 Unsupported query executed by Brighthouse(storage engine) with no error message.
Submitted: 25 Jun 2007 17:33 Modified: 25 Jul 2007 18:49
Reporter: amir sheikh Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server: Memory storage engine Severity:S3 (Non-critical)
Version:5.1.14-beta OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[25 Jun 2007 17:33] amir sheikh
The following defect is reproduciable for our storage engine(The Brighthouse) implemented with mysql.

How to repeat:
Steps to Reproduce:
1. Create two Brighthouse tables with same table structures. 
For example:
create table t1(a int) engine=brighthouse; and 
create table t2(a int) engine=brighthouse;

2. Load some data in table t1.

3. Execute the following query.

mysql> insert into t2 select * from t1;

This query will execute with zero rows affected and one warning. 
Note: inserting data from BH table to BH table is not supported.

4. Execute
mysql> show warnings;
| Level | Code | Message |
| Error | 1031 | Table storage engine for 't2' doesn't have this option |
1 row in set (0.00 sec)

The above message should appear at the time the above unsupported query is executed.

Suggested fix:
It is assumed about engines that they provide a certain interface. Some function like inserting rows in a table are optional functions in this interface.

If MySQL tries to use an optional function and it is not implemented in a given engine usually it reports an error.

In this case it reports a warning instead of an error so it is a bug in mysql.

Simply speaking, we report the information that the functionality of rows inserting is not implemented for BrightHouse tables. MySQL decides what to do with this information: whether to report it as warning or an error. MySQL reports it as warning.



[25 Jun 2007 18:49] Sveta Smirnova
Thank you for the report.

But version 5.1.14 is quite old. Please try with current version 5.1.19 and say us result.
[25 Jul 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".