issue_comments
8 rows where "created_at" is on date 2018-05-25 sorted by html_url
This data as json, CSV (advanced)
Suggested facets: issue_url, updated_at (date)
id | html_url ▼ | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
392212119 | https://github.com/simonw/datasette/issues/259#issuecomment-392212119 | https://api.github.com/repos/simonw/datasette/issues/259 | MDEyOklzc3VlQ29tbWVudDM5MjIxMjExOQ== | simonw 9599 | 2018-05-25T23:22:26Z | 2018-05-25T23:22:26Z | OWNER | This should detect any table which can be linked to the current table via some other table, based on the other table having a foreign key to them both. These join tables could be arbitrarily complicated. They might have foreign keys to more than two other tables, maybe even multiple foreign keys to the same column. Ideally M2M defection would catch all of these cases. Maybe the resulting inspect data looks something like this:
Let's ignore compound primary keys: we k it detect m2m relationships where the join table has foreign keys to a single primary key on the other two tables. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
inspect() should detect many-to-many relationships 322787470 | |
392214791 | https://github.com/simonw/datasette/issues/259#issuecomment-392214791 | https://api.github.com/repos/simonw/datasette/issues/259 | MDEyOklzc3VlQ29tbWVudDM5MjIxNDc5MQ== | simonw 9599 | 2018-05-25T23:43:15Z | 2018-07-29T00:56:03Z | OWNER | We may need to derive a usable name for each of these relationships that can be used in eg querystring parameters. The name of the join table is a reasonable choice here. Say the join table is called But what if |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
inspect() should detect many-to-many relationships 322787470 | |
392121905 | https://github.com/simonw/datasette/issues/267#issuecomment-392121905 | https://api.github.com/repos/simonw/datasette/issues/267 | MDEyOklzc3VlQ29tbWVudDM5MjEyMTkwNQ== | simonw 9599 | 2018-05-25T17:08:14Z | 2018-05-25T17:08:14Z | OWNER | See also #286 |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation for URL hashing, redirects and cache policy 323716411 | |
392118755 | https://github.com/simonw/datasette/issues/272#issuecomment-392118755 | https://api.github.com/repos/simonw/datasette/issues/272 | MDEyOklzc3VlQ29tbWVudDM5MjExODc1NQ== | simonw 9599 | 2018-05-25T16:56:40Z | 2018-06-05T16:01:13Z | OWNER | Thinking about this further, maybe I should embrace ASGI turtles-all-the-way-down and teach each datasette view class to take a scope to the constructor and act entirely as an ASGI component. Would be a nice way of diving deep into ASGI and I can add utility helpers for things like querystring evaluation as I need them. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Port Datasette to ASGI 324188953 | |
391912392 | https://github.com/simonw/datasette/issues/284#issuecomment-391912392 | https://api.github.com/repos/simonw/datasette/issues/284 | MDEyOklzc3VlQ29tbWVudDM5MTkxMjM5Mg== | simonw 9599 | 2018-05-25T01:16:56Z | 2018-05-25T01:17:13Z | OWNER |
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to enable/disable specific features via --config 326182814 | |
391950691 | https://github.com/simonw/datasette/issues/284#issuecomment-391950691 | https://api.github.com/repos/simonw/datasette/issues/284 | MDEyOklzc3VlQ29tbWVudDM5MTk1MDY5MQ== | simonw 9599 | 2018-05-25T06:01:23Z | 2018-05-25T06:05:02Z | OWNER | Demo:
https://datasette-demo-284.now.sh/ Note the following:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Ability to enable/disable specific features via --config 326182814 | |
392121500 | https://github.com/simonw/datasette/issues/286#issuecomment-392121500 | https://api.github.com/repos/simonw/datasette/issues/286 | MDEyOklzc3VlQ29tbWVudDM5MjEyMTUwMA== | simonw 9599 | 2018-05-25T17:06:46Z | 2018-05-25T17:06:46Z | OWNER | A few extra thoughts:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Database hash should include current datasette version 326599525 | |
392121743 | https://github.com/simonw/datasette/issues/286#issuecomment-392121743 | https://api.github.com/repos/simonw/datasette/issues/286 | MDEyOklzc3VlQ29tbWVudDM5MjEyMTc0Mw== | simonw 9599 | 2018-05-25T17:07:36Z | 2018-05-25T17:07:36Z | OWNER | This is also a great excuse to finally write up some detailed documentation on Datasette's caching strategy |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Database hash should include current datasette version 326599525 |
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 5