issue_comments

Table actions

4 rows where issue = 443021509 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

  • Paginate + search for databases/tables on the homepage · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
747734273 https://github.com/simonw/datasette/issues/461#issuecomment-747734273 https://api.github.com/repos/simonw/datasette/issues/461 MDEyOklzc3VlQ29tbWVudDc0NzczNDI3Mw== simonw 9599 2020-12-17T22:14:46Z 2020-12-17T22:14:46Z OWNER

I've been thinking about this a bunch. For Datasette to be useful as a private repository of data (Datasette Library, #417) it's crucial that it can handle a much, much larger number of databases.

This makes me worry about how many connections (and open file handles) it makes sense to have open at one time.

I realize now that this is much less of a problem for private instances. Public instances on the internet could get traffic to any database at any time, so connections could easily get out of control. A private instance with only a few users could instead get away with only opening connections to databases in "active use".

This does however make it even more important for Datasette to maintain a cached set of metadata about the tables - which is also needed to power this feature.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Paginate + search for databases/tables on the homepage 443021509  
710693927 https://github.com/simonw/datasette/issues/461#issuecomment-710693927 https://api.github.com/repos/simonw/datasette/issues/461 MDEyOklzc3VlQ29tbWVudDcxMDY5MzkyNw== simonw 9599 2020-10-16T23:20:43Z 2020-10-16T23:20:43Z OWNER

Related: redesign homepage entirely #991.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Paginate + search for databases/tables on the homepage 443021509  
492296836 https://github.com/simonw/datasette/issues/461#issuecomment-492296836 https://api.github.com/repos/simonw/datasette/issues/461 MDEyOklzc3VlQ29tbWVudDQ5MjI5NjgzNg== simonw 9599 2019-05-14T15:50:34Z 2019-05-14T15:51:11Z OWNER

This is needed by Datasette Library #417 since that's going to demand listing a LOT of databases on the homepage.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Paginate + search for databases/tables on the homepage 443021509  
491532380 https://github.com/simonw/datasette/issues/461#issuecomment-491532380 https://api.github.com/repos/simonw/datasette/issues/461 MDEyOklzc3VlQ29tbWVudDQ5MTUzMjM4MA== simonw 9599 2019-05-11T18:06:01Z 2019-05-11T18:06:01Z OWNER

I plan to add a search filter box too, but only if there are more than X (probably 10) connected databases.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Paginate + search for databases/tables on the homepage 443021509  

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