issue_comments

Table actions

4 rows where author_association = "OWNER", issue = 706001517 and user = 9599 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

  • simonw · 4 ✖

issue 1

  • Idea: conversions= could take Python functions · 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
997502242 https://github.com/simonw/sqlite-utils/issues/163#issuecomment-997502242 https://api.github.com/repos/simonw/sqlite-utils/issues/163 IC_kwDOCGYnMM47dK0i simonw 9599 2021-12-20T00:56:45Z 2021-12-20T00:56:52Z OWNER

Maybe sqlite-utils should absorb all of the functionality from sqlite-transform - having two separate tools doesn't necessarily make sense.

I implemented that in: - #251

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Idea: conversions= could take Python functions 706001517  
708695369 https://github.com/simonw/sqlite-utils/issues/163#issuecomment-708695369 https://api.github.com/repos/simonw/sqlite-utils/issues/163 MDEyOklzc3VlQ29tbWVudDcwODY5NTM2OQ== simonw 9599 2020-10-14T22:32:39Z 2020-10-14T22:32:39Z OWNER

sqlite-utils convert my.db mytable mycolumn could become the new sqlite-transform. The sub-command could take --code but could also take --parsedate and --parsedatetime options.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Idea: conversions= could take Python functions 706001517  
708693290 https://github.com/simonw/sqlite-utils/issues/163#issuecomment-708693290 https://api.github.com/repos/simonw/sqlite-utils/issues/163 MDEyOklzc3VlQ29tbWVudDcwODY5MzI5MA== simonw 9599 2020-10-14T22:26:50Z 2020-10-14T22:27:48Z OWNER

This could even be exposed as a feature of the CLI tool - similar to how sqlite-transform works: https://github.com/simonw/sqlite-transform

$ sqlite-transform lambda my.db mytable mycolumn --code='str(value).upper()'

Maybe sqlite-utils should absorb all of the functionality from sqlite-transform - having two separate tools doesn't necessarily make sense.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Idea: conversions= could take Python functions 706001517  
696465788 https://github.com/simonw/sqlite-utils/issues/163#issuecomment-696465788 https://api.github.com/repos/simonw/sqlite-utils/issues/163 MDEyOklzc3VlQ29tbWVudDY5NjQ2NTc4OA== simonw 9599 2020-09-22T01:33:04Z 2020-09-22T01:33:04Z OWNER

This would apply to .transform() in #114 too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Idea: conversions= could take Python functions 706001517  

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