Debugging the SQL triggers is hard because stack traces are missing/start without context.
The throw below is triggered by the change queue. Debugging the trigger requires a breakpoint at the correct "time" when the query breaks. If a stack trace of a side-effect includes the cause, debugging becomes simpler.
Idea
We might be able to use the Kysely plugin interface to trigger side effects like the change queue.
Context
Debugging the SQL triggers is hard because stack traces are missing/start without context.
The throw below is triggered by the change queue. Debugging the trigger requires a breakpoint at the correct "time" when the query breaks. If a stack trace of a side-effect includes the cause, debugging becomes simpler.
Idea
We might be able to use the Kysely plugin interface to trigger side effects like the change queue.