UPDATE statement on a VIEW built with a UNION clause does not compile #1018
Comments
|
ah right. thats gonna be an interesting one. Do you know what happens to an update on a view that doesn't have a trigger? Does it crash at runtime when you execute the view or does it just do nothing? Would be nice if we can also fail at compile time if you have an update statement on a view with on corresponding trigger (if SQLite also disallows it) |
|
SQLite docs seem to imply that it's an error to perform
A little test confirms it: $ sqlite3
SQLite version 3.24.0 2018-06-04 14:10:15
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> CREATE TABLE foo (
...> id INTEGER NOT NULL PRIMARY KEY,
...> name TEXT NOT NULL
...> );
sqlite> CREATE VIEW bar AS SELECT * FROM foo;
sqlite> UPDATE bar SET name = 'Baz' WHERE id = 1;
Error: cannot modify bar because it is a view
sqlite> CREATE TRIGGER bar_update
...> INSTEAD OF UPDATE OF name ON bar
...> BEGIN
...> UPDATE foo SET name = new.name WHERE id = new.id;
...> END;
sqlite> UPDATE bar SET name = 'Baz' WHERE id = 1;
sqlite>
That'd be awesome |
|
awesome. thanks! |
AlecKazakova
added
component: sql-psi
Versions: 1.0.0-alpha5, 1.0.0-rc2
Have a couple of tables, a
VIEW, aTRIGGERon aVIEWand anUPDATEstatement:Compilation fails with the following error:
Removing
UNIONand the secondSELECTfrom theVIEWlets the compiler to run just fine.The text was updated successfully, but these errors were encountered: