{"html_url": "https://github.com/simonw/datasette/pull/603#issuecomment-548069706", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/603", "id": 548069706, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA2OTcwNg==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-30T19:12:21Z", "updated_at": "2019-10-30T19:12:21Z", "author_association": "OWNER", "body": "Shipped in 0.30.1 https://datasette.readthedocs.io/en/latest/changelog.html#v0-30-1", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 509612217, "label": "always pop as_format off args dict"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/604#issuecomment-548069859", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/604", "id": 548069859, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA2OTg1OQ==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-30T19:12:38Z", "updated_at": "2019-10-30T19:12:38Z", "author_association": "OWNER", "body": "Shipped in 0.30.1 https://datasette.readthedocs.io/en/latest/changelog.html#v0-30-1", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 509693773, "label": "_where= parameter is not persisted in hidden form fields"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/605#issuecomment-548056066", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/605", "id": 548056066, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA1NjA2Ng==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-30T18:38:54Z", "updated_at": "2019-10-30T18:38:54Z", "author_association": "OWNER", "body": "Could you flesh this out a little and help me understand what this might look like? If you define a query against a specific table in `metadata.json` where would you expect that query to be displayed in the Datasette UI?", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 510076368, "label": "Support queries at the table level"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/605#issuecomment-548058715", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/605", "id": 548058715, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA1ODcxNQ==", "user": {"value": 12617395, "label": "bsilverm"}, "created_at": "2019-10-30T18:44:41Z", "updated_at": "2019-10-30T18:55:37Z", "author_association": "NONE", "body": "Sure.  I imagine it being pretty straight forward.  Today when you click on the database, the UI displays:\r\n\r\n-Table 1-\r\n  -fields-\r\n  -row count-\r\n-Table 2-\r\n  -fields-\r\n  -row count-\r\nQueries:\r\n  -query1-\r\n  -query2-\r\n  ..\r\n  ...\r\n\r\nMy proposal would be to display as follows:\r\n\r\n-Table 1-\r\n  -fields-\r\n  -row count-\r\n  Queries:\r\n  -query1-\r\n  -query2-\r\n  ..\r\n  ...\r\n-Table 2-\r\n  -fields-\r\n  -row count-\r\n  Queries:\r\n  -query1-\r\n  -query2-\r\n  ..\r\n  ...\r\n\r\nThis way, if a given table is not present in the database, the associated queries are also not present.  Today, I have a list of queries, some work, some result in errors depending on whether the dependent tables exist in the database.\r\n\r\nLet me know if that makes sense.  Thanks again!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 510076368, "label": "Support queries at the table level"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/607#issuecomment-548055544", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/607", "id": 548055544, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA1NTU0NA==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-30T18:37:44Z", "updated_at": "2019-10-30T18:37:52Z", "author_association": "OWNER", "body": ".Hi @zeluspudding \r\n\r\nYou're running your search queries using the \"contains\" filter, which uses a `like` query under the hood.\r\n\r\nSQL `like` queries are generally slow because they force a full table scan. You can add an index on the column but it will only speed up prefix queries, like `... where name like 'apple%'` - they won't help if you are searching for text further along the string.\r\n\r\nInstead, you should take a look at SQLite's FTS - full text indexing feature. You can build a FTS index against a column and dramatically speed up searches for words within that column.\r\n\r\nThis documentation should help get you started: https://datasette.readthedocs.io/en/stable/full_text_search.html", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 512996469, "label": "Ways to improve fuzzy search speed on larger data sets?"}, "performed_via_github_app": null}
{"html_url": "https://github.com/simonw/datasette/issues/607#issuecomment-548060038", "issue_url": "https://api.github.com/repos/simonw/datasette/issues/607", "id": 548060038, "node_id": "MDEyOklzc3VlQ29tbWVudDU0ODA2MDAzOA==", "user": {"value": 8431341, "label": "zeluspudding"}, "created_at": "2019-10-30T18:47:57Z", "updated_at": "2019-10-30T18:47:57Z", "author_association": "NONE", "body": "Hi Simon, thanks for the pointer! Feeling good that I came to your conclusion a few days ago. I did hit a snag with figuring out how to compile a special version of sqlite for my windows machine (which I only realized I needed to do after running your command `sqlite-utils enable-fts mydatabase.db items name description`). \r\n\r\nI'll try to solve that problem next week and report back here with my findings (if you know of a good tutorial for compiling on windows, I'm all ears). Either way, I'll try to close this issue out in the next two weeks. Thanks again!", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 512996469, "label": "Ways to improve fuzzy search speed on larger data sets?"}, "performed_via_github_app": null}
{"html_url": "https://github.com/dogsheep/twitter-to-sqlite/issues/26#issuecomment-547713287", "issue_url": "https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/26", "id": 547713287, "node_id": "MDEyOklzc3VlQ29tbWVudDU0NzcxMzI4Nw==", "user": {"value": 9599, "label": "simonw"}, "created_at": "2019-10-30T02:36:13Z", "updated_at": "2019-10-30T02:36:13Z", "author_association": "MEMBER", "body": "Shipped this in 0.13: https://github.com/dogsheep/twitter-to-sqlite/releases/tag/0.13\r\n\r\nSee also this Twitter thread: https://twitter.com/simonw/status/1189369677509623809", "reactions": "{\"total_count\": 0, \"+1\": 0, \"-1\": 0, \"laugh\": 0, \"hooray\": 0, \"confused\": 0, \"heart\": 0, \"rocket\": 0, \"eyes\": 0}", "issue": {"value": 513074501, "label": "Command for importing mentions timeline"}, "performed_via_github_app": null}