issue_comments

Table actions

4 rows where issue = 1384549993 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • Setting to turn off table row counts entirely · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1258738740 https://github.com/simonw/datasette/issues/1818#issuecomment-1258738740 https://api.github.com/repos/simonw/datasette/issues/1818 IC_kwDOBm6k_c5LBtQ0 nelsonjchen 5363 2022-09-26T22:52:45Z 2022-09-26T22:55:57Z NONE

thoughts on order of precedence to use:

  • sqlite-utils count, if present. closest thing to a standard i guess.
  • row(max_id) if like, the first and/or last x amount of rows ids are all contiguous. kind of a cheap/dumb/imperfect heuristic to see if the table is dump/not dump. if the check passes, still stick on est. after the display.
  • count(*) if enabled in datasette 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Setting to turn off table row counts entirely 1384549993  
1258735747 https://github.com/simonw/datasette/issues/1818#issuecomment-1258735747 https://api.github.com/repos/simonw/datasette/issues/1818 IC_kwDOBm6k_c5LBsiD simonw 9599 2022-09-26T22:47:59Z 2022-09-26T22:47:59Z OWNER

Another option here is to tie into a feature I built in sqlite-utils with this problem in mind but never introduced on the Datasette side of things: https://sqlite-utils.datasette.io/en/stable/python-api.html#cached-table-counts-using-triggers

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Setting to turn off table row counts entirely 1384549993  
1258735283 https://github.com/simonw/datasette/issues/1818#issuecomment-1258735283 https://api.github.com/repos/simonw/datasette/issues/1818 IC_kwDOBm6k_c5LBsaz simonw 9599 2022-09-26T22:47:19Z 2022-09-26T22:47:19Z OWNER

That's a really interesting idea: for a lot of databases (those made out of straight imports from CSV) max(rowid) would indeed reflect the size of the table, but would be a MUCH faster operation than attempting a count(*).

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Setting to turn off table row counts entirely 1384549993  
1257290709 https://github.com/simonw/datasette/issues/1818#issuecomment-1257290709 https://api.github.com/repos/simonw/datasette/issues/1818 IC_kwDOBm6k_c5K8LvV nelsonjchen 5363 2022-09-25T22:17:06Z 2022-09-25T22:17:06Z NONE

I wonder if having an option for displaying the max row id might help too. Not accurate especially if something was deleted, but useful for DBs as a dump. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Setting to turn off table row counts entirely 1384549993  

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