Inserting and Updating with Views

You are viewing an old version of this article. View the current version here.

A view can be used for inserting or updating. However, there are certain limitations.

Updating with views

A view cannot be used for updating if it uses any of the following:

  • ALGORITHM=TEMPTABLE (see View Algorithms)
  • An aggregate function, such as MAX(), MIN(), SUM() or COUNT()
  • subquery in the SELECT list
  • subquery in the WHERE clause referring to a table in the FROM clause
  • if it has no underlying table because it refers only to literal values
  • the FROM clause contains a non-updatdable view.
  • multiple references to any base table column
  • an outer join
  • an inner join where more than one table in the view definition is being updated
  • if there's a LIMIT clause, the view does not contain all primary or not null unique key columns from the underlying table and the updatable_views_with_limit system variable is set to 0.

Inserting with views

A view cannot be used for inserting if it fails any of the criteria for updating, and must also meet the following conditions:

  • the view contains all base table columns that don't have default values
  • there are no duplicate view column names
  • the view columns are all simple columns, and not derived in any way. The following are examples of derived columns
    • column_name + 25
    • LOWER(column_name)
    • (subquery)
    • 9.5
    • column1 / column2

Checking whether a view is updatable

MariaDB stores an IS_UPDATABLE flag with each view, so it is always possible to see if MariaDB considers a view updatable (although not necessarily insertable) by querying the IS_UPDATABLE column in the INFORMATION_SCHEMA.VIEWS table.


The WITH CHECK OPTION clause is used to prevent updates or inserts to views unless the WHERE clause in the SELECT statement is true.

There are two keywords that can be applied. WITH LOCAL CHECK OPTION restricts the CHECK OPTION to only the view being defined, while WITH CASCADED CHECK OPTION checks all underlying views as well. CASCADED is treated as default if neither keyword is given.

If a row is rejected because of the CHECK OPTION, an error similar to the following is produced:

ERROR 1369 (HY000): CHECK OPTION failed 'db_name.view_name'

A view with a WHERE which is always false (like WHERE 0) and WITH CHECK OPTION is similar to a BLACKHOLE table: no row is ever inserted and no row is ever returned. An insertable view with a WHERE which is always false but no CHECK OPTION is a view that accepts data but does not show them.


MariaDB [test]> CREATE TABLE table1 (x INT);

MariaDB [test]> CREATE VIEW view1 AS SELECT x, 99 AS y FROM table1;

Checking whether the view is updateable:

| view1      | YES          |

This query works, as the view is updateable:

MariaDB [test]> UPDATE view1 SET x = 5;

This query fails, since column y is a literal.

MariaDB [test]> UPDATE view1 SET y = 5;
ERROR 1348 (HY000): Column 'y' is not updatable

Here are three views to demonstrate the WITH CHECK OPTION clause.

MariaDB [test]> CREATE VIEW view_check1 AS SELECT * FROM table1 WHERE x < 100 WITH CHECK OPTION;

MariaDB [test]> CREATE VIEW view_check2 AS SELECT * FROM view_check1 WHERE x > 10 WITH LOCAL CHECK OPTION;

MariaDB [test]> CREATE VIEW view_check3 AS SELECT * FROM view_check1 WHERE x > 10 WITH CASCADED CHECK OPTION;

This insert succeeds, as view_check2 only checks the insert against view_check2, and the WHERE clause evaluates to true (150 is >10).

MariaDB [test]> INSERT INTO view_check2 VALUES (150);

This insert fails, as view_check3 checks the insert against both view_check3 and the underlying views. The WHERE clause for view_check1 evaluates as false (150 is >10, but 150 is not <100), so the insert fails.

MariaDB [test]> INSERT INTO view_check3 VALUES (150);
ERROR 1369 (HY000): CHECK OPTION failed 'test.view_check3'


Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.