issue_comments

Table actions

5 rows where issue = 557892819

✎ 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
580567505 https://github.com/simonw/sqlite-utils/pull/80#issuecomment-580567505 https://api.github.com/repos/simonw/sqlite-utils/issues/80 MDEyOklzc3VlQ29tbWVudDU4MDU2NzUwNQ== simonw 9599 2020-01-31T03:39:19Z 2020-01-31T03:39:19Z OWNER Still needs documentation and tests. Also I'm not certain that this should be an argument you can pass to the `.table()` constructor, need to think that over. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} on_create mechanism for after table creation 557892819  
580567604 https://github.com/simonw/sqlite-utils/pull/80#issuecomment-580567604 https://api.github.com/repos/simonw/sqlite-utils/issues/80 MDEyOklzc3VlQ29tbWVudDU4MDU2NzYwNA== simonw 9599 2020-01-31T03:39:58Z 2020-01-31T03:39:58Z OWNER Perhaps this should be called `after_create` instead of `on_create`. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} on_create mechanism for after table creation 557892819  
580567886 https://github.com/simonw/sqlite-utils/pull/80#issuecomment-580567886 https://api.github.com/repos/simonw/sqlite-utils/issues/80 MDEyOklzc3VlQ29tbWVudDU4MDU2Nzg4Ng== simonw 9599 2020-01-31T03:41:31Z 2020-01-31T03:41:31Z OWNER I think it does make sense to be able to pass it to the `.table()` constructor. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} on_create mechanism for after table creation 557892819  
580569059 https://github.com/simonw/sqlite-utils/pull/80#issuecomment-580569059 https://api.github.com/repos/simonw/sqlite-utils/issues/80 MDEyOklzc3VlQ29tbWVudDU4MDU2OTA1OQ== simonw 9599 2020-01-31T03:48:41Z 2020-01-31T03:48:41Z OWNER This may not be the right feature after all, see https://github.com/simonw/geojson-to-sqlite/issues/6#issuecomment-580569002 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} on_create mechanism for after table creation 557892819  
580584269 https://github.com/simonw/sqlite-utils/pull/80#issuecomment-580584269 https://api.github.com/repos/simonw/sqlite-utils/issues/80 MDEyOklzc3VlQ29tbWVudDU4MDU4NDI2OQ== simonw 9599 2020-01-31T05:08:04Z 2020-01-31T05:08:04Z OWNER Ditching this since it won't actually solve my problem. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} on_create mechanism for after table creation 557892819  

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