github
html_url | issue_url | id | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591768604 | https://api.github.com/repos/simonw/sqlite-utils/issues/88 | 591768604 | MDEyOklzc3VlQ29tbWVudDU5MTc2ODYwNA== | 9599 | 2020-02-27T04:03:03Z | 2020-02-27T04:03:03Z | OWNER | `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. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
571805300 | |
https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769046 | https://api.github.com/repos/simonw/sqlite-utils/issues/88 | 591769046 | MDEyOklzc3VlQ29tbWVudDU5MTc2OTA0Ng== | 9599 | 2020-02-27T04:05:15Z | 2020-02-27T04:05:15Z | OWNER | I can reliably get the list of triggers to delete from `select name from sqlite_master where type = 'trigger' and tbl_name = 'resources';` | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
571805300 | |
https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769171 | https://api.github.com/repos/simonw/sqlite-utils/issues/88 | 591769171 | MDEyOklzc3VlQ29tbWVudDU5MTc2OTE3MQ== | 9599 | 2020-02-27T04:05:58Z | 2020-02-27T04:26:31Z | OWNER | 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. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
571805300 | |
https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769373 | https://api.github.com/repos/simonw/sqlite-utils/issues/88 | 591769373 | MDEyOklzc3VlQ29tbWVudDU5MTc2OTM3Mw== | 9599 | 2020-02-27T04:06:47Z | 2020-02-27T04:06:47Z | OWNER | Looks like safest option is to loop through those trigger names and run `DROP TRIGGER IF EXISTS foo` on each one. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
571805300 | |
https://github.com/simonw/sqlite-utils/issues/88#issuecomment-591769759 | https://api.github.com/repos/simonw/sqlite-utils/issues/88 | 591769759 | MDEyOklzc3VlQ29tbWVudDU5MTc2OTc1OQ== | 9599 | 2020-02-27T04:08:29Z | 2020-02-27T04:08:29Z | OWNER | 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. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
571805300 | |
https://github.com/simonw/sqlite-utils/issues/86#issuecomment-591770623 | https://api.github.com/repos/simonw/sqlite-utils/issues/86 | 591770623 | MDEyOklzc3VlQ29tbWVudDU5MTc3MDYyMw== | 9599 | 2020-02-27T04:12:39Z | 2020-02-27T04:12:39Z | OWNER | I pushed a branch with my experiment in it, but I'm going to fix this by throwing an error on `[` or `]` in a column name instead - I won't implement the changes from that branch. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
564579430 | |
https://github.com/simonw/sqlite-utils/issues/82#issuecomment-591771532 | https://api.github.com/repos/simonw/sqlite-utils/issues/82 | 591771532 | MDEyOklzc3VlQ29tbWVudDU5MTc3MTUzMg== | 9599 | 2020-02-27T04:16:30Z | 2020-02-27T04:16:30Z | OWNER | Closing as can't reproduce. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
559197745 |