issue_comments

Table actions

4 rows where issue = 1359557737

✎ 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
1234925616 https://github.com/simonw/datasette/issues/1798#issuecomment-1234925616 https://api.github.com/repos/simonw/datasette/issues/1798 IC_kwDOBm6k_c5Jm3gw simonw 9599 2022-09-01T23:56:33Z 2022-09-01T23:56:33Z OWNER Oh that's a classic YAML problem, I hadn't realized it would affect Datasette like this! You should be able to fix it by quoting the `off` key like this: ```yaml title: Some title description_html: |- <p>This is an experiment.</p> databases: "off": tables: products_from_owners: title: products_from_owners* description_html: |- <p>Description</p> ``` {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Parts of YAML file do not work when db name is "off" 1359557737  
1234925618 https://github.com/simonw/datasette/issues/1798#issuecomment-1234925618 https://api.github.com/repos/simonw/datasette/issues/1798 IC_kwDOBm6k_c5Jm3gy simonw 9599 2022-09-02T00:01:00Z 2022-09-02T00:01:00Z OWNER There's a thread about this here, but it doesn't have any workaround that look to me like they would be worth applying: https://stackoverflow.com/questions/36463531/pyyaml-automatically-converting-certain-keys-to-boolean-values {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Parts of YAML file do not work when db name is "off" 1359557737  
1234925621 https://github.com/simonw/datasette/issues/1798#issuecomment-1234925621 https://api.github.com/repos/simonw/datasette/issues/1798 IC_kwDOBm6k_c5Jm3g1 simonw 9599 2022-09-02T00:01:47Z 2022-09-02T00:01:47Z OWNER It's a nasty gotcha though. I'm inclined to add validation to Datasette that fails to start the server with an error if you attempt to start it with metadata that accidentally has a boolean where a database name is expected. {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Parts of YAML file do not work when db name is "off" 1359557737  
1234925975 https://github.com/simonw/datasette/issues/1798#issuecomment-1234925975 https://api.github.com/repos/simonw/datasette/issues/1798 IC_kwDOBm6k_c5Jm3mX simonw 9599 2022-09-02T00:02:53Z 2022-09-02T00:02:53Z OWNER Here's a very old issue that suggests validating metadata: - https://github.com/simonw/datasette/issues/260 {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} Parts of YAML file do not work when db name is "off" 1359557737  

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