issue_comments

Table actions

3 rows where author_association = "OWNER" and issue = 465327844 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • Potential improvements to facet-by-date · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
509278616 https://github.com/simonw/datasette/issues/553#issuecomment-509278616 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3ODYxNg== simonw 9599 2019-07-08T15:41:05Z 2019-07-08T15:41:55Z OWNER

Having a "more link" is very interesting. I could do that by generating a custom SQL query link, but that wouldn't play well in instances that disable custom SQL.

This may be a case where a new URL is needed under the proposed /database/table/-/namespace namespace - #296

Compatibility with datasette-vega is useful, since then anyone can get a chart by starting with a facet of some sort.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  
509277853 https://github.com/simonw/datasette/issues/553#issuecomment-509277853 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3Nzg1Mw== simonw 9599 2019-07-08T15:39:08Z 2019-07-08T15:39:15Z OWNER

My reply on Twitter:

https://twitter.com/simonw/status/1148254258900262913

Huh I hadn't thought about order-by-date - that's really useful. Not sure what I'll do for data that's spread over e.g. 1,000 days (other facets only return up to 30 data points right now) - maybe 30 most recent plus a link to view more than that?

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  
509277577 https://github.com/simonw/datasette/issues/553#issuecomment-509277577 https://api.github.com/repos/simonw/datasette/issues/553 MDEyOklzc3VlQ29tbWVudDUwOTI3NzU3Nw== simonw 9599 2019-07-08T15:38:26Z 2019-07-08T15:38:26Z OWNER

One thing that's clear is I need to add a demo to the fixtures that illustrates the feature, ideally with a thousand generated rows in it to give a better example of how it works.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Potential improvements to facet-by-date 465327844  

Advanced export

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

CSV options: 

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]);