issue_comments

Table actions

3 rows where issue = 838148087 and user = 9599 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: updated_at (date)

user 1

  • simonw · 3 ✖

issue 1

  • Handle byte order marks (BOMs) in CSV files · 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
850772428 https://github.com/simonw/sqlite-utils/issues/250#issuecomment-850772428 https://api.github.com/repos/simonw/sqlite-utils/issues/250 MDEyOklzc3VlQ29tbWVudDg1MDc3MjQyOA== simonw 9599 2021-05-29T05:16:02Z 2021-05-29T05:28:57Z OWNER

I needed to find some CSV files on my computer with a BOM at the beginning - I figured out this recipe: % rg -U -E none '^(?-u:\xEF\xBB\xBF)' --glob '*.csv' . TIL here: https://til.simonwillison.net/bash/finding-bom-csv-files-with-ripgrep

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle byte order marks (BOMs) in CSV files 838148087  
850771264 https://github.com/simonw/sqlite-utils/issues/250#issuecomment-850771264 https://api.github.com/repos/simonw/sqlite-utils/issues/250 MDEyOklzc3VlQ29tbWVudDg1MDc3MTI2NA== simonw 9599 2021-05-29T05:06:13Z 2021-05-29T05:06:13Z OWNER

The other option is to check if the file starts with codecs.BOM_UTF8 - which is b'\xef\xbb\xbf'.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle byte order marks (BOMs) in CSV files 838148087  
850771017 https://github.com/simonw/sqlite-utils/issues/250#issuecomment-850771017 https://api.github.com/repos/simonw/sqlite-utils/issues/250 MDEyOklzc3VlQ29tbWVudDg1MDc3MTAxNw== simonw 9599 2021-05-29T05:04:28Z 2021-05-29T05:04:28Z OWNER

https://stackoverflow.com/a/44573867/6083 says:

There is no reason to check if a BOM exists or not, utf-8-sig manages that for you and behaves exactly as utf-8 if the BOM does not exist

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Handle byte order marks (BOMs) in CSV files 838148087  

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