issue_comments
8 rows where "created_at" is on date 2022-09-02 sorted by reactions
This data as json, CSV (advanced)
Suggested facets: issue_url, reactions, updated_at (date)
user 2
- simonw 7
- zaneselvans 1
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions ▼ | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
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 | |
1234926923 | https://github.com/simonw/datasette/issues/260#issuecomment-1234926923 | https://api.github.com/repos/simonw/datasette/issues/260 | IC_kwDOBm6k_c5Jm31L | simonw 9599 | 2022-09-02T00:04:26Z | 2022-09-02T00:04:45Z | OWNER | Interesting example of why this would be valuable here: - https://github.com/simonw/datasette/issues/1798 This YAML file:
```yaml
title: Some title
description_html: |-
This is an experiment. databases:
off:
tables:
products_from_owners:
title: products_from_owners
This is an experiment. ", "databases": { "false": { "tables": { "products_from_owners": { "title": "products_from_owners" } } } } } ``` Validation that caught this would have been useful. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Validate metadata.json on startup 323223872 | |
1234927627 | https://github.com/simonw/datasette/issues/260#issuecomment-1234927627 | https://api.github.com/repos/simonw/datasette/issues/260 | IC_kwDOBm6k_c5Jm4AL | simonw 9599 | 2022-09-02T00:05:43Z | 2022-09-02T00:05:43Z | OWNER | I'm inclined to consider Pydantic for this, since it is widely used now and can generate really good error messages. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Validate metadata.json on startup 323223872 | |
1235752140 | https://github.com/simonw/datasette/issues/1293#issuecomment-1235752140 | https://api.github.com/repos/simonw/datasette/issues/1293 | IC_kwDOBm6k_c5JqBTM | simonw 9599 | 2022-09-02T17:34:09Z | 2022-09-02T17:34:09Z | OWNER | Accidentally closed. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Show column metadata plus links for foreign keys on arbitrary query results 849978964 | |
1235785955 | https://github.com/simonw/datasette/issues/260#issuecomment-1235785955 | https://api.github.com/repos/simonw/datasette/issues/260 | IC_kwDOBm6k_c5JqJjj | simonw 9599 | 2022-09-02T18:18:06Z | 2022-09-02T18:18:06Z | OWNER | Did some related research work in this issue: - https://github.com/simonw/shot-scraper/issues/28 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Validate metadata.json on startup 323223872 | |
1235079469 | https://github.com/simonw/datasette/issues/260#issuecomment-1235079469 | https://api.github.com/repos/simonw/datasette/issues/260 | IC_kwDOBm6k_c5JndEt | zaneselvans 596279 | 2022-09-02T05:24:59Z | 2022-09-02T05:24:59Z | NONE | @zschira is working with Pydantic while converting between and validating JSON frictionless datapackage descriptors that annotate an SQLite DB (extracted from FERC's XBRL data) and the Datasette YAML metadata so we can publish them with Datasette. Maybe there's some overlap? We've been loving Pydantic. |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 1 } |
Validate metadata.json on startup 323223872 |
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]);
issue 3