issue_comments
4 rows where "created_at" is on date 2020-02-29 sorted by html_url descending
This data as json, CSV (advanced)
Suggested facets: author_association, issue, updated_at (date)
id | html_url ▲ | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
592999503 | https://github.com/simonw/sqlite-utils/issues/46#issuecomment-592999503 | https://api.github.com/repos/simonw/sqlite-utils/issues/46 | MDEyOklzc3VlQ29tbWVudDU5Mjk5OTUwMw== | chrishas35 35075 | 2020-02-29T22:08:20Z | 2020-02-29T22:08:20Z | NONE | @simonw any thoughts on allow extracts to specify the lookup column name? If I'm understanding the documentation right, `.lookup()` allows you to define the "value" column (the documentation uses name), but when you use `extracts` keyword as part of `.insert()`, `.upsert()` etc. the lookup must be done against a column named "value". I have an existing lookup table that I've populated with columns "id" and "name" as opposed to "id" and "value", and seems I can't use `extracts=`, unless I'm missing something... Initial thought on how to do this would be to allow the dictionary value to be a tuple of table name column pair... so: ``` table = db.table("trees", extracts={"species_id": ("Species", "name"}) ``` I haven't dug too much into the existing code yet, but does this make sense? Worth doing? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | extracts= option for insert/update/etc 471780443 | |
592814610 | https://github.com/simonw/datasette/issues/687#issuecomment-592814610 | https://api.github.com/repos/simonw/datasette/issues/687 | MDEyOklzc3VlQ29tbWVudDU5MjgxNDYxMA== | simonw 9599 | 2020-02-29T02:08:49Z | 2020-02-29T02:08:49Z | OWNER | Eventually I can also document what to do if your plugin needs to include its own CLI tool. I'm goong it show how to ship a CLI tool with the same name as the plugin using Click and `setup.py`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Expand plugins documentation to multiple pages 572896293 | |
592814114 | https://github.com/simonw/datasette/issues/687#issuecomment-592814114 | https://api.github.com/repos/simonw/datasette/issues/687 | MDEyOklzc3VlQ29tbWVudDU5MjgxNDExNA== | simonw 9599 | 2020-02-29T02:07:03Z | 2020-02-29T02:07:03Z | OWNER | The tutorial should start by taking about development environments - how to get a new fresh copy of Datasette that you can start hacking plugins for, in a fresh virtual environment. It should then explain the `--plugins-dir` mechanism, and show how to use it to create a simple plugin that adds a custom SQL function. Does `--reload` work against plugins in the `plugins/` directory? It should. Then it should demonstrate a more complex plugin that uses the `datasette` argument to render a template. It should promote the next page which lists the plugin hooks. The hooks page should include links next to each hook to examples of plugins that use them. The packaging page can explain `setup.py` for distributing packages (let's not bother explaining single modules) and also needs to show how to bundle package data such as templates. It should also show how to use `pip install -e .[test]` for development, and mention that this works with `--reload`. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Expand plugins documentation to multiple pages 572896293 | |
592798079 | https://github.com/simonw/datasette/issues/649#issuecomment-592798079 | https://api.github.com/repos/simonw/datasette/issues/649 | MDEyOklzc3VlQ29tbWVudDU5Mjc5ODA3OQ== | simonw 9599 | 2020-02-29T01:00:16Z | 2020-02-29T01:00:16Z | OWNER | I tried this out in https://github.com/simonw/datasette/commit/34bc16aa591a2f02b2bb33277d33e5bccfb95569 with an upper limit of 100MB and it worked an absolute treat against my personal Dogsheep. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Reduce table counts on index page with many databases 534530973 |
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]);
created_at (date) 1 ✖