issue_comments

Table actions

3 rows where author_association = "OWNER", "created_at" is on date 2019-10-16 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: issue_url, created_at (date), updated_at (date)

user 1

  • simonw · 3 ✖

author_association 1

  • OWNER · 3 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
542872388 https://github.com/simonw/datasette/issues/597#issuecomment-542872388 https://api.github.com/repos/simonw/datasette/issues/597 MDEyOklzc3VlQ29tbWVudDU0Mjg3MjM4OA== simonw 9599 2019-10-16T20:13:38Z 2019-10-16T20:13:38Z OWNER

I encountered this bug in my own private instance of Datasette running behind an nginx proxy.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977  
542872267 https://github.com/simonw/datasette/issues/597#issuecomment-542872267 https://api.github.com/repos/simonw/datasette/issues/597 MDEyOklzc3VlQ29tbWVudDU0Mjg3MjI2Nw== simonw 9599 2019-10-16T20:13:21Z 2019-10-16T20:13:21Z OWNER

$ echo '{"hello": "world"}' | sqlite-utils insert foo.db hello - $ echo '{"hello": "world"}' | sqlite-utils insert foo-bar.db hello - $ datasette publish now \ --about_url=https://github.com/simonw/datasette/issues/597 \ --title="Issue #597" \ --alias=datasette-issue-597 \ foo.db foo-bar.db This failed to replicate the issue. https://datasette-issue-597.now.sh/ is working as it should.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 If you have databases called foo.db and foo-bar.db you cannot visit /foo-bar 508070977  
542462126 https://github.com/simonw/datasette/issues/596#issuecomment-542462126 https://api.github.com/repos/simonw/datasette/issues/596 MDEyOklzc3VlQ29tbWVudDU0MjQ2MjEyNg== simonw 9599 2019-10-16T00:45:45Z 2019-10-16T00:45:45Z OWNER

This means moving away from select *. I've been thinking this would be worthwhile anyway, since that way when you click "Edit SQL" you'll get a more useful SQL statement to start hacking away at.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle really wide tables better 507454958  

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