issue_comments
7 rows where author_association = "OWNER", "created_at" is on date 2018-05-29 and user = 9599 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date), updated_at (date)
user 1
- simonw · 7 ✖
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
392969173 | https://github.com/simonw/datasette/issues/276#issuecomment-392969173 | https://api.github.com/repos/simonw/datasette/issues/276 | MDEyOklzc3VlQ29tbWVudDM5Mjk2OTE3Mw== | simonw 9599 | 2018-05-29T22:32:08Z | 2018-05-29T22:32:08Z | OWNER | The more time I spend with SpatiaLite the more convinced I am that this should be default behavior. There's nothing useful about the binary Geometry representation - it's not even valid WKB. I'm on board with WKT as the default display in HTML and GeoJSON as the default for |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handle spatialite geometry columns better 324835838 | |
392918311 | https://github.com/simonw/datasette/issues/296#issuecomment-392918311 | https://api.github.com/repos/simonw/datasette/issues/296 | MDEyOklzc3VlQ29tbWVudDM5MjkxODMxMQ== | simonw 9599 | 2018-05-29T19:44:33Z | 2018-05-29T19:44:33Z | OWNER | Should the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Per-database and per-table /-/ URL namespace 327395270 | |
392840811 | https://github.com/simonw/datasette/issues/296#issuecomment-392840811 | https://api.github.com/repos/simonw/datasette/issues/296 | MDEyOklzc3VlQ29tbWVudDM5Mjg0MDgxMQ== | simonw 9599 | 2018-05-29T16:26:27Z | 2018-05-29T19:43:23Z | OWNER | Since #275 will allow configs to be overridden at the table and database level it also makes sense to expose a completely evaluated list of configs at:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Per-database and per-table /-/ URL namespace 327395270 | |
392917380 | https://github.com/simonw/datasette/issues/298#issuecomment-392917380 | https://api.github.com/repos/simonw/datasette/issues/298 | MDEyOklzc3VlQ29tbWVudDM5MjkxNzM4MA== | simonw 9599 | 2018-05-29T19:41:59Z | 2018-05-29T19:41:59Z | OWNER | Creating URLs using concatenation as seen in |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
URLify URLs in results from custom SQL statements / views 327459829 | |
392831543 | https://github.com/simonw/datasette/issues/191#issuecomment-392831543 | https://api.github.com/repos/simonw/datasette/issues/191 | MDEyOklzc3VlQ29tbWVudDM5MjgzMTU0Mw== | simonw 9599 | 2018-05-29T15:58:33Z | 2018-05-29T15:58:33Z | OWNER | I ran an informal survey on twitter and most people were on 3.21 - https://twitter.com/simonw/status/1001487546289815553 Maybe this is from upgrading to the latest OS X release. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Figure out how to bundle a more up-to-date SQLite 310533258 | |
392822050 | https://github.com/simonw/datasette/issues/191#issuecomment-392822050 | https://api.github.com/repos/simonw/datasette/issues/191 | MDEyOklzc3VlQ29tbWVudDM5MjgyMjA1MA== | simonw 9599 | 2018-05-29T15:33:25Z | 2018-05-29T15:33:25Z | OWNER | I don't know how it happened, but I've somehow got myself into a state where my local SQLite for Python 3 on OS X is ``` ~ $ python3 Python 3.6.5 (default, Mar 30 2018, 06:41:53) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)] on darwin Type "help", "copyright", "credits" or "license" for more information.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Figure out how to bundle a more up-to-date SQLite 310533258 | |
392815673 | https://github.com/simonw/datasette/issues/276#issuecomment-392815673 | https://api.github.com/repos/simonw/datasette/issues/276 | MDEyOklzc3VlQ29tbWVudDM5MjgxNTY3Mw== | simonw 9599 | 2018-05-29T15:17:04Z | 2018-05-29T15:17:04Z | OWNER | I'm coming round to the idea that this should be baked into Datasette core - see above referenced issues for some of the explorations I've been doing around this area. Datasette should absolutely work without SpatiaLite, but it's such a huge bonus part of the SQLite ecosystem that I'm happy to ship features that take advantage of it without being relegated to plugins. I'm also becoming aware that there aren't really that many other interesting loadable extensions for SQLite. If SpatiaLite was one of dozens I'd feel that a rule that "anything dependent on an extension lives in a plugin" would make sense, but as it stands I think 99% of the time the only loadable extensions people will be using will be SpatiaLite and json1 (and json1 is available in the amalgamation anyway). |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Handle spatialite geometry columns better 324835838 |
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 4