home / github

Menu
  • Search all tables
  • GraphQL API

issue_comments

Table actions
  • GraphQL API for issue_comments

2 rows where user = 14294 sorted by updated_at descending

✖
✖

✎ View and edit SQL

This data as json, CSV (advanced)

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

issue 2

  • sqlite-utils extract could handle nested objects 1
  • Add an option for specifying column names when inserting CSV data 1

user 1

  • hubgit · 2 ✖

author_association 1

  • NONE 2
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1236200834 https://github.com/simonw/sqlite-utils/issues/239#issuecomment-1236200834 https://api.github.com/repos/simonw/sqlite-utils/issues/239 IC_kwDOCGYnMM5Jru2C hubgit 14294 2022-09-03T21:26:32Z 2022-09-03T21:26:32Z NONE

I was looking for something like this today, for extracting columns containing objects (and arrays of objects) into separate tables.

Would it make sense (especially for the fields containing arrays of objects) to create a one-to-many relationship, where each row of the newly created table would contain the id of the row that originally contained it?

If the extracted objects have a unique id and are repeated, it could even create a many-to-many relationship, with a third table for the joins.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
sqlite-utils extract could handle nested objects 816526538  
1229449018 https://github.com/simonw/sqlite-utils/issues/474#issuecomment-1229449018 https://api.github.com/repos/simonw/sqlite-utils/issues/474 IC_kwDOCGYnMM5JR-c6 hubgit 14294 2022-08-28T12:40:13Z 2022-08-28T12:40:13Z NONE

Creating the table before inserting is a useful workaround, thanks. It does require figuring out the create table syntax and listing all the fields manually, though, which loses some of the magic of sqlite-utils.

I was expecting to find an option like --headers=foo,bar (or --header-row='foo\tbar', if that would be easier) - not necessarily that exact syntax, but something that would essentially be treated the same as having a header row in the file.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
Add an option for specifying column names when inserting CSV data 1353074021  

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]);
Powered by Datasette · Queries took 194.271ms · About: github-to-sqlite
  • Sort ascending
  • Sort descending
  • Facet by this
  • Hide this column
  • Show all columns
  • Show not-blank rows