issue_comments

Table actions

5 rows where "created_at" is on date 2017-12-08 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 · 5 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
350323722 https://github.com/simonw/datasette/issues/154#issuecomment-350323722 https://api.github.com/repos/simonw/datasette/issues/154 MDEyOklzc3VlQ29tbWVudDM1MDMyMzcyMg== simonw 9599 2017-12-08T17:35:25Z 2017-12-08T17:35:25Z OWNER

If I do this as a querystring parameter I won't need to worry about URL routing.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette CSS should include content hash in the URL 276873891  
350302417 https://github.com/simonw/datasette/issues/154#issuecomment-350302417 https://api.github.com/repos/simonw/datasette/issues/154 MDEyOklzc3VlQ29tbWVudDM1MDMwMjQxNw== simonw 9599 2017-12-08T16:11:24Z 2017-12-08T16:11:24Z OWNER

I think I'll do this as a custom Jinja template filter. That way template authors can re-use it for their own static files if they want.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Datasette CSS should include content hash in the URL 276873891  
350301248 https://github.com/simonw/datasette/issues/141#issuecomment-350301248 https://api.github.com/repos/simonw/datasette/issues/141 MDEyOklzc3VlQ29tbWVudDM1MDMwMTI0OA== simonw 9599 2017-12-08T16:07:04Z 2017-12-08T16:07:04Z OWNER

This fix should work, please have a go with latest master and let me know if you run into any problems.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 datasette publish can fail if /tmp is on a different device 275814941  
350292364 https://github.com/simonw/datasette/issues/141#issuecomment-350292364 https://api.github.com/repos/simonw/datasette/issues/141 MDEyOklzc3VlQ29tbWVudDM1MDI5MjM2NA== simonw 9599 2017-12-08T15:33:18Z 2017-12-08T15:33:18Z OWNER

I can emulate this on OS X using a disk image (Disk Utility -> File -> New Image -> Blank Image...) - once mounted, I get the following:

>>> os.link('/tmp/hello', '/Volumes/Untitled/hello')
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 18] Cross-device link: '/tmp/hello' -> '/Volumes/Untitled/hello'

I can simulate that in a mock like this:

>>> from unittest.mock import patch
>>> @patch('os.link')
... def test_link(mock_link):
...     mock_link.side_effect = OSError
...     mock_link()
...

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 datasette publish can fail if /tmp is on a different device 275814941  
350158037 https://github.com/simonw/datasette/issues/161#issuecomment-350158037 https://api.github.com/repos/simonw/datasette/issues/161 MDEyOklzc3VlQ29tbWVudDM1MDE1ODAzNw== simonw 9599 2017-12-08T02:52:34Z 2017-12-08T02:52:34Z OWNER

That might mean your version of SQLite doesn't support that syntax. Unfortunately the version bundled with Python is a bit old - the one built by the Dockerfile in this repo should handle it though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Support WITH query  278814220  

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