issue_comments

Table actions

1 row where author_association = "NONE" and issue = 510076368 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

  • Support queries at the table level · 1 ✖

author_association 1

  • NONE · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
548058715 https://github.com/simonw/datasette/issues/605#issuecomment-548058715 https://api.github.com/repos/simonw/datasette/issues/605 MDEyOklzc3VlQ29tbWVudDU0ODA1ODcxNQ== bsilverm 12617395 2019-10-30T18:44:41Z 2019-10-30T18:55:37Z NONE

Sure. I imagine it being pretty straight forward. Today when you click on the database, the UI displays:

-Table 1- -fields- -row count- -Table 2- -fields- -row count- Queries: -query1- -query2- .. ...

My proposal would be to display as follows:

-Table 1- -fields- -row count- Queries: -query1- -query2- .. ... -Table 2- -fields- -row count- Queries: -query1- -query2- .. ...

This way, if a given table is not present in the database, the associated queries are also not present. Today, I have a list of queries, some work, some result in errors depending on whether the dependent tables exist in the database.

Let me know if that makes sense. Thanks again!

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Support queries at the table level 510076368  

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