issue_comments

Table actions

5 rows where author_association = "OWNER", issue = 507454958 and user = 9599 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

  • simonw · 5 ✖

issue 1

  • Handle really wide tables better · 5 ✖

author_association 1

  • OWNER · 5 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1238790634 https://github.com/simonw/datasette/issues/596#issuecomment-1238790634 https://api.github.com/repos/simonw/datasette/issues/596 IC_kwDOBm6k_c5J1nHq simonw 9599 2022-09-07T00:55:52Z 2022-09-07T00:58:41Z OWNER

Or there's this recipe on StackOverflow that does the same thing without jQuery - there's an interactive demo on that page if you click "Run code snippet": https://stackoverflow.com/a/47038108/6083

All sorts of other potential solutions in that thread too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  
1238790158 https://github.com/simonw/datasette/issues/596#issuecomment-1238790158 https://api.github.com/repos/simonw/datasette/issues/596 IC_kwDOBm6k_c5J1nAO simonw 9599 2022-09-07T00:54:55Z 2022-09-07T00:54:55Z OWNER

The jqDoubleScroll plugin is interesting: https://github.com/avianey/jqDoubleScroll/blob/master/jquery.doubleScroll.js

Here's a demo: https://6317eba21040d42c0228aab9--tiny-tarsier-c1f294.netlify.app/example.html

Wouldn't be too hard to port that to work without jQuery.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  
720689653 https://github.com/simonw/datasette/issues/596#issuecomment-720689653 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDcyMDY4OTY1Mw== simonw 9599 2020-11-02T19:53:36Z 2020-11-02T19:53:47Z OWNER

In #998 I implemented a horizontal scrollbar for these tables, which is a big improvement - demo here: https://global-power-plants.datasettes.com/global-power-plants/global-power-plants

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  
647893140 https://github.com/simonw/datasette/issues/596#issuecomment-647893140 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDY0Nzg5MzE0MA== simonw 9599 2020-06-23T03:59:51Z 2020-06-23T03:59:51Z OWNER

Related: #862 - a time limit on the total time spent considering suggested facets for a table.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  
542462126 https://github.com/simonw/datasette/issues/596#issuecomment-542462126 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDU0MjQ2MjEyNg== simonw 9599 2019-10-16T00:45:45Z 2019-10-16T00:45:45Z OWNER

This means moving away from select *. I've been thinking this would be worthwhile anyway, since that way when you click "Edit SQL" you'll get a more useful SQL statement to start hacking away at.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  

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