github: issues: 6 rows where comments = 2 and "updated

6 rows where comments = 2 and "updated_at" is on date 2019-06-24

Search:

descending

id ▼	node_id	number	title	user	state	assignee	comments	created_at	updated_at	closed_at	author_association	pull_request	body	repo	type	reactions	draft	state_reason
276455748	MDU6SXNzdWUyNzY0NTU3NDg=	146	datasette publish gcloud	simonw 9599	closed		2	2017-11-23T18:55:03Z	2019-06-24T06:48:20Z	2019-06-24T06:48:20Z	OWNER		See also #103 It looks like you can start a Google Cloud VM with a "docker container" option - and the Google Cloud Registry is easy to push containers to. So it would be feasible to have `datasette publish gcloud ...` automatically build a container, push it to GCR, then start a new VM instance with it: https://cloud.google.com/container-registry/docs/pushing-and-pulling	datasette 107914493	issue	{"url": "https://api.github.com/repos/simonw/datasette/issues/146/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}		completed
291639118	MDU6SXNzdWUyOTE2MzkxMTg=	183	Custom Queries - escaping strings	psychemedia 82988	closed		2	2018-01-25T16:49:13Z	2019-06-24T06:45:07Z	2019-06-24T06:45:07Z	CONTRIBUTOR		If a SQLite table column name contains spaces, they are usually referred to in double quotes: `SELECT * FROM mytable WHERE "gappy column name"="my value";` In the JSON metadata file, this is passed by escaping the double quotes: `"queries": {"my query": "SELECT * FROM mytable WHERE \"gappy column name\"=\"my value\";"}` When specifying a custom query in `metadata.json` using double quotes, these are then rendered in the datasette query box using single quotes: `SELECT * FROM mytable WHERE 'gappy column name'='my value';` which does not work. Alternatively, a valid custom query can be passed using backticks (\`) to quote the column name and single (unescaped) quotes for the matched value: ``"queries": {"my query": "SELECT * FROM mytable WHERE `gappy column name`='my value';"}``	datasette 107914493	issue	{"url": "https://api.github.com/repos/simonw/datasette/issues/183/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}		completed
329147284	MDU6SXNzdWUzMjkxNDcyODQ=	305	Add contributor guidelines to docs	simonw 9599	closed		2	2018-06-04T17:25:30Z	2019-06-24T06:40:19Z	2019-06-24T06:40:19Z	OWNER		https://channels.readthedocs.io/en/latest/contributing.html is a nice example of this done well.	datasette 107914493	issue	{"url": "https://api.github.com/repos/simonw/datasette/issues/305/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}		completed
438048318	MDExOlB1bGxSZXF1ZXN0Mjc0MTc0NjE0	437	Add inspect and prepare_sanic hooks	russss 45057	closed		2	2019-04-28T11:53:34Z	2019-06-24T16:38:57Z	2019-06-24T16:38:56Z	CONTRIBUTOR	simonw/datasette/pulls/437	This adds two new plugin hooks: The `inspect` hook allows plugins to add data to the inspect dictionary. The `prepare_sanic` hook allows plugins to hook into the web router. I've attached a warning to this hook in the docs in light of #272 but I want this hook now... On quick inspection, I don't think it's worthwhile to try and make this hook independent of the web framework (but it looks like Starlette would make the hook implementation a bit nicer). Ref #14	datasette 107914493	pull	{"url": "https://api.github.com/repos/simonw/datasette/issues/437/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}	0
459627549	MDU6SXNzdWU0NTk2Mjc1NDk=	523	Show total/unfiltered row count when filtering	rixx 2657547	closed		2	2019-06-23T22:56:48Z	2019-06-24T01:38:14Z	2019-06-24T01:38:14Z	CONTRIBUTOR		When I'm seeing a filtered view of a table, I'd like to be able to see something like '2 rows where status != "closed" (of 1000 total)' to have a context for the data I'm seeing – e.g. currently my database is being filled by an importer, so this information would be super helpful. Since this information would be a performance hit, maybe something like '12 rows where status != "closed" (of ??? total)' with lazy-loading on-click(?) could be applied (Or via a "How many total?" tooltip, or …)	datasette 107914493	issue	{"url": "https://api.github.com/repos/simonw/datasette/issues/523/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}		completed
459714943	MDU6SXNzdWU0NTk3MTQ5NDM=	525	Add section on sqite-utils enable-fts to the search documentation	simonw 9599	closed	simonw 9599	2	2019-06-24T06:39:16Z	2019-06-24T16:36:35Z	2019-06-24T16:29:43Z	OWNER		https://datasette.readthedocs.io/en/stable/full_text_search.html already has a section about csvs-to-sqlite, sqlite-utils is even more relevant.	datasette 107914493	issue	{"url": "https://api.github.com/repos/simonw/datasette/issues/525/reactions", "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}		completed

Advanced export

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

CREATE TABLE [issues] (
   [id] INTEGER PRIMARY KEY,
   [node_id] TEXT,
   [number] INTEGER,
   [title] TEXT,
   [user] INTEGER REFERENCES [users]([id]),
   [state] TEXT,
   [locked] INTEGER,
   [assignee] INTEGER REFERENCES [users]([id]),
   [milestone] INTEGER REFERENCES [milestones]([id]),
   [comments] INTEGER,
   [created_at] TEXT,
   [updated_at] TEXT,
   [closed_at] TEXT,
   [author_association] TEXT,
   [pull_request] TEXT,
   [body] TEXT,
   [repo] INTEGER REFERENCES [repos]([id]),
   [type] TEXT
, [active_lock_reason] TEXT, [performed_via_github_app] TEXT, [reactions] TEXT, [draft] INTEGER, [state_reason] TEXT);
CREATE INDEX [idx_issues_repo]
                ON [issues] ([repo]);
CREATE INDEX [idx_issues_milestone]
                ON [issues] ([milestone]);
CREATE INDEX [idx_issues_assignee]
                ON [issues] ([assignee]);
CREATE INDEX [idx_issues_user]
                ON [issues] ([user]);