html_url,issue_url,id,node_id,user,user_label,created_at,updated_at,author_association,body,reactions,issue,issue_label,performed_via_github_app
https://github.com/dogsheep/twitter-to-sqlite/issues/26#issuecomment-547713287,https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/26,547713287,MDEyOklzc3VlQ29tbWVudDU0NzcxMzI4Nw==,9599,simonw,2019-10-30T02:36:13Z,2019-10-30T02:36:13Z,MEMBER,"Shipped this in 0.13: https://github.com/dogsheep/twitter-to-sqlite/releases/tag/0.13
See also this Twitter thread: https://twitter.com/simonw/status/1189369677509623809","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",513074501,Command for importing mentions timeline,
https://github.com/simonw/datasette/issues/607#issuecomment-548055544,https://api.github.com/repos/simonw/datasette/issues/607,548055544,MDEyOklzc3VlQ29tbWVudDU0ODA1NTU0NA==,9599,simonw,2019-10-30T18:37:44Z,2019-10-30T18:37:52Z,OWNER,".Hi @zeluspudding
You're running your search queries using the ""contains"" filter, which uses a `like` query under the hood.
SQL `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.
Instead, 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.
This documentation should help get you started: https://datasette.readthedocs.io/en/stable/full_text_search.html","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",512996469,Ways to improve fuzzy search speed on larger data sets?,
https://github.com/simonw/datasette/issues/605#issuecomment-548056066,https://api.github.com/repos/simonw/datasette/issues/605,548056066,MDEyOklzc3VlQ29tbWVudDU0ODA1NjA2Ng==,9599,simonw,2019-10-30T18:38:54Z,2019-10-30T18:38:54Z,OWNER,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?,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",510076368,Support queries at the table level,
https://github.com/simonw/datasette/issues/605#issuecomment-548058715,https://api.github.com/repos/simonw/datasette/issues/605,548058715,MDEyOklzc3VlQ29tbWVudDU0ODA1ODcxNQ==,12617395,bsilverm,2019-10-30T18:44:41Z,2019-10-30T18:55:37Z,NONE,"Sure. I imagine it being pretty straight forward. Today when you click on the database, the UI displays:
-Table 1-
-fields-
-row count-
-Table 2-
-fields-
-row count-
Queries:
-query1-
-query2-
..
...
My proposal would be to display as follows:
-Table 1-
-fields-
-row count-
Queries:
-query1-
-query2-
..
...
-Table 2-
-fields-
-row count-
Queries:
-query1-
-query2-
..
...
This 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.
Let me know if that makes sense. Thanks again!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",510076368,Support queries at the table level,
https://github.com/simonw/datasette/issues/607#issuecomment-548060038,https://api.github.com/repos/simonw/datasette/issues/607,548060038,MDEyOklzc3VlQ29tbWVudDU0ODA2MDAzOA==,8431341,zeluspudding,2019-10-30T18:47:57Z,2019-10-30T18:47:57Z,NONE,"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`).
I'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!","{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",512996469,Ways to improve fuzzy search speed on larger data sets?,
https://github.com/simonw/datasette/pull/603#issuecomment-548069706,https://api.github.com/repos/simonw/datasette/issues/603,548069706,MDEyOklzc3VlQ29tbWVudDU0ODA2OTcwNg==,9599,simonw,2019-10-30T19:12:21Z,2019-10-30T19:12:21Z,OWNER,Shipped in 0.30.1 https://datasette.readthedocs.io/en/latest/changelog.html#v0-30-1,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",509612217,always pop as_format off args dict,
https://github.com/simonw/datasette/issues/604#issuecomment-548069859,https://api.github.com/repos/simonw/datasette/issues/604,548069859,MDEyOklzc3VlQ29tbWVudDU0ODA2OTg1OQ==,9599,simonw,2019-10-30T19:12:38Z,2019-10-30T19:12:38Z,OWNER,Shipped in 0.30.1 https://datasette.readthedocs.io/en/latest/changelog.html#v0-30-1,"{""total_count"": 0, ""+1"": 0, ""-1"": 0, ""laugh"": 0, ""hooray"": 0, ""confused"": 0, ""heart"": 0, ""rocket"": 0, ""eyes"": 0}",509693773,_where= parameter is not persisted in hidden form fields,