Re: Behavior change around triggers between 3.19 and 3.30
Graham Holden <SQLite-xBROCQ2OzI4qxzdet/[email protected]>
| Newsgroups | gmane.comp.db.sqlite.general |
|---|---|
| Message-ID | <[email protected]> |
Thursday, January 30, 2020, 12:24:40 PM, Dominique Devienne <[email protected]> wrote: > The strange thing though, is that I can't repro on a small example. > Despite using not_there in the trigger, and doing DML and ALTER TABLE, > still doesn't fail the same way as in production. What could be the cause? --DD I suspect it may only kick-in if you use ALTER TABLE to rename either a table or column. As I understand it, the old behaviour was to JUST rename the table/column; the new behaviour also scan triggers etc. and renames any references to the table/column as well. Since a new column cannot (shouldn't?) be referenced by a trigger, there's no real need to check them. Graham _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users