issue_comments

Table actions

4 rows where author_association = "OWNER" and issue = 925305186 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 1

issue 1

  • Automatic type detection for CSV data · 4 ✖

author_association 1

  • OWNER · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
864354627 https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864354627 https://api.github.com/repos/simonw/sqlite-utils/issues/282 MDEyOklzc3VlQ29tbWVudDg2NDM1NDYyNw== simonw 9599 2021-06-19T04:42:03Z 2021-06-19T04:42:03Z OWNER

Demo:

curl -s 'https://api.github.com/users/simonw/repos?per_page=100' | \
  sqlite-utils memory - 'select sum(size), sum(stargazers_count) from stdin limit 1'
[{"sum(size)": 2042547, "sum(stargazers_count)": 6769}]

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Automatic type detection for CSV data 925305186  
864350407 https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864350407 https://api.github.com/repos/simonw/sqlite-utils/issues/282 MDEyOklzc3VlQ29tbWVudDg2NDM1MDQwNw== simonw 9599 2021-06-19T03:52:20Z 2021-06-19T03:52:20Z OWNER

I'll have an environment variable for --detect-types so users who really want that as the default option can turn it on.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Automatic type detection for CSV data 925305186  
864349123 https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864349123 https://api.github.com/repos/simonw/sqlite-utils/issues/282 MDEyOklzc3VlQ29tbWVudDg2NDM0OTEyMw== simonw 9599 2021-06-19T03:36:54Z 2021-06-19T03:36:54Z OWNER

I may change the default for sqlite-utils insert to detect types if I release sqlite-utils 4.0, as a backwards-incompatible change.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Automatic type detection for CSV data 925305186  
864348954 https://github.com/simonw/sqlite-utils/issues/282#issuecomment-864348954 https://api.github.com/repos/simonw/sqlite-utils/issues/282 MDEyOklzc3VlQ29tbWVudDg2NDM0ODk1NA== simonw 9599 2021-06-19T03:34:42Z 2021-06-19T03:35:46Z OWNER

I built some prototype code here for something which looks at every row in a CSV import and records the likely types: https://gist.github.com/simonw/465f9356f175d1cf86957947dff501d4

This could be used by the command-line tools to figure out what table.transform(types=...) method to use at the end.

This is a different approach to the pure SQL version I tried building in https://github.com/simonw/sqlite-utils/issues/179 - I think this is a better approach though, it's less prone to weird idiosyncrasies of SQLite types, and it's also easy for us to add on to the existing CSV import code in a way that won't require scanning the data twice.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Automatic type detection for CSV data 925305186  

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