issue_comments: 1021472918

This data as json

html_url	issue_url	id	node_id	user	created_at	updated_at	author_association	body	reactions	issue	performed_via_github_app
https://github.com/simonw/datasette/issues/1612#issuecomment-1021472918	https://api.github.com/repos/simonw/datasette/issues/1612	1021472918	IC_kwDOBm6k_c484nCW	9599	2022-01-25T18:14:27Z	2022-01-25T18:15:54Z	OWNER	They're currently shown at the very bottom of the page, under the list of tables and far away from the SQL query box: https://latest.datasette.io/fixtures <img width="353" alt="image" src="https://user-images.githubusercontent.com/9599/151034640-c3b79214-7fec-4137-b3ed-45541167feff.png"> I'm also questioning if "Queries" is the best header for this. Other options: - Canned queries (what the feature is called in the documentation, but I don't think it's a great user-facing term) - Saved queries - overlaps with a mechanism by which queries can be saved by the user using a plugin such as [datasette-saved-queries](https://github.com/simonw/datasette-saved-queries) - though that plugin does itself use the canned queries plugin hook so not completely unrelated - Sample or Example queries - I don't like these much because they're more than just examples - they are often the core functionality of the specific customized Datasette instance - Prepared queries - overlaps with terminology used in other databases, so not great either - Pre-configured queries - urgh, don't like that language, feels clumsy - Query recipes - bit out of left-field this one, only really makes sense for queries that include named parameters for specific use-cases Maybe "Queries" is right after all.	{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	1114147905