drop table resources_fts drops the FTS table and the other ones that it created (resources_fts_data, resources_fts_idx, resources_fts_docsize, resources_fts_config) - but keeps the triggers.

I can reliably get the list of triggers to delete from select name from sqlite_master where type = 'trigger' and tbl_name = 'resources';

Strange - https://www.sqlite.org/lang_droptrigger.html says "Note that triggers are automatically dropped when the associated table is dropped" but that doesn't seem to be true in my experimenting.

UPDATE: no that makes sense - the triggers are on resources which still exists, it was resources_fts that was dropped.

Looks like safest option is to loop through those trigger names and run DROP TRIGGER IF EXISTS foo on each one.

I think the method should be called table.disable_fts() - the opposite of table.enable_fts(...).

There should be a sqlite-utils disable-fts database.db tablename command to match it.