pull_requests: 1082769953
This data as json
| id | node_id | number | state | locked | title | user | body | created_at | updated_at | closed_at | merged_at | merge_commit_sha | assignee | milestone | draft | head | base | author_association | repo | url | merged_by | auto_merge |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1082769953 | PR_kwDOCGYnMM5AicIh | 498 | closed | 0 | fix: enable-fts permanently save triggers | 7908073 | I was wondering why my all my databases were giving wild search results. Turns out create_trigger was not sticking! Running `sqlite-utils triggers x.db` shows `[]` after running `enable-fts` using the python api. Looking at the counts trigger it seems that is the right way to save triggers. triggers show up now <!-- readthedocs-preview sqlite-utils start --> ---- :books: Documentation preview :books:: https://sqlite-utils--498.org.readthedocs.build/en/498/ <!-- readthedocs-preview sqlite-utils end --> | 2022-10-11T05:10:51Z | 2022-10-15T04:33:08Z | 2022-10-11T06:34:31Z | ab24d21e9c2aa9c514c3b65f05cfc0bafa7621c1 | 0 | 75577e595d9177177a48030a1c39573af010df51 | d792dad1cf5f16525da81b1e162fb71d469995f3 | CONTRIBUTOR | 140912432 | https://github.com/simonw/sqlite-utils/pull/498 |
Links from other tables
- 0 rows from pull_requests_id in labels_pull_requests