github: issue_comments: 153 rows where reactions = "{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by id descending

153 rows where reactions = "{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}" sorted by id descending

Search:

descending

id ▲	html_url	issue_url	node_id	user	created_at	updated_at	author_association	body	reactions	issue
1105474232	https://github.com/dogsheep/github-to-sqlite/issues/72#issuecomment-1105474232	https://api.github.com/repos/dogsheep/github-to-sqlite/issues/72	IC_kwDODFdgUs5B5DK4	simonw 9599	2022-04-21T17:02:15Z	2022-04-21T17:02:15Z	MEMBER	That's interesting - yeah it looks like the number of pages can be derived from the `Link` header, which is enough information to show a progress bar, probably using Click just to avoid adding another dependency. https://docs.github.com/en/rest/guides/traversing-with-pagination	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	feature: display progress bar when downloading multi-page responses 1211283427
1098548931	https://github.com/simonw/sqlite-utils/issues/421#issuecomment-1098548931	https://api.github.com/repos/simonw/sqlite-utils/issues/421	IC_kwDOCGYnMM5BeobD	simonw 9599	2022-04-13T22:41:59Z	2022-04-13T22:41:59Z	OWNER	I'm going to close this ticket since it looks like this is a bug in the way the Dockerfile builds Python, but I'm going to ship a fix for that issue I found so the `LD_PRELOAD` workaround above should work OK with the next release of `sqlite-utils`. Thanks for the detailed bug report!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"Error: near "(": syntax error" when using sqlite-utils indexes CLI 1180427792
1082663746	https://github.com/simonw/datasette/issues/1692#issuecomment-1082663746	https://api.github.com/repos/simonw/datasette/issues/1692	IC_kwDOBm6k_c5AiCNC	simonw 9599	2022-03-30T06:14:39Z	2022-03-30T06:14:51Z	OWNER	I like your design, though I think it should be `"nomodule": True` for consistency with the other options. I think `"async": True` is worth supporting too.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	[plugins][feature request]: Support additional script tag attributes when loading custom JS 1182227211
1079582485	https://github.com/simonw/datasette/issues/1688#issuecomment-1079582485	https://api.github.com/repos/simonw/datasette/issues/1688	IC_kwDOBm6k_c5AWR8V	simonw 9599	2022-03-26T03:15:34Z	2022-03-26T03:15:34Z	OWNER	Yup, you're right in what you figured out here: stand-alone plugins can't currently package static assets other then using the static folder. The `datasette-plugin` cookiecutter template should make creating a Python package pretty easy though: https://github.com/simonw/datasette-plugin You can run that yourself, or you can run it using this GitHub template repository: https://github.com/simonw/datasette-plugin-template-repository	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	[plugins][documentation] Is it possible to serve per-plugin static folders when writing one-off (single file) plugins? 1181432624
1074019047	https://github.com/simonw/datasette/issues/526#issuecomment-1074019047	https://api.github.com/repos/simonw/datasette/issues/526	IC_kwDOBm6k_c5ABDrn	simonw 9599	2022-03-21T15:09:56Z	2022-03-21T15:09:56Z	OWNER	I should research how much overhead creating a new connection costs - it may be that an easy way to solve this is to create A dedicated connection for the query and then close that connection at the end.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Stream all results for arbitrary SQL and canned queries 459882902
1066222323	https://github.com/simonw/datasette/issues/1384#issuecomment-1066222323	https://api.github.com/repos/simonw/datasette/issues/1384	IC_kwDOBm6k_c4_jULz	brandonrobertz 2670795	2022-03-14T00:36:42Z	2022-03-14T00:36:42Z	CONTRIBUTOR	> Ah, sorry, I didn't get what you were saying you the first time. Using _metadata_local in that way makes total sense -- I agree, refreshing metadata each cell was seeming quite excessive. Now I'm on the same page! :) All good. Report back any issues you find with this stuff. Metadata/dynamic config hasn't been tested widely outside of what I've done AFAIK. If you find a strong use case for async meta, it's going to be better to know sooner rather than later!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Plugin hook for dynamic metadata 930807135
1059652834	https://github.com/simonw/sqlite-utils/issues/412#issuecomment-1059652834	https://api.github.com/repos/simonw/sqlite-utils/issues/412	IC_kwDOCGYnMM4_KQTi	zaneselvans 596279	2022-03-05T02:14:40Z	2022-03-05T02:14:40Z	NONE	We do a lot of `df.to_sql()` to write into sqlite, mostly in [this moddule](https://github.com/catalyst-cooperative/pudl/blob/main/src/pudl/load.py#L25)	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Optional Pandas integration 1160182768
1059650190	https://github.com/simonw/sqlite-utils/issues/412#issuecomment-1059650190	https://api.github.com/repos/simonw/sqlite-utils/issues/412	IC_kwDOCGYnMM4_KPqO	simonw 9599	2022-03-05T02:04:43Z	2022-03-05T02:04:54Z	OWNER	To be honest, I'm having second thoughts about this now mainly because the idiom for turning a generator of dicts into a DataFrame is SO simple: ```python df = pd.DataFrame(db.query("select * from articles")) ``` Given it's that simple, I'm questioning if there's any value to adding this to `sqlite-utils` at all. This likely becomes a documentation thing instead!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Optional Pandas integration 1160182768
1030740653	https://github.com/simonw/sqlite-utils/issues/399#issuecomment-1030740653	https://api.github.com/repos/simonw/sqlite-utils/issues/399	IC_kwDOCGYnMM49b9qt	eyeseast 25778	2022-02-06T02:57:17Z	2022-02-06T02:57:17Z	CONTRIBUTOR	I like the idea of having stock conversions you could import. I'd actually move them to a dedicated module (call it `sqlite_utils.conversions` or something), because it's different from other utilities. Maybe they even take configuration, or they're composable. ```python from sqlite_utils.conversions import LongitudeLatitude db["places"].insert( { "name": "London", "lng": -0.118092, "lat": 51.509865, }, conversions={"point": LongitudeLatitude("lng", "lat")}, ) ``` I would definitely use that for every CSV I get with lat/lng columns where I actually need GeoJSON.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Make it easier to insert geometries, with documentation and maybe code 1124731464
1029285985	https://github.com/simonw/sqlite-utils/pull/385#issuecomment-1029285985	https://api.github.com/repos/simonw/sqlite-utils/issues/385	IC_kwDOCGYnMM49Wahh	simonw 9599	2022-02-03T18:37:48Z	2022-02-03T18:37:48Z	OWNER	`from sqlite_utils.utils import find_spatialite` is part of the documented API already: https://sqlite-utils.datasette.io/en/3.22.1/python-api.html#finding-spatialite To avoid needing to bump the major version number to 4 to indicate a backwards incompatible change, we should keep a `from .gis import find_spatialite` line at the top of `utils.py` such that any existing code with that documented import continues to work.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Add new spatialite helper methods 1102899312
1017998993	https://github.com/simonw/datasette/issues/1608#issuecomment-1017998993	https://api.github.com/repos/simonw/datasette/issues/1608	IC_kwDOBm6k_c48rW6R	simonw 9599	2022-01-20T22:56:00Z	2022-01-20T22:56:00Z	OWNER	> https://sphinx-version-warning.readthedocs.io/ looks like it can show a banner for "You are looking at v0.36 but you should be looking at 0.40" but doesn't hand the case I need here which is "you are looking at /latest/ but you should be looking at /stable/". Correction! That tool DOES support that, as can be seen in their example configuration for their own documentation: https://github.com/humitos/sphinx-version-warning/blob/a82156c2ea08e5feab406514d0ccd9d48a345f48/docs/conf.py#L32-L38 ```python versionwarning_messages = { 'latest': 'This is a custom message only for version "latest" of this documentation.', } versionwarning_admonition_type = 'tip' versionwarning_banner_title = 'Tip' versionwarning_body_selector = 'div[itemprop="articleBody"]' ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Documentation should clarify /stable/ vs /latest/ 1109808154
995034143	https://github.com/simonw/datasette/issues/1552#issuecomment-995034143	https://api.github.com/repos/simonw/datasette/issues/1552	IC_kwDOBm6k_c47TwQf	simonw 9599	2021-12-15T18:02:53Z	2021-12-15T18:02:53Z	OWNER	This is definitely a missing feature. The "different types of facet" stuff feels incomplete to me generally - this is one issue, but this one as well: - #625	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Allow to set `facets_array` in metadata (like current `facets`) 1078702875
991754794	https://github.com/simonw/datasette/issues/1549#issuecomment-991754794	https://api.github.com/repos/simonw/datasette/issues/1549	IC_kwDOBm6k_c47HPoq	simonw 9599	2021-12-11T19:16:33Z	2021-12-11T19:16:33Z	OWNER	Good call! I'm doing a refactor #1518 right now which will hopefully bring the functionality of those two much closer - I'll make a note to consider this there too.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Redesign CSV export to improve usability 1077620955
991378346	https://github.com/simonw/sqlite-utils/issues/353#issuecomment-991378346	https://api.github.com/repos/simonw/sqlite-utils/issues/353	IC_kwDOCGYnMM47Fzuq	simonw 9599	2021-12-10T23:48:28Z	2021-12-10T23:48:28Z	OWNER	One option: allow `CODE` to be a special value of `-` which means "read from standard input". It's a tiny bit of a hack but I think it would work here. If you wanted to replace a column entirely with hyphens you would still be able to do this: sqlite-utils convert my.db mytable col1 '"-"'	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Allow passing a file of code to "sqlite-utils convert" 1077102934
981980048	https://github.com/simonw/datasette/issues/1304#issuecomment-981980048	https://api.github.com/repos/simonw/datasette/issues/1304	IC_kwDOBm6k_c46h9OQ	20after4 30934	2021-11-29T20:13:53Z	2021-11-29T20:14:11Z	NONE	There isn't any way to do this with sqlite as far as I know. The only option is to insert the right number of ? placeholders into the sql template and then provide an array of values.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Document how to send multiple values for "Named parameters" 863884805
976117989	https://github.com/simonw/datasette/issues/1522#issuecomment-976117989	https://api.github.com/repos/simonw/datasette/issues/1522	IC_kwDOBm6k_c46LmDl	glasnt 813732	2021-11-23T03:00:34Z	2021-11-23T03:00:34Z	CONTRIBUTOR	I tried deploying the most recent version of the Dockerfile in this thread ([link to comment](https://github.com/simonw/datasette/issues/1522#issuecomment-974605128)), and after trying a few different different combinations, I was only successful when I used `--no-cpu-throttling` ("CPU Is always allocated" in the UI) Using this method, I got a very similar issue to you: The first time I'd load the site I'd get a 503. But after that first load, I didn't get the issue again. It would re-occur if the service started from cold boot. I suspect this is a race condition in the supervisord configuration. The errors I got were the same `Connection refused: AH00957: http: attempt to connect to 127.0.0.1:8001 (127.0.0.1) failed`, and that seems to indicate that `datasette` hadn't yet started. Looking at the order of logs getting back, the processes reported successfully completing loading after the first 503 was returned, so that makes me think race condition. I can replicate this locally, if I `docker run` and request `localhost:5000/prefix` _before_ I get the `datasette entered RUNNING state` message. Cloud Run wakes up when requests are received, so this test would semi-replicate that, but local docker would be the equivalent of a persistent process, hence it doesn't normally exhibit the same issues. Unfortunately supervisor/supervisor issue 122 (not linking as to prevent cross-project link spam) seems to say that dependency chaining is a feature that's been asked for for a long time, but hasn't been implemented. You could try some suggestions in that thread.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Deploy a live instance of demos/apache-proxy 1058896236
962411119	https://github.com/simonw/sqlite-utils/issues/336#issuecomment-962411119	https://api.github.com/repos/simonw/sqlite-utils/issues/336	IC_kwDOCGYnMM45XTpv	simonw 9599	2021-11-06T07:21:04Z	2021-11-06T07:21:04Z	OWNER	I've never used `DEFAULT 'CURRENT_TIMESTAMP'` myself so this one should be an interesting bug to explore.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	sqlite-util tranform --column-order mangles columns of type "timestamp" 1044267332
949604763	https://github.com/simonw/datasette/issues/1284#issuecomment-949604763	https://api.github.com/repos/simonw/datasette/issues/1284	IC_kwDOBm6k_c44mdGb	fgregg 536941	2021-10-22T12:54:34Z	2021-10-22T12:54:34Z	NONE	i'm going to take a swing at this today. we'll see.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Feature or Documentation Request: Individual table as home page template 845794436
943594712	https://github.com/simonw/datasette/pull/1489#issuecomment-943594712	https://api.github.com/repos/simonw/datasette/issues/1489	IC_kwDOBm6k_c44PhzY	simonw 9599	2021-10-14T18:04:11Z	2021-10-14T18:04:11Z	OWNER	@dependabot recreate	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Update pyyaml requirement from ~=5.3 to >=5.3,<7.0 1026379132
942722595	https://github.com/simonw/datasette/pull/1487#issuecomment-942722595	https://api.github.com/repos/simonw/datasette/issues/1487	IC_kwDOBm6k_c44MM4j	simonw 9599	2021-10-13T21:08:53Z	2021-10-13T21:08:53Z	OWNER	Thanks for this!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Added instructions for installing plugins via pipx, #1486 1023245060
925321439	https://github.com/simonw/sqlite-utils/issues/325#issuecomment-925321439	https://api.github.com/repos/simonw/sqlite-utils/issues/325	IC_kwDOCGYnMM43J0jf	simonw 9599	2021-09-22T20:52:56Z	2021-09-22T20:52:56Z	OWNER	Updated documentation: https://sqlite-utils.datasette.io/en/latest/cli.html#running-queries-directly-against-csv-or-json > If two files have the same name they will be assigned a numeric suffix: > > $ sqlite-utils memory foo/data.csv bar/data.csv "select * from data_2"	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	sqlite-utils memory can't deal with multiple files with the same name 990844088
925296085	https://github.com/simonw/sqlite-utils/issues/328#issuecomment-925296085	https://api.github.com/repos/simonw/sqlite-utils/issues/328	IC_kwDOCGYnMM43JuXV	simonw 9599	2021-09-22T20:14:53Z	2021-09-22T20:14:53Z	OWNER	The bug is in this code: https://github.com/simonw/sqlite-utils/blob/77c240df56068341561e95e4a412cbfa24dc5bc7/sqlite_utils/cli.py#L2205-L2227	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Invalid JSON output when no rows 1004613267
913001416	https://github.com/simonw/datasette/pull/1455#issuecomment-913001416	https://api.github.com/repos/simonw/datasette/issues/1455	IC_kwDOBm6k_c42a0vI	simonw 9599	2021-09-04T16:32:21Z	2021-09-04T16:32:21Z	OWNER	I'll add researchers too.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Add scientists to target groups 988325628
913001282	https://github.com/simonw/datasette/pull/1455#issuecomment-913001282	https://api.github.com/repos/simonw/datasette/issues/1455	IC_kwDOBm6k_c42a0tC	ctb 51016	2021-09-04T16:31:24Z	2021-09-04T16:31:24Z	CONTRIBUTOR	I love it! maybe 'researchers' instead? Or 'scientists and researchers'?	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Add scientists to target groups 988325628
897996296	https://github.com/simonw/datasette/issues/942#issuecomment-897996296	https://api.github.com/repos/simonw/datasette/issues/942	IC_kwDOBm6k_c41hlYI	simonw 9599	2021-08-12T22:01:36Z	2021-08-12T22:01:36Z	OWNER	I'm going with `"columns": {"name-of-column": "description-of-column"}`. If I decide to make `"col"` and `"nocol"` available in metadata I'll use those as the keys in the metadata, for consistency with the existing query string parameters. I'm OK with having both `"columns": ...` and `"col": ...` keys in the metadata, even though they could be a tiny bit confusing without the documentation.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Support column descriptions in metadata.json 681334912
891359751	https://github.com/simonw/sqlite-utils/issues/298#issuecomment-891359751	https://api.github.com/repos/simonw/sqlite-utils/issues/298	IC_kwDOCGYnMM41IRIH	simonw 9599	2021-08-02T21:55:16Z	2021-08-02T21:55:16Z	OWNER	This is a feature already! You can do this: sqlite-utils insert nl-demo.db mytable data.ndjson --nl See https://sqlite-utils.datasette.io/en/stable/cli.html#inserting-newline-delimited-json	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Read lines with JSON object 951581763
880326049	https://github.com/simonw/datasette/issues/1396#issuecomment-880326049	https://api.github.com/repos/simonw/datasette/issues/1396	MDEyOklzc3VlQ29tbWVudDg4MDMyNjA0OQ==	simonw 9599	2021-07-15T01:50:05Z	2021-07-15T01:50:05Z	OWNER	I think I made a mistake in this commit: https://github.com/simonw/datasette/commit/0486303b60ce2784fd2e2ecdbecf304b7d6e6659 <img width="770" alt="Explicitly_push_version_tag__refs__1281_·_simonw_datasette_0486303" src="https://user-images.githubusercontent.com/9599/125715241-dc96d147-191a-4a69-bdf0-1cb092d97330.png"> It looks like I copied `$VERSION_TAG` from here - but it's not available in the `publish.yml` flow: https://github.com/simonw/datasette/blob/0486303b60ce2784fd2e2ecdbecf304b7d6e6659/.github/workflows/push_docker_tag.yml#L18-L25	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"invalid reference format" publishing Docker image 944903881
875738149	https://github.com/simonw/datasette/issues/1388#issuecomment-875738149	https://api.github.com/repos/simonw/datasette/issues/1388	MDEyOklzc3VlQ29tbWVudDg3NTczODE0OQ==	simonw 9599	2021-07-07T16:14:29Z	2021-07-07T16:14:29Z	OWNER	This sounds like a valuable feature for people running Datasette behind a proxy.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Serve using UNIX domain socket 939051549
864128489	https://github.com/simonw/sqlite-utils/issues/278#issuecomment-864128489	https://api.github.com/repos/simonw/sqlite-utils/issues/278	MDEyOklzc3VlQ29tbWVudDg2NDEyODQ4OQ==	simonw 9599	2021-06-18T15:46:24Z	2021-06-18T15:46:24Z	OWNER	A workaround could be to define a bash or zsh alias of some sort.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Support db as first parameter before subcommand, or as environment variable 923697888
861987651	https://github.com/simonw/sqlite-utils/issues/272#issuecomment-861987651	https://api.github.com/repos/simonw/sqlite-utils/issues/272	MDEyOklzc3VlQ29tbWVudDg2MTk4NzY1MQ==	simonw 9599	2021-06-16T02:27:20Z	2021-06-16T02:27:20Z	OWNER	Solution: `sqlite-utils memory -` attempts to detect the input based on if it starts with a `{` or `[` (likely JSON) or if it doesn't use the `csv.Sniffer()` mechanism. Or you can use `sqlite-utils memory -:csv` to specifically indicate the type of input.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Idea: import CSV to memory, run SQL, export in a single command 921878733
860548546	https://github.com/simonw/datasette/issues/1375#issuecomment-860548546	https://api.github.com/repos/simonw/datasette/issues/1375	MDEyOklzc3VlQ29tbWVudDg2MDU0ODU0Ng==	frafra 4068	2021-06-14T09:41:59Z	2021-06-14T09:41:59Z	NONE	> There is a feature for this at the moment, but it's a little bit hidden: you can use `?_json=col` to tell > Datasette that you would like a specific column to be exported as nested JSON: https://docs.datasette.io/en/stable/json_api.html#special-json-arguments Thanks :) > I considered trying to make this automatic - so it detects columns that appear to contain valid JSON and outputs them as nested objects - but the problem with that is that it can lead to inconsistent results - you might hit the API and find that not every column contains valid JSON (compared to the previous day) resulting in the API retuning string instead of the expected dictionary and breaking your code. If a developer is not sure if the JSON fields are valid, but then retrieves and parse them, it should handle errors too. Handling inconsistent data is necessary due to the nature of SQLite. A global or dataset option to render the data as they have been defined (JSON, boolean, etc.) when requesting JSON could allow the user to download a regular JSON from the browser without having to rely on APIs. I would guess someone could just make a custom template with an extra JSON-parsed download button otherwise :)	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	JSON export dumps JSON fields as TEXT 919508498
860230385	https://github.com/simonw/datasette/issues/1375#issuecomment-860230385	https://api.github.com/repos/simonw/datasette/issues/1375	MDEyOklzc3VlQ29tbWVudDg2MDIzMDM4NQ==	simonw 9599	2021-06-13T15:37:49Z	2021-06-13T15:37:49Z	OWNER	There is a feature for this at the moment, but it's a little bit hidden: you can use `?_json=col` to tell Datasette that you would like a specific column to be exported as nested JSON: https://docs.datasette.io/en/stable/json_api.html#special-json-arguments I considered trying to make this automatic - so it detects columns that appear to contain valid JSON and outputs them as nested objects - but the problem with that is that it can lead to inconsistent results - you might hit the API and find that not every column contains valid JSON (compared to the previous day) resulting in the API retuning string instead of the expected dictionary and breaking your code.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	JSON export dumps JSON fields as TEXT 919508498
853567861	https://github.com/simonw/sqlite-utils/issues/264#issuecomment-853567861	https://api.github.com/repos/simonw/sqlite-utils/issues/264	MDEyOklzc3VlQ29tbWVudDg1MzU2Nzg2MQ==	simonw 9599	2021-06-03T05:12:21Z	2021-06-03T05:12:21Z	OWNER	I think this is more likely to happen in Datasette than in sqlite-utils - see https://github.com/simonw/datasette/issues/1356 for thoughts on this.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Supporting additional output formats, like GeoJSON 907642546
853567413	https://github.com/simonw/datasette/issues/526#issuecomment-853567413	https://api.github.com/repos/simonw/datasette/issues/526	MDEyOklzc3VlQ29tbWVudDg1MzU2NzQxMw==	simonw 9599	2021-06-03T05:11:27Z	2021-06-03T05:11:27Z	OWNER	Another potential way to implement this would be to hold the SQLite connection open and execute the full query there. I've avoided this in the past due to concerns of resource exhaustion - if multiple requests attempt this at the same time all of the connections in the pool will become tied up and the site will be unable to respond to further requests. But... now that Datasette has authentication there's the possibility of making this feature only available to specific authenticated users - the `--root` user for example. Which avoids the danger while unlocking a super-useful feature. Not to mention people who are running Datasette privately on their own laptop, or the proposed `--query` CLI feature in #1356.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Stream all results for arbitrary SQL and canned queries 459882902
852673695	https://github.com/simonw/datasette/pull/1352#issuecomment-852673695	https://api.github.com/repos/simonw/datasette/issues/1352	MDEyOklzc3VlQ29tbWVudDg1MjY3MzY5NQ==	simonw 9599	2021-06-02T02:52:26Z	2021-06-02T02:52:26Z	OWNER	@dependabot recreate	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Bump black from 21.5b1 to 21.5b2 908276134
843718859	https://github.com/simonw/sqlite-utils/issues/253#issuecomment-843718859	https://api.github.com/repos/simonw/sqlite-utils/issues/253	MDEyOklzc3VlQ29tbWVudDg0MzcxODg1OQ==	simonw 9599	2021-05-19T03:31:47Z	2021-05-19T03:31:47Z	OWNER	Fixed: https://simonwillison.net/2020/Sep/23/sqlite-advanced-alter-table/	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	fixtures.db example error in sql-utils blog post 847423559
843702392	https://github.com/simonw/sqlite-utils/pull/258#issuecomment-843702392	https://api.github.com/repos/simonw/sqlite-utils/issues/258	MDEyOklzc3VlQ29tbWVudDg0MzcwMjM5Mg==	simonw 9599	2021-05-19T02:47:37Z	2021-05-19T02:47:37Z	OWNER	I'm going to merge this and add a test - thanks!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Fixing insert from JSON containing strings with non-ascii characters … 868191959
815978405	https://github.com/simonw/datasette/issues/1286#issuecomment-815978405	https://api.github.com/repos/simonw/datasette/issues/1286	MDEyOklzc3VlQ29tbWVudDgxNTk3ODQwNQ==	mroswell 192568	2021-04-08T16:47:29Z	2021-04-10T03:59:00Z	CONTRIBUTOR	This worked for me: `<td class="col-{{ cell.column\|to_css_class }} type-{{ cell.value_type }}">{{ cell.value \| replace('", "','; ') \| replace('[\"','') \| replace('\"]','')}}</td>` I'm sure there is a prettier (and more flexible) way, but for now, this is ever-so-much more pleasant to look at. ------ AFTER: <img width="778" alt="Screen Shot 2021-04-08 at 12 27 36 PM" src="https://user-images.githubusercontent.com/192568/114062829-f2f20c00-9865-11eb-891d-b0c348a9b433.png"> ------ BEFORE: <img width="795" alt="Screen Shot 2021-04-08 at 12 25 54 PM" src="https://user-images.githubusercontent.com/192568/114062871-01402800-9866-11eb-91ce-91efe4ee45cd.png"> (Note: I didn't figure out how to have one item have no semicolon, while multi-items close with a semicolon, but this is good enough for now. I also didn't figure out how to set up a new jinja filter. I don't want to add to /datasette/utils/__init__.py as I assume that would get overwritten when upgrading datasette. Having a starter guide on creating jinja filters in datasette would be helpful. (The jinja documentation isn't datasette-specific enough for me to quite nail it.)	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Better default display of arrays of items 849220154
812710120	https://github.com/simonw/datasette/issues/1255#issuecomment-812710120	https://api.github.com/repos/simonw/datasette/issues/1255	MDEyOklzc3VlQ29tbWVudDgxMjcxMDEyMA==	jungle-boogie 1111743	2021-04-02T20:50:08Z	2021-04-02T20:50:08Z	NONE	Hello again, I was able to get my facets running with this `settings.json`, which was lifted from one of Simon's datasette's and slightly modified. ``` { "default_page_size": 100, "max_returned_rows": 1000, "num_sql_threads": 3, "sql_time_limit_ms": 9000, "default_facet_size": 10, "facet_time_limit_ms": 9000, "facet_suggest_time_limit_ms": 500, "hash_urls": false, "allow_facet": true, "suggest_facets": false, "default_cache_ttl": 5, "default_cache_ttl_hashed": 31536000, "cache_size_kb": 0, "allow_csv_stream": true, "max_csv_mb": 100, "truncate_cells_html": 2048, "template_debug": false, "base_url": "/" } ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Facets timing out but work when filtering 826700095
812664443	https://github.com/simonw/datasette/issues/1286#issuecomment-812664443	https://api.github.com/repos/simonw/datasette/issues/1286	MDEyOklzc3VlQ29tbWVudDgxMjY2NDQ0Mw==	simonw 9599	2021-04-02T18:52:45Z	2021-04-02T18:52:51Z	OWNER	Idea: default to displaying single-dimension JSON arrays of strings as a comma-separated list but show the comma in a different colour - something like this: <img width="561" alt="fixtures__facetable__15_rows" src="https://user-images.githubusercontent.com/9599/113445005-dce9d480-93a9-11eb-901c-0c2fb079c150.png"> I used this HTML for the prototype (re-using `.type-int` just to get the colour): ```html <td class="col-tags type-str">tag1<span class="type-int">, </span>tag2</td> ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Better default display of arrays of items 849220154
810740486	https://github.com/simonw/datasette/issues/1284#issuecomment-810740486	https://api.github.com/repos/simonw/datasette/issues/1284	MDEyOklzc3VlQ29tbWVudDgxMDc0MDQ4Ng==	simonw 9599	2021-03-31T03:57:55Z	2021-03-31T03:57:55Z	OWNER	You're right, doing this is really hard at the moment - I'm not sure I know how I would tackle this either, and it's something I've wanted in the past! I'll have a think about this one.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Feature or Documentation Request: Individual table as home page template 845794436
809548363	https://github.com/simonw/datasette/issues/696#issuecomment-809548363	https://api.github.com/repos/simonw/datasette/issues/696	MDEyOklzc3VlQ29tbWVudDgwOTU0ODM2Mw==	simonw 9599	2021-03-29T17:04:19Z	2021-03-29T17:04:19Z	OWNER	I tried this just now against Datasette 0.56 with the new Dockerfile from #1249 (that uses SQLite and SpatiaLite installed with `apt-get install`) and the tests all passed.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Single failing unit test when run inside the Docker image 576722115
809010713	https://github.com/simonw/datasette/pull/1031#issuecomment-809010713	https://api.github.com/repos/simonw/datasette/issues/1031	MDEyOklzc3VlQ29tbWVudDgwOTAxMDcxMw==	simonw 9599	2021-03-29T01:46:45Z	2021-03-29T01:46:45Z	OWNER	Sorry I didn't get to this PR sooner. I've joint-credited you in the release notes for this fix: https://docs.datasette.io/en/stable/changelog.html#v0-56	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Fallback to databases in inspect-data.json when no -i options are passed 724369025
808988697	https://github.com/simonw/datasette/pull/1260#issuecomment-808988697	https://api.github.com/repos/simonw/datasette/issues/1260	MDEyOklzc3VlQ29tbWVudDgwODk4ODY5Nw==	simonw 9599	2021-03-29T00:22:21Z	2021-03-29T00:22:21Z	OWNER	This is interesting! I've decided to apply a subset of these - the `if` and `elif` blocks are a deliberate style choice from me, because I find code clearer when it has if/else as opposed to relying on early termination. Likewise the iteration against `.keys()` on dictionaries. I like the other fixes though, I'm about to land them in a separate commit that credits you.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Fix: code quality issues 831163537
808651088	https://github.com/simonw/datasette/issues/1258#issuecomment-808651088	https://api.github.com/repos/simonw/datasette/issues/1258	MDEyOklzc3VlQ29tbWVudDgwODY1MTA4OA==	simonw 9599	2021-03-27T04:41:52Z	2021-03-27T04:42:14Z	OWNER	Right now they look like this: ```yaml databases: fixtures: queries: neighborhood_search: params: - text ``` In addition to being able to specify defaults, I'd also like to add other things in the future - most significantly the ability to specify a different input widget (e.g. textarea v.s. single-line input) So maybe this looks like: ```yaml params: - name: text default: "" - name: age widget: number ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Allow canned query params to specify default values 828858421
805214307	https://github.com/simonw/datasette/issues/1274#issuecomment-805214307	https://api.github.com/repos/simonw/datasette/issues/1274	MDEyOklzc3VlQ29tbWVudDgwNTIxNDMwNw==	bobwhitelock 7476523	2021-03-23T20:12:29Z	2021-03-23T20:12:29Z	CONTRIBUTOR	One issue I could see with adding first class support for metadata in hjson format is that this would require adding an additional dependency to handle this, for a feature that would be unused by many users. I wonder if this could fit in as a plugin instead; if a hook existed for loading metadata (maybe as part of https://github.com/simonw/datasette/issues/860) the metadata could then come from any source, as specified by plugins, e.g. hjson, toml, XML, a database table etc. Until/unless this exists, a few ideas for how you could add comments: - Using YAML as you suggest. - A common pattern is adding a `"comment"` key for comments to any object in JSON - I don't think including an unnecessary key like this would break anything in Datasette, but not certain. - You could use another tool as a preprocessor for your JSON metadata - e.g. hjson or Jsonnet. You'd write the metadata in that format, and then convert that into JSON to actually use as your final metadata.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Might there be some way to comment metadata.json? 839008371
805109341	https://github.com/simonw/datasette/issues/1153#issuecomment-805109341	https://api.github.com/repos/simonw/datasette/issues/1153	MDEyOklzc3VlQ29tbWVudDgwNTEwOTM0MQ==	simonw 9599	2021-03-23T17:55:48Z	2021-03-23T18:41:57Z	OWNER	Beginnings of a UI element for switching between them: ```html <div style="border: 1px solid rgb(225, 228, 229); background-color: rgb(238, 255, 204); padding: 0.3em; position: relative; top: 3px; font-family: courier;"> <a href="#" style="display: inline-block; padding-left: 0px; padding-right: 2em;">JSON</a> <a href="#" style="display: inline-block;">YAML</a> </div> ``` <img width="646" alt="Metadata_—_Datasette_documentation" src="https://user-images.githubusercontent.com/9599/112194637-51f92500-8bc6-11eb-9662-3faa7ef37538.png"> That `<pre>` has a padding of 12px, so using 12px padding on the tab links should get them to line up better.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Use YAML examples in documentation by default, not JSON 771202454
803501756	https://github.com/simonw/sqlite-utils/issues/249#issuecomment-803501756	https://api.github.com/repos/simonw/sqlite-utils/issues/249	MDEyOklzc3VlQ29tbWVudDgwMzUwMTc1Ng==	simonw 9599	2021-03-21T02:33:45Z	2021-03-21T02:33:45Z	OWNER	Did you run `enable-fts` before you inserted the data? If so you'll need to run `populate-fts` after the insert to populate the FTS index. A better solution may be to add `--create-triggers` to the `enable-fts` command to add triggers that will automatically keep the index updated as you insert new records.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Full text search possibly broken? 836963850
795895436	https://github.com/simonw/datasette/issues/838#issuecomment-795895436	https://api.github.com/repos/simonw/datasette/issues/838	MDEyOklzc3VlQ29tbWVudDc5NTg5NTQzNg==	simonw 9599	2021-03-10T18:44:46Z	2021-03-10T18:44:57Z	OWNER	Let's reopen this.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Incorrect URLs when served behind a proxy with base_url set 637395097
790857004	https://github.com/simonw/datasette/issues/1238#issuecomment-790857004	https://api.github.com/repos/simonw/datasette/issues/1238	MDEyOklzc3VlQ29tbWVudDc5MDg1NzAwNA==	tsibley 79913	2021-03-04T19:06:55Z	2021-03-04T19:06:55Z	NONE	@rgieseke Ah, that's super helpful. Thank you for the workaround for now!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Custom pages don't work with base_url setting 813899472
790389335	https://github.com/dogsheep/google-takeout-to-sqlite/pull/5#issuecomment-790389335	https://api.github.com/repos/dogsheep/google-takeout-to-sqlite/issues/5	MDEyOklzc3VlQ29tbWVudDc5MDM4OTMzNQ==	UtahDave 306240	2021-03-04T07:32:04Z	2021-03-04T07:32:04Z	NONE	> The command takes quite a while to start running, presumably because this line causes it to have to scan the WHOLE file in order to generate a count: > > https://github.com/dogsheep/google-takeout-to-sqlite/blob/a3de045eba0fae4b309da21aa3119102b0efc576/google_takeout_to_sqlite/utils.py#L66-L67 > > I'm fine with waiting though. It's not like this is a command people run every day - and without that count we can't show a progress bar, which seems pretty important for a process that takes this long. The wait is from python loading the mbox file. This happens regardless if you're getting the length of the mbox. The mbox module is on the slow side. It is possible to do one's own parsing of the mbox, but I kind of wanted to avoid doing that.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	WIP: Add Gmail takeout mbox import 813880401
790198930	https://github.com/dogsheep/google-takeout-to-sqlite/issues/4#issuecomment-790198930	https://api.github.com/repos/dogsheep/google-takeout-to-sqlite/issues/4	MDEyOklzc3VlQ29tbWVudDc5MDE5ODkzMA==	Btibert3 203343	2021-03-04T00:58:40Z	2021-03-04T00:58:40Z	NONE	I am just seeing this sorry, yes! I will kick the tires later on tonight. My apologies for the delay.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Feature Request: Gmail 778380836
786925280	https://github.com/dogsheep/google-takeout-to-sqlite/pull/5#issuecomment-786925280	https://api.github.com/repos/dogsheep/google-takeout-to-sqlite/issues/5	MDEyOklzc3VlQ29tbWVudDc4NjkyNTI4MA==	simonw 9599	2021-02-26T22:23:10Z	2021-02-26T22:23:10Z	MEMBER	Thanks! I requested my Gmail export from takeout - once that arrives I'll test it against this and then merge the PR.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	WIP: Add Gmail takeout mbox import 813880401
784567547	https://github.com/simonw/datasette/issues/1241#issuecomment-784567547	https://api.github.com/repos/simonw/datasette/issues/1241	MDEyOklzc3VlQ29tbWVudDc4NDU2NzU0Nw==	simonw 9599	2021-02-23T22:45:56Z	2021-02-23T22:46:12Z	OWNER	I really like the way the Share feature on Stack Overflow works: https://stackoverflow.com/questions/18934149/how-can-i-use-postgresqls-text-column-type-in-django	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Share button for copying current URL 814595021
782789598	https://github.com/simonw/datasette/issues/782#issuecomment-782789598	https://api.github.com/repos/simonw/datasette/issues/782	MDEyOklzc3VlQ29tbWVudDc4Mjc4OTU5OA==	simonw 9599	2021-02-21T03:30:02Z	2021-02-21T03:30:02Z	OWNER	Another benefit to default:object - I could include a key that shows a list of available extras. I could then use that to power an interactive API explorer.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Redesign default .json format 627794879
778510528	https://github.com/simonw/sqlite-utils/issues/131#issuecomment-778510528	https://api.github.com/repos/simonw/sqlite-utils/issues/131	MDEyOklzc3VlQ29tbWVudDc3ODUxMDUyOA==	simonw 9599	2021-02-12T23:25:06Z	2021-02-12T23:25:06Z	OWNER	If `-c` isn't available, maybe `-t` or `--type` would work for specifying column types: ``` sqlite-utils insert db.db images images.tsv \ --tsv \ --type id int \ --type score float ``` or ``` sqlite-utils insert db.db images images.tsv \ --tsv \ -t id int \ -t score float ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	sqlite-utils insert: options for column types 675753042
778467759	https://github.com/simonw/datasette/issues/1220#issuecomment-778467759	https://api.github.com/repos/simonw/datasette/issues/1220	MDEyOklzc3VlQ29tbWVudDc3ODQ2Nzc1OQ==	aborruso 30607	2021-02-12T21:35:17Z	2021-02-12T21:35:17Z	NONE	Thank you	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Installing datasette via docker: Path 'fixtures.db' does not exist 806743116
777798330	https://github.com/dogsheep/evernote-to-sqlite/issues/11#issuecomment-777798330	https://api.github.com/repos/dogsheep/evernote-to-sqlite/issues/11	MDEyOklzc3VlQ29tbWVudDc3Nzc5ODMzMA==	simonw 9599	2021-02-11T21:18:58Z	2021-02-11T21:18:58Z	MEMBER	Thanks for the fix!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	XML parse error 792851444
777178728	https://github.com/simonw/datasette/issues/1200#issuecomment-777178728	https://api.github.com/repos/simonw/datasette/issues/1200	MDEyOklzc3VlQ29tbWVudDc3NzE3ODcyOA==	simonw 9599	2021-02-11T03:13:59Z	2021-02-11T03:13:59Z	OWNER	I came up with the need for this while playing with this tool: https://calands.datasettes.com/calands?sql=select%0D%0A++AsGeoJSON(geometry)%2C+*%0D%0Afrom%0D%0A++CPAD_2020a_SuperUnits%0D%0Awhere%0D%0A++PARK_NAME+like+'%25mini%25'+and%0D%0A++Intersects(GeomFromGeoJSON(%3Afreedraw)%2C+geometry)+%3D+1%0D%0A++and+CPAD_2020a_SuperUnits.rowid+in+(%0D%0A++++select%0D%0A++++++rowid%0D%0A++++from%0D%0A++++++SpatialIndex%0D%0A++++where%0D%0A++++++f_table_name+%3D+'CPAD_2020a_SuperUnits'%0D%0A++++++and+search_frame+%3D+GeomFromGeoJSON(%3Afreedraw)%0D%0A++)&freedraw={"type"%3A"MultiPolygon"%2C"coordinates"%3A[[[[-122.42202758789064%2C37.82280243352759]%2C[-122.39868164062501%2C37.823887203271454]%2C[-122.38220214843751%2C37.81846319511331]%2C[-122.35061645507814%2C37.77071473849611]%2C[-122.34924316406251%2C37.74465712069939]%2C[-122.37258911132814%2C37.703380457832374]%2C[-122.39044189453125%2C37.690340943717715]%2C[-122.41241455078126%2C37.680559803205135]%2C[-122.44262695312501%2C37.67295135774715]%2C[-122.47283935546876%2C37.67295135774715]%2C[-122.52502441406251%2C37.68382032669382]%2C[-122.53463745117189%2C37.6892542140253]%2C[-122.54699707031251%2C37.690340943717715]%2C[-122.55798339843751%2C37.72945260537781]%2C[-122.54287719726564%2C37.77831314799672]%2C[-122.49893188476564%2C37.81303878836991]%2C[-122.46185302734376%2C37.82822612280363]%2C[-122.42889404296876%2C37.82822612280363]%2C[-122.42202758789064%2C37.82280243352759]]]]} - before I fixed https://github.com/simonw/datasette-leaflet-geojson/issues/16 it was loading a LOT of maps, which felt bad. I wanted to be able to link people to that page with a hard limit on the number of rows displayed on that page. It's mainly to guard against unexpected behaviour from limit-less queries though. It's not a very high priority feature!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	?_size=10 option for the arbitrary query page would be useful 792890765
774385092	https://github.com/simonw/datasette/issues/1217#issuecomment-774385092	https://api.github.com/repos/simonw/datasette/issues/1217	MDEyOklzc3VlQ29tbWVudDc3NDM4NTA5Mg==	plpxsk 6165713	2021-02-06T02:49:11Z	2021-02-06T02:49:11Z	NONE	A good reference seems to be the note to run `datasette` as a module in https://github.com/simonw/datasette/pull/556	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Possible to deploy as a python app (for Rstudio connect server)? 802513359
770071568	https://github.com/dogsheep/github-to-sqlite/issues/60#issuecomment-770071568	https://api.github.com/repos/dogsheep/github-to-sqlite/issues/60	MDEyOklzc3VlQ29tbWVudDc3MDA3MTU2OA==	simonw 9599	2021-01-29T21:56:15Z	2021-01-29T21:56:15Z	MEMBER	I really like the way you're using pipes here - really smart. It's similar to how I build the demo database in this GitHub Actions workflow: https://github.com/dogsheep/github-to-sqlite/blob/62dfd3bc4014b108200001ef4bc746feb6f33b45/.github/workflows/deploy-demo.yml#L52-L82 `twitter-to-sqlite` actually has a mechanism for doing this kind of thing, documented at https://github.com/dogsheep/twitter-to-sqlite#providing-input-from-a-sql-query-with---sql-and---attach It lets you do things like: ``` $ twitter-to-sqlite users-lookup my.db --sql="select follower_id from following" --ids ``` Maybe I should add something similar to `github-to-sqlite`? Feels like it could be really useful.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Use Data from SQLite in other commands 797097140
769455370	https://github.com/simonw/datasette/issues/1209#issuecomment-769455370	https://api.github.com/repos/simonw/datasette/issues/1209	MDEyOklzc3VlQ29tbWVudDc2OTQ1NTM3MA==	simonw 9599	2021-01-28T23:00:21Z	2021-01-28T23:00:21Z	OWNER	Good catch on the workaround here. The root problem is that `datasette-template-sql` looks for the first available databsae if you don't provide it with a `database=` argument, and in Datasette 0.54 the first available database changed to being the new `_internal` database. Is this a bug? I think it is - because the documented behaviour on https://docs.datasette.io/en/stable/internals.html#get-database-name is this: > `name` - string, optional > > The name to be used for this database - this will be used in the URL path, e.g. `/dbname`. If not specified Datasette will pick one based on the filename or memory name. Since the new behaviour differs from what was in the documentation I'm going to treat this as a bug and fix it.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	v0.54 500 error from sql query in custom template; code worked in v0.53; found a workaround 795367402
761015218	https://github.com/simonw/sqlite-utils/issues/220#issuecomment-761015218	https://api.github.com/repos/simonw/sqlite-utils/issues/220	MDEyOklzc3VlQ29tbWVudDc2MTAxNTIxOA==	mhalle 649467	2021-01-15T15:40:08Z	2021-01-15T15:40:08Z	NONE	Make sense. If you're coming from the sqlite3 side of things, rather than the datasette side, wanting the fts methods to work for views makes more sense. sqlite3 allows fts5 tables on views, so I was looking for CLI functionality to build the fts virtual tables. Ultimately, though, sharing fts virtual tables across tables and derivative views is likely more efficient. Maybe an explicit error message like, "fts is not supported for views" rather than just throwing an exception that the method doesn't exist" might be helpful. Not critical though. Thanks.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Better error message for _fts methods against views 783778672*
754215392	https://github.com/simonw/datasette/issues/93#issuecomment-754215392	https://api.github.com/repos/simonw/datasette/issues/93	MDEyOklzc3VlQ29tbWVudDc1NDIxNTM5Mg==	simonw 9599	2021-01-04T20:59:20Z	2021-01-04T21:03:14Z	OWNER	Updated `pyinstaller` recipe - lots of hidden imports needed now: ``` pip install wheel pip install datasette pyinstaller BASE=$(python -c 'import os; print(os.path.dirname(__import__("datasette").__file__))') \ pyinstaller -F \ --add-data "$BASE/templates:datasette/templates" \ --add-data "$BASE/static:datasette/static" \ --hidden-import datasette.publish \ --hidden-import datasette.publish.heroku \ --hidden-import datasette.publish.cloudrun \ --hidden-import datasette.facets \ --hidden-import datasette.sql_functions \ --hidden-import datasette.actor_auth_cookie \ --hidden-import datasette.default_permissions \ --hidden-import datasette.default_magic_parameters \ --hidden-import datasette.blob_renderer \ --hidden-import datasette.default_menu_links \ --hidden-import uvicorn \ --hidden-import uvicorn.logging \ --hidden-import uvicorn.loops \ --hidden-import uvicorn.loops.auto \ --hidden-import uvicorn.protocols \ --hidden-import uvicorn.protocols.http \ --hidden-import uvicorn.protocols.http.auto \ --hidden-import uvicorn.protocols.websockets \ --hidden-import uvicorn.protocols.websockets.auto \ --hidden-import uvicorn.lifespan \ --hidden-import uvicorn.lifespan.on \ $(which datasette) ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Package as standalone binary 273944952
754187326	https://github.com/simonw/datasette/issues/913#issuecomment-754187326	https://api.github.com/repos/simonw/datasette/issues/913	MDEyOklzc3VlQ29tbWVudDc1NDE4NzMyNg==	simonw 9599	2021-01-04T20:03:50Z	2021-01-04T20:03:50Z	OWNER	I renamed `--config` to `--setting` and changed it to work like this: datasette --setting sql_time_limit_ms 1000 Note the lack of colons. This actually makes colons cleaner to use for plugins - I could support this: datasette --setting datasette-insert:unsafe 1	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Mechanism for passing additional options to `datasette my.db` that affect plugins 670209331
753653260	https://github.com/simonw/datasette/issues/1169#issuecomment-753653260	https://api.github.com/repos/simonw/datasette/issues/1169	MDEyOklzc3VlQ29tbWVudDc1MzY1MzI2MA==	simonw 9599	2021-01-03T17:54:40Z	2021-01-03T17:54:40Z	OWNER	And @benpickles yes I would land that pull request straight away as-is. Thanks!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Prettier package not actually being cached 777677671
752714747	https://github.com/simonw/datasette/issues/987#issuecomment-752714747	https://api.github.com/repos/simonw/datasette/issues/987	MDEyOklzc3VlQ29tbWVudDc1MjcxNDc0Nw==	simonw 9599	2020-12-30T18:23:08Z	2020-12-30T18:23:20Z	OWNER	In terms of "places to put your plugin content", the simplest solution I can think of is something like this: ```html <div id="plugin-content-pre-table"></div> ``` Alternative designs: - A documented JavaScript function that returns the CSS selector where plugins should put their content - A documented JavaScript function that returns a DOM node where plugins should put their content. This would allow the JavaScript to create the element if it does not already exist (though it wouldn't be obvious WHERE that element should be created) - Documented JavaScript functions for things like "append this node/HTML to the place-where-plugins-go" I think the original option - an empty `<div>` with a known `id` attribute - is the right one to go with here. It's the simplest, it's very easy for custom template authors to understand and it acknowledges that plugins may have all kinds of extra crazy stuff they want to do - like checking in that div to see if another plugin has written to it already, for example.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Documented HTML hooks for JavaScript plugin authors 712984738
750390741	https://github.com/simonw/datasette/pull/1158#issuecomment-750390741	https://api.github.com/repos/simonw/datasette/issues/1158	MDEyOklzc3VlQ29tbWVudDc1MDM5MDc0MQ==	simonw 9599	2020-12-23T17:05:32Z	2020-12-23T17:05:32Z	OWNER	Thanks for this! I'm fine keeping the `os.path` stuff as is.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Modernize code to Python 3.6+ 773913793
747207787	https://github.com/simonw/datasette/issues/1149#issuecomment-747207787	https://api.github.com/repos/simonw/datasette/issues/1149	MDEyOklzc3VlQ29tbWVudDc0NzIwNzc4Nw==	simonw 9599	2020-12-17T05:06:16Z	2020-12-17T05:06:16Z	OWNER	So, an idea: what if Datasette's default CSS applied only to elements with classes - or maybe to childen of a `body class="datasette"` element? In such a way that you could write your own custom HTML that reused elements of Datasette's CSS - the cog menu styling for example - but only on an opt-in basis?	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Make it easier to theme Datasette with CSS 769520939
747062909	https://github.com/simonw/datasette/issues/1148#issuecomment-747062909	https://api.github.com/repos/simonw/datasette/issues/1148	MDEyOklzc3VlQ29tbWVudDc0NzA2MjkwOQ==	simonw 9599	2020-12-16T21:51:54Z	2020-12-16T21:51:54Z	OWNER	This is a really frustrating bug with Vercel: https://github.com/simonw/datasette-publish-vercel/issues/28 `+` characters in URLs get translated into spaces before they get to Datasette. They know about the bug and said they were working on a fix a few months ago, but looks like it's still a problem. A workaround is to avoid `+` and use `-` instead - I think this SQL query does the same thing as yours: https://aws-partners-singapore.vercel.app/partners?sql=select%0D%0A++A.launch_rank%2C%0D%0A++A.partner_info%0D%0Afrom%0D%0A++summary+A%0D%0A++INNER+JOIN+summary+B+ON+A.launch_rank+%3E%3D+B.launch_rank+-+3%0D%0A++AND+A.launch_rank+-4+%3C%3D+B.launch_rank%0D%0AWHERE%0D%0A++B.%22partner_info%22+LIKE+%27%25Palo+Alto%25%27 ```sql select A.launch_rank, A.partner_info from summary A INNER JOIN summary B ON A.launch_rank >= B.launch_rank - 3 AND A.launch_rank -4 <= B.launch_rank WHERE B."partner_info" LIKE '%Palo Alto%' ``` I've been moving projects from Vercel to Cloud Run when they run into this, but that's not a great situation to be in.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Syntax error with + symbol when deployed to Vercel 767561886
744563209	https://github.com/simonw/datasette/issues/1142#issuecomment-744563209	https://api.github.com/repos/simonw/datasette/issues/1142	MDEyOklzc3VlQ29tbWVudDc0NDU2MzIwOQ==	simonw 9599	2020-12-14T16:41:11Z	2020-12-14T16:41:11Z	OWNER	To check out and start the server: /tmp % git clone git@github.com:nitinpaul/datasette Cloning into 'datasette'... remote: Enumerating objects: 124, done. # ... datasette % python3 -m venv venv datasette % source venv/bin/activate (venv) datasette % pip install -e '.[test]' Obtaining file:///private/tmp/datasette Collecting asgiref<3.4.0,>=3.2.10 Using cached asgiref-3.3.1-py3-none-any.whl (19 kB) # ... (venv) datasette % datasette INFO: Started server process [24002] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://127.0.0.1:8001 (Press CTRL+C to quit) And to run the tests: (venv) datasette % pytest ======================================================================== test session starts ======================================================================== platform darwin -- Python 3.9.1, pytest-6.1.2, py-1.10.0, pluggy-0.13.1 SQLite: 3.34.0 rootdir: /private/tmp/datasette, configfile: pytest.ini plugins: asyncio-0.14.0, timeout-1.4.2 collected 841 items tests/test_package.py .. [ 0%]	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"Stream all rows" is not at all obvious 763361458
744522099	https://github.com/simonw/datasette/issues/1142#issuecomment-744522099	https://api.github.com/repos/simonw/datasette/issues/1142	MDEyOklzc3VlQ29tbWVudDc0NDUyMjA5OQ==	nitinpaultifr 6622733	2020-12-14T15:37:47Z	2020-12-14T15:37:47Z	NONE	Alright I could give it a try! This might be a stupid question, can you tell me how to run the server from my fork? So that I can test the changes?	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"Stream all rows" is not at all obvious 763361458
744489028	https://github.com/simonw/datasette/issues/1144#issuecomment-744489028	https://api.github.com/repos/simonw/datasette/issues/1144	MDEyOklzc3VlQ29tbWVudDc0NDQ4OTAyOA==	MarkusH 475613	2020-12-14T14:47:11Z	2020-12-14T14:47:11Z	NONE	Thanks for opening the issue, @simonw. Let me elaborate on my Tweets. [datasette-chartjs](https://github.com/MarkusH/datasette-chartjs) provides drop down lists to pick the chart visualization (e.g. bar, line, doughnut, pie, ...) as well as the column used for the "x axis" (e.g. time). A user can change the values on-demand. The chart will be redrawn w/o querying the database again. However, if a user wants to change the underlying query, they will use the SQL field provided by datasette or any of the other datasette built-in features to amend a query. In order to maintain a user's selections for the plugin, datasette-chartjs copies some parts of [datasette-vega](https://github.com/simonw/datasette-vega) which persist the chosen visualization and column in the hash part of a URL (the stuff behind the `#`). The plugin load the config from the hash upon initialization on the next page and use it accordingly. Additionally, datasette-vega and datasette-chartjs need to make sure to include the hash in all links and forms that cause a reload of the page. This is, such that the config persists between clicks. This ticket is about moving thes parts into datasette that provide the functionality to do so. This includes: 1. a way to load config options with a given prefix from the current URL hash 1. a way to update the current URL hash with a new config value or a bunch of config options 1. updating all necessary links and forms on the current page to include the URL hash whenever its updated 1. to prevent leaking config options to external pages, only "internal" links should be updated There's another, optional, feature that we might want to think about during the design phase: the scope of the config. Links within a datasette instance have 1 of 3 scopes: 1. global, for the whole datasette project 1. database, for all tables in a database 1. table, only for a table within a database When updating the links and forms as pointed out in 3. above, it might be worth considering which links need …	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	JavaScript to help plugins interact with the fragment part of the URL 765637324
744461856	https://github.com/simonw/datasette/issues/276#issuecomment-744461856	https://api.github.com/repos/simonw/datasette/issues/276	MDEyOklzc3VlQ29tbWVudDc0NDQ2MTg1Ng==	robintw 296686	2020-12-14T14:04:57Z	2020-12-14T14:04:57Z	NONE	I'm looking into using datasette with a database with spatialite geometry columns, and came across this issue. Has there been any progress on this since 2018? In one of my tables I'm just storing lat/lon points in a spatialite point geometry, and I've managed to make datasette-cluster-map display the points by extracting the lat and lon in SQL - using something like `select ... ST_X(location) as longitude, ST_Y(location) as latitude from Blah`. Something more 'built-in' would be great though - particularly for the tables I have that store more complex geometries.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Handle spatialite geometry columns better 324835838
743998792	https://github.com/simonw/datasette/issues/1142#issuecomment-743998792	https://api.github.com/repos/simonw/datasette/issues/1142	MDEyOklzc3VlQ29tbWVudDc0Mzk5ODc5Mg==	nitinpaultifr 6622733	2020-12-13T12:14:06Z	2020-12-13T12:14:06Z	NONE	Agreed, it would definitely provide better controls. However, I do feel it makes for a bit of inconsistent UX for the 'Advanced export' section, with links to download for JSON, checkboxes and radio buttons + button to download for CSV. Do you think this example makes the UX a bit nicer/consistent? ![Screenshot 2020-12-13 at 5 38 43 PM](https://user-images.githubusercontent.com/6622733/102011444-1dc1cd00-3d6a-11eb-9e38-5af198161e80.png) I could give it a try if you'd like but I've never contributed to an actual project!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"Stream all rows" is not at all obvious 763361458
741665253	https://github.com/simonw/datasette/issues/766#issuecomment-741665253	https://api.github.com/repos/simonw/datasette/issues/766	MDEyOklzc3VlQ29tbWVudDc0MTY2NTI1Mw==	clausjuhl 2181410	2020-12-09T09:59:05Z	2020-12-09T09:59:05Z	NONE	Hi Simon. Any news on using wildcard-searches with datasette? Thanks!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Enable wildcard-searches by default 617323873
739355855	https://github.com/simonw/datasette/pull/1128#issuecomment-739355855	https://api.github.com/repos/simonw/datasette/issues/1128	MDEyOklzc3VlQ29tbWVudDczOTM1NTg1NQ==	simonw 9599	2020-12-05T19:34:57Z	2020-12-05T19:34:57Z	OWNER	Thanks for this!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Fix startup error on windows 756867924
738904347	https://github.com/simonw/datasette/issues/111#issuecomment-738904347	https://api.github.com/repos/simonw/datasette/issues/111	MDEyOklzc3VlQ29tbWVudDczODkwNDM0Nw==	simonw 9599	2020-12-04T17:16:56Z	2020-12-04T17:16:56Z	OWNER	This is STILL a good idea.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Add “updated” to metadata 274615452
737563699	https://github.com/simonw/datasette/issues/749#issuecomment-737563699	https://api.github.com/repos/simonw/datasette/issues/749	MDEyOklzc3VlQ29tbWVudDczNzU2MzY5OQ==	simonw 9599	2020-12-02T23:45:42Z	2020-12-02T23:45:42Z	OWNER	I asked about this on Twitter - https://twitter.com/steren/status/1334281184965140483 > You simply need to send the `Transfer-Encoding: chunked` header.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Cloud Run fails to serve database files larger than 32MB 610829227
737463116	https://github.com/simonw/datasette/issues/942#issuecomment-737463116	https://api.github.com/repos/simonw/datasette/issues/942	MDEyOklzc3VlQ29tbWVudDczNzQ2MzExNg==	simonw 9599	2020-12-02T20:02:10Z	2020-12-02T20:03:01Z	OWNER	My idea is that if you installed my proposed plugin you wouldn't need `metadata.json` at all - your metadata would instead live in a table in the connected SQLite database files - either one table per database (so the metadata can live in the same place as the data) or maybe also in a dedicated separate database file, for if you want to add metadata to an otherwise read-only database. The plugin would then provide a UI for editing that metadata - maybe by configuring some writable canned queries or maybe something more custom than that. Or you could edit the metadata by manually editing the SQLite database file (or loading data into it using a tool like [yaml-to-sqlite](https://github.com/simonw/yaml-to-sqlite)).	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Support column descriptions in metadata.json 681334912
735443626	https://github.com/simonw/datasette/issues/1114#issuecomment-735443626	https://api.github.com/repos/simonw/datasette/issues/1114	MDEyOklzc3VlQ29tbWVudDczNTQ0MzYyNg==	simonw 9599	2020-11-29T19:40:49Z	2020-11-29T19:40:49Z	OWNER	Fix is out in 0.52.1: https://docs.datasette.io/en/latest/changelog.html#v0-52-1	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	--load-extension=spatialite not working with datasetteproject/datasette docker image 752966476
726412057	https://github.com/simonw/datasette/issues/865#issuecomment-726412057	https://api.github.com/repos/simonw/datasette/issues/865	MDEyOklzc3VlQ29tbWVudDcyNjQxMjA1Nw==	simonw 9599	2020-11-12T23:49:23Z	2020-11-12T23:49:23Z	OWNER	@tballison thanks, I've split that out into a new issue #1091	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	base_url doesn't seem to work when adding criteria and clicking "apply" 644582921
718342036	https://github.com/simonw/datasette/issues/1050#issuecomment-718342036	https://api.github.com/repos/simonw/datasette/issues/1050	MDEyOklzc3VlQ29tbWVudDcxODM0MjAzNg==	simonw 9599	2020-10-29T03:49:57Z	2020-10-29T03:49:57Z	OWNER	@thadk from that error it looks like the problem may have been that you had a BLOB column containing a `null` value? If so that's definitely a bug, I'll fix that.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Switch to .blob render extension for BLOB downloads 729057388
717359145	https://github.com/simonw/sqlite-utils/pull/189#issuecomment-717359145	https://api.github.com/repos/simonw/sqlite-utils/issues/189	MDEyOklzc3VlQ29tbWVudDcxNzM1OTE0NQ==	adamwolf 35681	2020-10-27T16:20:32Z	2020-10-27T16:20:32Z	CONTRIBUTOR	No problem. I added a test. Let me know if it looks sufficient or if you want me to to tweak something! If you don't mind, would you tag this PR as "hacktoberfest-accepted"? If you do mind, no problem and I'm sorry for asking :) My kiddos like the shirts.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Allow iterables other than Lists in m2m records 729818242
716048564	https://github.com/simonw/datasette/issues/1033#issuecomment-716048564	https://api.github.com/repos/simonw/datasette/issues/1033	MDEyOklzc3VlQ29tbWVudDcxNjA0ODU2NA==	simonw 9599	2020-10-24T20:08:31Z	2020-10-24T20:08:31Z	OWNER	Documentation here: https://docs.datasette.io/en/latest/internals.html#datasette-urls	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	datasette.urls.static_plugins(...) method 725099777
715585140	https://github.com/simonw/datasette/pull/1043#issuecomment-715585140	https://api.github.com/repos/simonw/datasette/issues/1043	MDEyOklzc3VlQ29tbWVudDcxNTU4NTE0MA==	simonw 9599	2020-10-23T20:54:29Z	2020-10-23T20:54:29Z	OWNER	Thanks. I'll push a source release of `asgi-csrf`.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Include LICENSE in sdist 727915394
715584579	https://github.com/simonw/datasette/pull/1044#issuecomment-715584579	https://api.github.com/repos/simonw/datasette/issues/1044	MDEyOklzc3VlQ29tbWVudDcxNTU4NDU3OQ==	simonw 9599	2020-10-23T20:53:01Z	2020-10-23T20:53:01Z	OWNER	Thanks for this!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Add minimum supported python 727916744
712569695	https://github.com/simonw/datasette/issues/782#issuecomment-712569695	https://api.github.com/repos/simonw/datasette/issues/782	MDEyOklzc3VlQ29tbWVudDcxMjU2OTY5NQ==	carlmjohnson 222245	2020-10-20T03:45:48Z	2020-10-20T03:46:14Z	NONE	I vote against headers. It has a lot of strikes against it: poor discoverability, new developers often don’t know how to use them, makes CORS harder, makes it hard to use eg with JQ, needs ad hoc specification for each bit of metadata, etc. The only advantage of headers is that you don’t need to do .rows, but that’s actually good as a data validation step anyway—if .rows is missing assume there’s an error and do your error handling path instead of parsing the rest.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Redesign default .json format 627794879
712317638	https://github.com/simonw/datasette/issues/991#issuecomment-712317638	https://api.github.com/repos/simonw/datasette/issues/991	MDEyOklzc3VlQ29tbWVudDcxMjMxNzYzOA==	simonw 9599	2020-10-19T17:30:56Z	2020-10-19T17:30:56Z	OWNER	https://biglocal.datasettes.com/ is one of my larger Datasettes in terms of number of databases.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Redesign application homepage 714377268
702265255	https://github.com/simonw/datasette/pull/986#issuecomment-702265255	https://api.github.com/repos/simonw/datasette/issues/986	MDEyOklzc3VlQ29tbWVudDcwMjI2NTI1NQ==	simonw 9599	2020-10-01T16:51:45Z	2020-10-01T16:51:45Z	OWNER	Thanks for taking a look! The fix ended up being a little different from this because I still want to disable faceting on regular single primary keys (since faceting by those won't ever produce interesting results) - here's what I used: https://github.com/simonw/datasette/commit/5d6bc4c268f9f155e59561671f8617addd3e91bc	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Allow facet by primary keys, fixes #985 712889459
701627158	https://github.com/simonw/sqlite-utils/pull/178#issuecomment-701627158	https://api.github.com/repos/simonw/sqlite-utils/issues/178	MDEyOklzc3VlQ29tbWVudDcwMTYyNzE1OA==	simonw 9599	2020-09-30T20:29:11Z	2020-09-30T20:29:11Z	OWNER	Thanks for the fix!	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Update README.md 709043182
697973420	https://github.com/simonw/datasette/issues/619#issuecomment-697973420	https://api.github.com/repos/simonw/datasette/issues/619	MDEyOklzc3VlQ29tbWVudDY5Nzk3MzQyMA==	obra 45416	2020-09-23T21:07:58Z	2020-09-23T21:07:58Z	NONE	I've just run into this after crafting a complex query and discovered that hitting back loses my query. Even showing me the whole bad query would be a huge improvement over the current status quo.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	"Invalid SQL" page should let you edit the SQL 520655983
696163452	https://github.com/simonw/datasette/issues/670#issuecomment-696163452	https://api.github.com/repos/simonw/datasette/issues/670	MDEyOklzc3VlQ29tbWVudDY5NjE2MzQ1Mg==	snth 652285	2020-09-21T14:46:10Z	2020-09-21T14:46:10Z	NONE	I'm currently using PostgREST to serve OpenAPI APIs off Postgresql databases. I would like to try out datasette once this becomes available on Postgres.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Prototoype for Datasette on PostgreSQL 564833696
695896557	https://github.com/simonw/datasette/issues/970#issuecomment-695896557	https://api.github.com/repos/simonw/datasette/issues/970	MDEyOklzc3VlQ29tbWVudDY5NTg5NjU1Nw==	simonw 9599	2020-09-21T04:40:12Z	2020-09-21T04:40:12Z	OWNER	The Python standard library has a module for this: https://docs.python.org/3/library/webbrowser.html	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	request an "-o" option on "datasette server" to open the default browser at the running url 705108492
693199049	https://github.com/simonw/sqlite-utils/issues/159#issuecomment-693199049	https://api.github.com/repos/simonw/sqlite-utils/issues/159	MDEyOklzc3VlQ29tbWVudDY5MzE5OTA0OQ==	simonw 9599	2020-09-16T06:20:26Z	2020-09-16T06:20:26Z	OWNER	See #121 - I need to think harder about how this all interacts with transactions. You can do this: ```python with db.conn: db["mytable"].delete_where() ``` But that should be documented and maybe rethought.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	.delete_where() does not auto-commit (unlike .insert() or .upsert()) 702386948
691501132	https://github.com/dogsheep/twitter-to-sqlite/issues/50#issuecomment-691501132	https://api.github.com/repos/dogsheep/twitter-to-sqlite/issues/50	MDEyOklzc3VlQ29tbWVudDY5MTUwMTEzMg==	bcongdon 706257	2020-09-12T14:48:10Z	2020-09-12T14:48:10Z	NONE	This seems to be an issue even with larger values of `--stop_after`: ``` $ twitter-to-sqlite favorites twitter.db --stop_after=2000 Importing favorites [####################################] 198 $ ```	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	favorites --stop_after=N stops after min(N, 200) 698791218
683173375	https://github.com/simonw/sqlite-utils/pull/142#issuecomment-683173375	https://api.github.com/repos/simonw/sqlite-utils/issues/142	MDEyOklzc3VlQ29tbWVudDY4MzE3MzM3NQ==	simonw 9599	2020-08-28T22:29:02Z	2020-08-28T22:29:02Z	OWNER	Yeah I think that failure is actually because there's a brand new release of Black out and it subtly changes some of the formatting rules. I'll merge this and then run Black against the entire codebase.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	insert_all(..., alter=True) should work for new columns introduced after the first 100 records 688386219
675718593	https://github.com/simonw/datasette/issues/942#issuecomment-675718593	https://api.github.com/repos/simonw/datasette/issues/942	MDEyOklzc3VlQ29tbWVudDY3NTcxODU5Mw==	simonw 9599	2020-08-18T21:02:11Z	2020-08-18T21:02:24Z	OWNER	Easiest solution: if you provide column metadata it gets displayed above the table, something like on https://fivethirtyeight.datasettes.com/fivethirtyeight/antiquities-act%2Factions_under_antiquities_act <img width="500" alt="fivethirtyeight__antiquities-act_actions_under_antiquities_act__344_rows" src="https://user-images.githubusercontent.com/9599/90565187-57d3e700-e15b-11ea-89c8-0270e3040a50.png"> HTML `title=` tooltips are also added to the table headers, which won't be visible on touch devices but that's OK because the information is visible on the page already.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Support column descriptions in metadata.json 681334912
655673896	https://github.com/simonw/sqlite-utils/issues/121#issuecomment-655673896	https://api.github.com/repos/simonw/sqlite-utils/issues/121	MDEyOklzc3VlQ29tbWVudDY1NTY3Mzg5Ng==	simonw 9599	2020-07-08T18:08:11Z	2020-07-08T18:08:11Z	OWNER	I'm with you on most of this. Completely agreed that the CLI should do everything in a transaction. The one thing I'm not keen on is forcing calling code to explicitly start a transaction, for a couple of reasons: 1. It will break all of the existing code out there 2. It doesn't match to how I most commonly use this library - as an interactive tool in a Jupyter notebook, where I'm generally working against a brand new scratch database and any errors don't actually matter So... how about this: IF you wrap your code in a `with db:` block then the `.insert()` and suchlike methods expect you to manage transactions yourself. But if you don't use the context manager they behave like they do at the moment (or maybe a bit more sensibly). That way existing code works as it does today, lazy people like me can call `.insert()` without thinking about transactions, but people writing actual production code (as opposed to Jupyter hacks) have a sensible way to take control of the transactions themselves.	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Improved (and better documented) support for transactions 652961907
655652679	https://github.com/simonw/sqlite-utils/issues/121#issuecomment-655652679	https://api.github.com/repos/simonw/sqlite-utils/issues/121	MDEyOklzc3VlQ29tbWVudDY1NTY1MjY3OQ==	tsibley 79913	2020-07-08T17:24:46Z	2020-07-08T17:24:46Z	CONTRIBUTOR	Better transaction handling would be really great. Some of my thoughts on implementing better transaction discipline are in https://github.com/simonw/sqlite-utils/pull/118#issuecomment-655239728. My preferences: - Each CLI command should operate in a single transaction so that either the whole thing succeeds or the whole thing is rolled back. This avoids partially completed operations when an error occurs part way through processing. Partially completed operations are typically much harder to recovery from gracefully and may cause inconsistent data states. - The Python API should be transaction-agnostic and rely on the caller to coordinate transactions. Only the caller knows how individual insert, create, update, etc operations/methods should be bundled conceptually into transactions. When the caller is the CLI, for example, that bundling would be at the CLI command-level. Other callers might want to break up operations into multiple transactions. Transactions are usually most useful when controlled at the application-level (like logging configuration) instead of the library level. The library needs to provide an API that's conducive to transaction use, though. - The Python API should provide a context manager to provide consistent transactions handling with more useful defaults than Python's `sqlite3` module. The latter issues implicit `BEGIN` statements by default for most DML (`INSERT`, `UPDATE`, `DELETE`, … but not `SELECT`, I believe), but not DDL (`CREATE TABLE`, `DROP TABLE`, `CREATE VIEW`, …). Notably, the `sqlite3` module doesn't issue the implicit `BEGIN` until the first DML statement. It _does not_ issue it when entering the `with conn` block, like other DBAPI2-compatible modules do. The `with conn` block for `sqlite3` only arranges to commit or rollback an existing transaction when exiting. Including DDL and `SELECT`s in transactions is important for operation consistency, though. There are several existing bugs.python.org tickets about this and future changes are in the works, but sql…	{"total_count": 1, "+1": 1, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	Improved (and better documented) support for transactions 652961907

Advanced export

JSON shape: default, array, newline-delimited, object

CREATE TABLE [issue_comments] (
   [html_url] TEXT,
   [issue_url] TEXT,
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [created_at] TEXT,
   [updated_at] TEXT,
   [author_association] TEXT,
   [body] TEXT,
   [reactions] TEXT,
   [issue] INTEGER REFERENCES [issues]([id])
, [performed_via_github_app] TEXT);
CREATE INDEX [idx_issue_comments_issue]
                ON [issue_comments] ([issue]);
CREATE INDEX [idx_issue_comments_user]
                ON [issue_comments] ([user]);