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/datasette/issues/651#issuecomment-568269476 | https://api.github.com/repos/simonw/datasette/issues/651 | 568269476 | MDEyOklzc3VlQ29tbWVudDU2ODI2OTQ3Ng== | 9599 | 2019-12-22T14:46:37Z | 2019-12-22T14:47:03Z | OWNER | https://stackoverflow.com/a/43756146 says that an escaping mechanism that works is this one: select * from blah where term match '"bacon" "and" "eggs"' So split on whitespace and then encapsulate each search term in double quotes. | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
539590148 | |
https://github.com/simonw/datasette/issues/651#issuecomment-568268746 | https://api.github.com/repos/simonw/datasette/issues/651 | 568268746 | MDEyOklzc3VlQ29tbWVudDU2ODI2ODc0Ng== | 9599 | 2019-12-22T14:37:37Z | 2019-12-22T14:37:37Z | OWNER | I've not yet been able to figure out what the escaping rule are for FTS5 queries. If we figure out how those work maybe we can bundle them as a custom function? select ... where docs_fts match fts_escape(:search) | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
539590148 |