issue_comments

Table actions

6 rows where issue = 1363440999

✎ 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
1238308213 https://github.com/simonw/datasette/issues/1804#issuecomment-1238308213 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5JzxV1 simonw 9599 2022-09-06T15:27:31Z 2022-09-06T15:27:31Z OWNER Relevant example from https://docs.datasette.io/en/stable/metadata.html#per-database-and-per-table-metadata ```json { "databases": { "database1": { "tables": { "example_table": { "sortable_columns": [ "height", "weight" ] } } } } } ``` I think this becomes `"facet_size": "..."` at the table level, to match the name of the `?_facet_size=100` querystring parameter. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  
1238309481 https://github.com/simonw/datasette/issues/1804#issuecomment-1238309481 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5Jzxpp simonw 9599 2022-09-06T15:28:35Z 2022-09-06T15:28:35Z OWNER I'm going to do this just at the table level - if you want it at the database level I would imagine usually you would be OK running `--setting default_facet_size 10` instead, since most Datasette instances only expose a single database. I may reconsider this in the future. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  
1238311565 https://github.com/simonw/datasette/issues/1804#issuecomment-1238311565 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5JzyKN simonw 9599 2022-09-06T15:30:19Z 2022-09-06T15:30:19Z OWNER Relevant code: https://github.com/simonw/datasette/blob/c9d1943aede436fa3413fd49bc56335cbda4ad07/datasette/facets.py#L102-L110 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  
1238313314 https://github.com/simonw/datasette/issues/1804#issuecomment-1238313314 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5Jzyli simonw 9599 2022-09-06T15:31:36Z 2022-09-06T15:31:36Z OWNER In that code `self.table` is the name of the current table, but can also be `None` if the faceting is being run against a custom SQL query instead (a future feature). `self.database` is the name of the current database. So reading metadata via `self.ds` should work fine. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  
1238347451 https://github.com/simonw/datasette/issues/1804#issuecomment-1238347451 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5Jz667 simonw 9599 2022-09-06T15:59:26Z 2022-09-06T15:59:26Z OWNER Still needs documentation. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  
1238773577 https://github.com/simonw/datasette/issues/1804#issuecomment-1238773577 https://api.github.com/repos/simonw/datasette/issues/1804 IC_kwDOBm6k_c5J1i9J simonw 9599 2022-09-07T00:21:56Z 2022-09-07T00:21:56Z OWNER `facet_size` is now documented here: https://docs.datasette.io/en/latest/facets.html#facets-in-metadata-json {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Ability to set a custom facet_size per table 1363440999  

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