issue_comments
5 rows where author_association = "OWNER", issue = 443020810 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: created_at (date), updated_at (date)
issue 1
- Design changes to homepage to support mutable files · 5 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 492903581 | https://github.com/simonw/datasette/issues/460#issuecomment-492903581 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5MjkwMzU4MQ== | simonw 9599 | 2019-05-16T03:34:08Z | 2019-05-16T03:34:08Z | OWNER | Demo of above: https://latest.datasette.io/?_sort=relationships compared to https://latest.datasette.io/ |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Design changes to homepage to support mutable files 443020810 | |
| 492899100 | https://github.com/simonw/datasette/issues/460#issuecomment-492899100 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5OTEwMA== | simonw 9599 | 2019-05-16T03:07:41Z | 2019-05-16T03:07:41Z | OWNER | I'm going to sort by row counts first, but if row counts aren't available I'll fall back to number of inbound/outbound foreign keys. To make unit testing easier, I'll accept an undocumented ?_sort=relationships parameter |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Design changes to homepage to support mutable files 443020810 | |
| 492898595 | https://github.com/simonw/datasette/issues/460#issuecomment-492898595 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5Mjg5ODU5NQ== | simonw 9599 | 2019-05-16T03:04:29Z | 2019-05-16T03:04:29Z | OWNER | One last thing before I close this: sort tables by number of inbound/outbound foreign keys. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Design changes to homepage to support mutable files 443020810 | |
| 492285114 | https://github.com/simonw/datasette/issues/460#issuecomment-492285114 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5MjI4NTExNA== | simonw 9599 | 2019-05-14T15:22:58Z | 2019-05-14T15:22:58Z | OWNER | If a database has less than 10 tables AND I can get a full count of all 10 of them in under 10ms each then I think I'll still show the row counts. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Design changes to homepage to support mutable files 443020810 | |
| 491536725 | https://github.com/simonw/datasette/issues/460#issuecomment-491536725 | https://api.github.com/repos/simonw/datasette/issues/460 | MDEyOklzc3VlQ29tbWVudDQ5MTUzNjcyNQ== | simonw 9599 | 2019-05-11T19:11:44Z | 2019-05-11T19:11:44Z | OWNER | I split pagination out to #461 - and I don't consider that necessary to ship the next release. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Design changes to homepage to support mutable files 443020810 |
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]);
user 1