issue_comments

Table actions

3 rows where issue = 612378203 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

issue 1

  • Question: Any fixed date for the release with the uft8-encoding fix? · 3 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
624821090 https://github.com/simonw/datasette/issues/757#issuecomment-624821090 https://api.github.com/repos/simonw/datasette/issues/757 MDEyOklzc3VlQ29tbWVudDYyNDgyMTA5MA== simonw 9599 2020-05-06T18:41:29Z 2020-05-06T18:41:29Z OWNER

OK, I just released 0.41 with that and a bunch of other stuff: https://datasette.readthedocs.io/en/latest/changelog.html#v0-41

 
{
    "total_count": 1,
    "+1": 1,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Question: Any fixed date for the release with the uft8-encoding fix? 612378203  
624798540 https://github.com/simonw/datasette/issues/757#issuecomment-624798540 https://api.github.com/repos/simonw/datasette/issues/757 MDEyOklzc3VlQ29tbWVudDYyNDc5ODU0MA== simonw 9599 2020-05-06T17:56:34Z 2020-05-06T17:56:34Z OWNER

Actually I'm going to put that release out today. I was hoping to finish #698 first but that shouldn't delay those other features any longer.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Question: Any fixed date for the release with the uft8-encoding fix? 612378203  
624798182 https://github.com/simonw/datasette/issues/757#issuecomment-624798182 https://api.github.com/repos/simonw/datasette/issues/757 MDEyOklzc3VlQ29tbWVudDYyNDc5ODE4Mg== simonw 9599 2020-05-06T17:55:50Z 2020-05-06T17:55:50Z OWNER

I'll definitely get that out this week!

For the moment a trick I often use is to put a URL to the most recent commit in my requirements.txt - e.g. https://github.com/simonw/datasette/archive/0784f2ef9d3ff6dd9df05f54cb51de29a6d11764.zip

This should be safe because nothing lands on Datasette master without the full unit test suite passing. But you're right, there's a bunch of stuff now that needs to go out in a release: https://github.com/simonw/datasette/compare/0.40...0784f2ef9d3ff6dd9df05f54cb51de29a6d11764

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Question: Any fixed date for the release with the uft8-encoding fix? 612378203  

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