issue_comments

Table actions

4 rows where author_association = "OWNER", issue = 336924199 and "updated_at" is on date 2018-07-10 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

  • Limit text display in cells containing large amounts of text · 4 ✖

author_association 1

  • OWNER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
403907193 https://github.com/simonw/datasette/issues/330#issuecomment-403907193 https://api.github.com/repos/simonw/datasette/issues/330 MDEyOklzc3VlQ29tbWVudDQwMzkwNzE5Mw== simonw 9599 2018-07-10T17:41:14Z 2018-07-10T17:41:14Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Limit text display in cells containing large amounts of text 336924199  
403906747 https://github.com/simonw/datasette/issues/330#issuecomment-403906747 https://api.github.com/repos/simonw/datasette/issues/330 MDEyOklzc3VlQ29tbWVudDQwMzkwNjc0Nw== simonw 9599 2018-07-10T17:39:46Z 2018-07-10T17:39:46Z OWNER

datasette publish now timezones.db --spatialite \ --extra-options="--config truncate_cells_html:200" \ --name=datasette-issue-330-demo \ --branch=master https://datasette-issue-330-demo-sbelwxttfn.now.sh/timezones-3cb9f64/timezones

But https://datasette-issue-330-demo-sbelwxttfn.now.sh/timezones-3cb9f64/timezones/1 displays the full blob.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Limit text display in cells containing large amounts of text 336924199  
403868584 https://github.com/simonw/datasette/issues/330#issuecomment-403868584 https://api.github.com/repos/simonw/datasette/issues/330 MDEyOklzc3VlQ29tbWVudDQwMzg2ODU4NA== simonw 9599 2018-07-10T15:39:12Z 2018-07-10T16:21:08Z OWNER

I think this makes sense for the HTML view (not for JSON or CSV). It could be controlled be a new config option, truncate_cells_html - which is on by default but can be turned off.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Limit text display in cells containing large amounts of text 336924199  
403855963 https://github.com/simonw/datasette/issues/330#issuecomment-403855963 https://api.github.com/repos/simonw/datasette/issues/330 MDEyOklzc3VlQ29tbWVudDQwMzg1NTk2Mw== simonw 9599 2018-07-10T15:04:31Z 2018-07-10T15:04:31Z OWNER

This relates to #276 - I'm definitely convinced now that displaying a giant b'...' blob on the page is not a useful default.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Limit text display in cells containing large amounts of text 336924199  

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