issue_comments

Table actions

1 row where author_association = "OWNER", issue = 795367402 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

user 1

  • simonw · 1 ✖

issue 1

  • v0.54 500 error from sql query in custom template; code worked in v0.53; found a workaround · 1 ✖

author_association 1

  • OWNER · 1 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
769455370 https://github.com/simonw/datasette/issues/1209#issuecomment-769455370 https://api.github.com/repos/simonw/datasette/issues/1209 MDEyOklzc3VlQ29tbWVudDc2OTQ1NTM3MA== simonw 9599 2021-01-28T23:00:21Z 2021-01-28T23:00:21Z OWNER

Good catch on the workaround here. The root problem is that datasette-template-sql looks for the first available databsae if you don't provide it with a database= argument, and in Datasette 0.54 the first available database changed to being the new _internal database.

Is this a bug? I think it is - because the documented behaviour on https://docs.datasette.io/en/stable/internals.html#get-database-name is this:

name - string, optional

The name to be used for this database - this will be used in the URL path, e.g. /dbname. If not specified Datasette will pick one based on the filename or memory name.

Since the new behaviour differs from what was in the documentation I'm going to treat this as a bug and fix it.

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 v0.54 500 error from sql query in custom template; code worked in v0.53; found a workaround 795367402  

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