issue_comments
2 rows where issue = 450032134
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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 497194179 | https://github.com/simonw/datasette/issues/495#issuecomment-497194179 | https://api.github.com/repos/simonw/datasette/issues/495 | MDEyOklzc3VlQ29tbWVudDQ5NzE5NDE3OQ== | simonw 9599 | 2019-05-30T04:04:01Z | 2019-05-30T04:04:01Z | OWNER | I think there are a few steps to solving this: * Define a variant of `?_facet_m2m={..}` that takes a JSON object which specifies which middle and destination table should be used, and via which columns * Teach the Facet `ManyToManyFacet.suggest()` method to check for multiple conflicting m2m relationships and use the new JSON URL for them. Also pick non-conflicting display names for those facets. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | facet_m2m gets confused by multiple relationships 450032134 | |
| 509038243 | https://github.com/simonw/datasette/issues/495#issuecomment-509038243 | https://api.github.com/repos/simonw/datasette/issues/495 | MDEyOklzc3VlQ29tbWVudDUwOTAzODI0Mw== | simonw 9599 | 2019-07-07T23:14:03Z | 2019-07-07T23:14:03Z | OWNER | Part of #551 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | facet_m2m gets confused by multiple relationships 450032134 |
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]);