DuckDB 2.0 Alpha Triggers: BEFORE Row-Level Support Missing, Row Triggers Cost 3x
A developer tested the DuckDB 2.0 alpha build's trigger feature against the stable 1.5 development build on the same machine. Most BEFORE FOR EACH ROW triggers fail with a 'not yet supported' error, and AFTER FOR EACH ROW triggers work for INSERT and DELETE but not UPDATE. Statement-level triggers functioned for both BEFORE and AFTER across all tested events. Benchmarks on 500,000 inserts showed a row-level AFTER INSERT trigger was about 3.0 times slower than no trigger, while a statement-level equivalent added only about 1.3 times overhead. The tester also found undocumented restrictions, including that statement and row triggers cannot be mixed on one table, and that the DROP TRIGGER syntax in the preview post fails on this build.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in