Chained SQLite triggers – why am I ending up with the wrong amount of rows?
Summary A developer encountered a data integrity issue where a chained trigger mechanism resulted in more rows in a downstream table than the intermediate table actually contained. Specifically, inserting 110 rows into arrivals resulted in 40 rows in places (correctly handling duplicates), but caused 110 rows to be inserted into _vec_queue (incorrectly bypassing the logic … Read more