MySQL Bugs: #19009: INSERT DELAYED into a <view> refuses to insert

Bug #19009	INSERT DELAYED into a <view> refuses to insert
Submitted:	11 Apr 2006 13:51	Modified:	14 Nov 2006 19:29
Reporter:	Alexander Ivanov	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.0, 5.1	OS:
Assigned to:	Paul DuBois	CPU Architecture:	Any

Description:
INSERT DELAYED into a <view> reports an error
(in both 5.0 and 5.1):

mysql> DROP TABLE IF EXISTS t1;
Query OK, 0 rows affected (0.01 sec)

mysql> DROP VIEW IF EXISTS v1;
Query OK, 0 rows affected (0.02 sec)

mysql> CREATE TABLE t1 (n INT);
Query OK, 0 rows affected (0.08 sec)

mysql> CREATE VIEW  v1 AS SELECT * FROM t1;
Query OK, 0 rows affected (0.05 sec)

mysql> INSERT DELAYED INTO v1 VALUES (1);
ERROR 1347 (HY000): 'test.v1' is not BASE TABLE

mysql> SELECT * FROM t1;
Empty set (0.00 sec)

As discussed with Psergey and Sanja (see also BUG#13683), either
INSERT DELAYED into a <view> should be executed as normal (i.e.
not delayed) INSERT (and really why not?) or there should be an
explicit remark in the Reference Manual.

How to repeat:
See above

Thank you for the bug report.

This is a design limitation that is not trivial to lift. So please have it mentioned in the appropriate place in the documentation.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

I've updated the manual to indicate that INSERT DELAYED
is not supported for views.