issue_comments

Table actions

2 rows where issue = 605147638

✎ View and edit SQL

This data as json, CSV (advanced)

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

id ▼ html_url issue_url node_id user created_at updated_at author_association body reactions issue performed_via_github_app
618100434 https://github.com/dogsheep/dogsheep-photos/issues/8#issuecomment-618100434 https://api.github.com/repos/dogsheep/dogsheep-photos/issues/8 MDEyOklzc3VlQ29tbWVudDYxODEwMDQzNA== simonw 9599 2020-04-23T00:02:53Z 2020-04-23T00:02:53Z MEMBER I don't think it matters one way or the other - I'm storing the sha256 in the filename, so the fact that I could read the MD5 back from the list bucket operation doesn't give me any benefits. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Should I have used MD5 instead of SHA256? 605147638  
618100658 https://github.com/dogsheep/dogsheep-photos/issues/8#issuecomment-618100658 https://api.github.com/repos/dogsheep/dogsheep-photos/issues/8 MDEyOklzc3VlQ29tbWVudDYxODEwMDY1OA== simonw 9599 2020-04-23T00:03:35Z 2020-04-23T00:03:35Z MEMBER Also MD5 isn't guaranteed for the ETag: > If an object is created by either the Multipart Upload or Part Copy operation, the ETag is not an MD5 digest, regardless of the method of encryption. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Should I have used MD5 instead of SHA256? 605147638  

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