issue_comments

Table actions

4 rows where issue = 1427293909 and "updated_at" is on date 2022-11-14 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

  • API explorer tool · 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
1313125870 https://github.com/simonw/datasette/issues/1871#issuecomment-1313125870 https://api.github.com/repos/simonw/datasette/issues/1871 IC_kwDOBm6k_c5ORLXu simonw 9599 2022-11-14T05:42:50Z 2022-11-14T05:42:50Z OWNER 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API explorer tool 1427293909  
1313097057 https://github.com/simonw/datasette/issues/1871#issuecomment-1313097057 https://api.github.com/repos/simonw/datasette/issues/1871 IC_kwDOBm6k_c5OREVh simonw 9599 2022-11-14T04:59:28Z 2022-11-14T04:59:28Z OWNER

In playing with the API explorer just now I realized it's way too easy to accidentally drop a table using it.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API explorer tool 1427293909  
1313072900 https://github.com/simonw/datasette/issues/1871#issuecomment-1313072900 https://api.github.com/repos/simonw/datasette/issues/1871 IC_kwDOBm6k_c5OQ-cE simonw 9599 2022-11-14T04:15:50Z 2022-11-14T04:15:50Z OWNER

For the example links - I'm going to have these at the bottom of the page so you don't have to scroll past them.

Ideally these would take the user's permissions into account. This could make the page expensive to load, but I'm going to risk it for the moment.

Something like this then:

  • data
  • /data/-/create - create table
  • /data/table1/-/insert - insert into table1
  • /data/table1/-/drop - drop table1

I won't bother with per-row demo links (for update and delete) because there could be thousands of them for each table.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API explorer tool 1427293909  
1313062699 https://github.com/simonw/datasette/issues/1871#issuecomment-1313062699 https://api.github.com/repos/simonw/datasette/issues/1871 IC_kwDOBm6k_c5OQ78r simonw 9599 2022-11-14T04:03:29Z 2022-11-14T04:12:41Z OWNER

Two things left before I close this issue:

  • [x] I want to preserve the state of the forms in the URL - probably after a #
  • [ ] Instead of hard-coding the current examples, I want to provide a list of links which populate the forms
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API explorer tool 1427293909  

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