issue_comments
5 rows where author_association = "OWNER", issue = 722816436 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: updated_at (date)
issue 1
- .extract() shouldn't extract null values · 5 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
710198162 | https://github.com/simonw/sqlite-utils/issues/186#issuecomment-710198162 | https://api.github.com/repos/simonw/sqlite-utils/issues/186 | MDEyOklzc3VlQ29tbWVudDcxMDE5ODE2Mg== | simonw 9599 | 2020-10-16T16:41:00Z | 2020-10-16T16:41:00Z | OWNER | Failing test:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.extract() shouldn't extract null values 722816436 | |
709706260 | https://github.com/simonw/sqlite-utils/issues/186#issuecomment-709706260 | https://api.github.com/repos/simonw/sqlite-utils/issues/186 | MDEyOklzc3VlQ29tbWVudDcwOTcwNjI2MA== | simonw 9599 | 2020-10-16T03:17:02Z | 2020-10-16T03:17:17Z | OWNER | Actually I think this should be an option to |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.extract() shouldn't extract null values 722816436 | |
709706065 | https://github.com/simonw/sqlite-utils/issues/186#issuecomment-709706065 | https://api.github.com/repos/simonw/sqlite-utils/issues/186 | MDEyOklzc3VlQ29tbWVudDcwOTcwNjA2NQ== | simonw 9599 | 2020-10-16T03:16:22Z | 2020-10-16T03:16:22Z | OWNER | Either way I think I'm going to need to add some SQL which uses |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.extract() shouldn't extract null values 722816436 | |
709705885 | https://github.com/simonw/sqlite-utils/issues/186#issuecomment-709705885 | https://api.github.com/repos/simonw/sqlite-utils/issues/186 | MDEyOklzc3VlQ29tbWVudDcwOTcwNTg4NQ== | simonw 9599 | 2020-10-16T03:15:39Z | 2020-10-16T03:15:39Z | OWNER | The alternative solution here would be that a single |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.extract() shouldn't extract null values 722816436 | |
709705624 | https://github.com/simonw/sqlite-utils/issues/186#issuecomment-709705624 | https://api.github.com/repos/simonw/sqlite-utils/issues/186 | MDEyOklzc3VlQ29tbWVudDcwOTcwNTYyNA== | simonw 9599 | 2020-10-16T03:14:39Z | 2020-10-16T03:14:39Z | OWNER | How should this work with extractions covering multiple columns? If there's a single column then it makes sense that a For a multiple column extraction, provided at least one of those columns is not null It should map to a record in the lookup table. Only if ALL of the extracted columns are null should the lookup value stay null. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.extract() shouldn't extract null values 722816436 |
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]);
user 1