issue_comments
4 rows where "created_at" is on date 2019-04-07 sorted by created_at
This data as json, CSV (advanced)
Suggested facets: issue_url, updated_at (date)
user 2
- simonw 3
- psychemedia 1
id | html_url | issue_url | node_id | user | created_at ▼ | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
480552387 | https://github.com/simonw/datasette/issues/420#issuecomment-480552387 | https://api.github.com/repos/simonw/datasette/issues/420 | MDEyOklzc3VlQ29tbWVudDQ4MDU1MjM4Nw== | simonw 9599 | 2019-04-07T02:06:20Z | 2019-04-07T02:06:20Z | OWNER |
This needs access to the column names for the table. I think we can drop this entirely in favour of a new utility function - and that function can incorporate the metadata check as well. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix all the places that currently use .inspect() data 421971339 | |
480556166 | https://github.com/simonw/datasette/issues/420#issuecomment-480556166 | https://api.github.com/repos/simonw/datasette/issues/420 | MDEyOklzc3VlQ29tbWVudDQ4MDU1NjE2Ng== | simonw 9599 | 2019-04-07T03:35:59Z | 2019-04-07T03:48:14Z | OWNER | Still need to solve: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Fix all the places that currently use .inspect() data 421971339 | |
480558501 | https://github.com/simonw/datasette/issues/425#issuecomment-480558501 | https://api.github.com/repos/simonw/datasette/issues/425 | MDEyOklzc3VlQ29tbWVudDQ4MDU1ODUwMQ== | simonw 9599 | 2019-04-07T04:32:28Z | 2019-04-07T04:32:28Z | OWNER | Here's the problem: Need an else block here that adds the SQL as a hidden form field. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Submitting SQL on hide page is broken 430103450 | |
480621924 | https://github.com/simonw/sqlite-utils/issues/18#issuecomment-480621924 | https://api.github.com/repos/simonw/sqlite-utils/issues/18 | MDEyOklzc3VlQ29tbWVudDQ4MDYyMTkyNA== | psychemedia 82988 | 2019-04-07T19:31:42Z | 2019-04-07T19:31:42Z | NONE | I've just noticed that SQLite lets you IGNORE inserts that collide with a pre-existing key. This can be quite handy if you have a dataset that keeps changing in part, and you don't want to upsert and replace pre-existing PK rows but you do want to ignore collisions to existing PK rows. Do |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
.insert/.upsert/.insert_all/.upsert_all should add missing columns 413871266 |
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