issue_comments

Table actions

3 rows where issue = 644161221

✎ 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
648440525 https://github.com/simonw/sqlite-utils/issues/117#issuecomment-648440525 https://api.github.com/repos/simonw/sqlite-utils/issues/117 MDEyOklzc3VlQ29tbWVudDY0ODQ0MDUyNQ== simonw 9599 2020-06-23T21:35:01Z 2020-06-23T21:35:01Z OWNER Here's what's missing: ``` In [11]: db.conn.execute('PRAGMA foreign_key_list(song)').fetchall() Out[11]: [(0, 0, 'album', 'songartist', 'albumartist', 'NO ACTION', 'NO ACTION', 'NONE'), (0, 1, 'album', 'songalbum', 'albumname', 'NO ACTION', 'NO ACTION', 'NONE')] ``` Compare with this code here: https://github.com/simonw/sqlite-utils/blob/d0cdaaaf00249230e847be3a3b393ee2689fbfe4/sqlite_utils/db.py#L563-L579 The first two columns returned by `PRAGMA foreign_key_list(table)` are `id` and `seq` - these show when two foreign key records are part of the same compound foreign key. `sqlite-utils` entirely ignores those at the moment. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Support for compound (composite) foreign keys 644161221  
648440634 https://github.com/simonw/sqlite-utils/issues/117#issuecomment-648440634 https://api.github.com/repos/simonw/sqlite-utils/issues/117 MDEyOklzc3VlQ29tbWVudDY0ODQ0MDYzNA== simonw 9599 2020-06-23T21:35:16Z 2020-06-23T21:35:16Z OWNER Relevant discussion: https://github.com/simonw/sqlite-generate/issues/8#issuecomment-648438056 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Support for compound (composite) foreign keys 644161221  
648442511 https://github.com/simonw/sqlite-utils/issues/117#issuecomment-648442511 https://api.github.com/repos/simonw/sqlite-utils/issues/117 MDEyOklzc3VlQ29tbWVudDY0ODQ0MjUxMQ== simonw 9599 2020-06-23T21:39:41Z 2020-06-23T21:39:41Z OWNER So there are two sides to supporting this: - Being able to sensibly introspect composite foreign keys - Being able to define composite foreign keys when creating a table {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Support for compound (composite) foreign keys 644161221  

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