issue_comments
5 rows where "updated_at" is on date 2019-11-14 sorted by updated_at
This data as json, CSV (advanced)
created_at (date) 1 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▼ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
553662218 | https://github.com/simonw/datasette/issues/634#issuecomment-553662218 | https://api.github.com/repos/simonw/datasette/issues/634 | MDEyOklzc3VlQ29tbWVudDU1MzY2MjIxOA== | simonw 9599 | 2019-11-14T00:05:22Z | 2019-11-14T00:05:22Z | OWNER | Here's why: the `pytest` invocation is part of the `script` block shared by all of the stages: https://github.com/simonw/datasette/blob/b51f258d00bb3c3b401f15d46a1fbd50394dbe1c/.travis.yml#L11-L14 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Don't run tests twice when releasing a tag 522352520 | |
553665699 | https://github.com/simonw/datasette/issues/628#issuecomment-553665699 | https://api.github.com/repos/simonw/datasette/issues/628 | MDEyOklzc3VlQ29tbWVudDU1MzY2NTY5OQ== | simonw 9599 | 2019-11-14T00:19:32Z | 2019-11-14T00:19:32Z | OWNER | This is going to be a lot easier than the first attempt because I already modified the `.render()` method to be async four months ago: https://github.com/simonw/datasette/commit/fcfcae21e67cc15090942b1d2a47b5f016279337#diff-4296b31822a931646fa92cd2d5581521R105 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Render jinja2 templates in async mode 521329771 | |
554109342 | https://github.com/simonw/datasette/issues/580#issuecomment-554109342 | https://api.github.com/repos/simonw/datasette/issues/580 | MDEyOklzc3VlQ29tbWVudDU1NDEwOTM0Mg== | simonw 9599 | 2019-11-14T22:25:24Z | 2019-11-14T22:25:24Z | OWNER | I needed this again today for `datasette-template-sql`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Testing utilities should be available to plugins 502355384 | |
554119604 | https://github.com/simonw/datasette/issues/580#issuecomment-554119604 | https://api.github.com/repos/simonw/datasette/issues/580 | MDEyOklzc3VlQ29tbWVudDU1NDExOTYwNA== | simonw 9599 | 2019-11-14T22:51:00Z | 2019-11-14T22:51:00Z | OWNER | One thing that would be useful is a way of constructing a `Datasette()` instance (and accompanying `TestClient`) which is attached to an in-memory database that the test itself can manipulate. This would make it trivial to run tests against hypothetical database tables - those tables could be created using `sqlite-utils` directly against the in-memory database that's being manipulated by the system-under-test. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Testing utilities should be available to plugins 502355384 | |
554132794 | https://github.com/simonw/datasette/issues/628#issuecomment-554132794 | https://api.github.com/repos/simonw/datasette/issues/628 | MDEyOklzc3VlQ29tbWVudDU1NDEzMjc5NA== | simonw 9599 | 2019-11-14T23:27:51Z | 2019-11-14T23:28:09Z | OWNER | I'm releasing this as Datasette 0.32 - I have a new plugin which takes advantage of it here: https://github.com/simonw/datasette-template-sql | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Render jinja2 templates in async mode 521329771 |
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]);
updated_at (date) 1 ✖