In working on this I spotted a bug with the way events work for /db/-/create - it currently fires a create-table event any time you call that endpoint, even if calling it actually just inserted rows into an existing table. It also doesn't fire an insert-rows event ever.

Instead it should do this:

• If table is created with example rows, fire create-table and then insert-rows
• If table already exists and more rows are added, fire insert-rows

Originally posted by @simonw in #2101 (comment)