issue_comments
4 rows where issue = 413867537
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 |
---|---|---|---|---|---|---|---|---|---|---|---|
496756348 | https://github.com/simonw/sqlite-utils/issues/16#issuecomment-496756348 | https://api.github.com/repos/simonw/sqlite-utils/issues/16 | MDEyOklzc3VlQ29tbWVudDQ5Njc1NjM0OA== | simonw 9599 | 2019-05-29T02:12:43Z | 2019-05-29T02:12:43Z | OWNER | For the CLI I'm thinking: sqlite-utils add-column data.db mytable col text --fk othertable id So the foreign key is added using `--fk othertable othercolumn` If the user doesn't provide the column type we can derive it from the foreign key. Can we make the `othercolumn` optional? That would be neat - then we could automatically detect it using the sole primary key of the referenced table. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | add_column() should support REFERENCES {other_table}({other_column}) 413867537 | |
496756758 | https://github.com/simonw/sqlite-utils/issues/16#issuecomment-496756758 | https://api.github.com/repos/simonw/sqlite-utils/issues/16 | MDEyOklzc3VlQ29tbWVudDQ5Njc1Njc1OA== | simonw 9599 | 2019-05-29T02:14:50Z | 2019-05-29T02:14:50Z | OWNER | Hmm... probably not: > For options, only a fixed number of arguments is supported. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | add_column() should support REFERENCES {other_table}({other_column}) 413867537 | |
496757010 | https://github.com/simonw/sqlite-utils/issues/16#issuecomment-496757010 | https://api.github.com/repos/simonw/sqlite-utils/issues/16 | MDEyOklzc3VlQ29tbWVudDQ5Njc1NzAxMA== | simonw 9599 | 2019-05-29T02:16:17Z | 2019-05-29T02:16:17Z | OWNER | In that case `--fk othertable` detects the primary key. If you want to point at a different column, use `--fk-col X` | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | add_column() should support REFERENCES {other_table}({other_column}) 413867537 | |
496787958 | https://github.com/simonw/sqlite-utils/issues/16#issuecomment-496787958 | https://api.github.com/repos/simonw/sqlite-utils/issues/16 | MDEyOklzc3VlQ29tbWVudDQ5Njc4Nzk1OA== | simonw 9599 | 2019-05-29T05:17:58Z | 2019-05-29T05:17:58Z | OWNER | Shipped this feature in sqlite-utils 1.1: https://sqlite-utils.readthedocs.io/en/latest/changelog.html#v1-1 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | add_column() should support REFERENCES {other_table}({other_column}) 413867537 |
Advanced export
JSON shape: default, array, newline-delimited, object
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]);