issue_comments

Table actions

1 row where issue = 990367646 and user = 9599 sorted by updated_at descending

✖
✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • simonw · 1 ✖

issue 1

  • Separate out "debug" options from "root" options · 1 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
914644260 https://github.com/simonw/datasette/issues/1462#issuecomment-914644260 https://api.github.com/repos/simonw/datasette/issues/1462 IC_kwDOBm6k_c42hF0k simonw 9599 2021-09-07T21:34:32Z 2021-09-07T21:34:32Z OWNER

I think this is a setting. There are two relevant settings at the moment: "template_debug": false, "trace_debug": false, For consistence then this should be called something_debug - but do I want a single setting that exposes the _internal database and adds those debug options to the menu, or do I want those as two separate settings?

  • internal_debug to enable access to that _internal database
  • menu_debug for those menu options?
 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Separate out "debug" options from "root" options 990367646  

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