issue_comments
10 rows where author_association = "OWNER" and "updated_at" is on date 2017-12-07 sorted by user
This data as json, CSV (advanced)
id | html_url | issue_url | node_id | user ▼ | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
349860851 | https://github.com/simonw/datasette/issues/135#issuecomment-349860851 | https://api.github.com/repos/simonw/datasette/issues/135 | MDEyOklzc3VlQ29tbWVudDM0OTg2MDg1MQ== | simonw 9599 | 2017-12-07T04:37:59Z | 2017-12-07T04:37:59Z | OWNER | I'm testing this like so: datasette ~/Dropbox/Development/timezones-api/timezones.db --reload --load-extension /usr/local/lib/mod_spatialite.dylib | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ?_search=x should work if used directly against a FTS virtual table 275179724 | |
349861461 | https://github.com/simonw/datasette/issues/135#issuecomment-349861461 | https://api.github.com/repos/simonw/datasette/issues/135 | MDEyOklzc3VlQ29tbWVudDM0OTg2MTQ2MQ== | simonw 9599 | 2017-12-07T04:43:12Z | 2017-12-07T04:43:12Z | OWNER | This query looks like it does the right thing: select * from sqlite_master where rootpage = 0 and ( sql like '%VIRTUAL TABLE%USING FTS%content="ElementaryGeometries"%' or ( tbl_name = "ElementaryGeometries" and sql like '%VIRTUAL TABLE%USING FTS%' ) ) Against a table that should not be shown as FTS: https://timezones-now-hrjgkinozh.now.sh/timezones-0d61a90?sql=++++++++select+*+from+sqlite_master%0D%0A++++++++++++where+rootpage+%3D+0%0D%0A++++++++++++and+%28%0D%0A++++++++++++++++sql+like+%27%25VIRTUAL+TABLE%25USING+FTS%25content%3D%22ElementaryGeometries%22%25%27%0D%0A++++++++++++++++or+%28%0D%0A++++++++++++++++++tbl_name+%3D+%22ElementaryGeometries%22%0D%0A++++++++++++++++++and+sql+like+%27%25VIRTUAL+TABLE%25USING+FTS%25%27%0D%0A++++++++++++++++%29%0D%0A++++++++++++%29+ Against a table that SHOULD match: https://sf-trees.now.sh/sf-trees-ebc2ad9?sql=++++++++select+*+from+sqlite_master%0D%0A++++++++++++where+rootpage+%3D+0%0D%0A++++++++++++and+%28%0D%0A++++++++++++++++sql+like+%27%25VIRTUAL+TABLE%25USING+FTS%25content%3D%22Street_Tree_List_fts%22%25%27%0D%0A++++++++++++++++or+%28%0D%0A++++++++++++++++++tbl_name+%3D+%22Street_Tree_List_fts%22%0D%0A++++++++++++++++++and+sql+like+%27%25VIRTUAL+TABLE%25USING+FTS%25%27%0D%0A++++++++++++++++%29%0D%0A++++++++++++%29+ | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | ?_search=x should work if used directly against a FTS virtual table 275179724 | |
349868849 | https://github.com/simonw/datasette/issues/158#issuecomment-349868849 | https://api.github.com/repos/simonw/datasette/issues/158 | MDEyOklzc3VlQ29tbWVudDM0OTg2ODg0OQ== | simonw 9599 | 2017-12-07T05:41:08Z | 2017-12-07T05:41:08Z | OWNER | I'm happy with this - we have extra_head, content, body_class and title blocks which should provide enough hooks for most reasonable customizations. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ensure default templates are designed to be extended 278190981 | |
349874052 | https://github.com/simonw/datasette/issues/153#issuecomment-349874052 | https://api.github.com/repos/simonw/datasette/issues/153 | MDEyOklzc3VlQ29tbWVudDM0OTg3NDA1Mg== | simonw 9599 | 2017-12-07T06:17:33Z | 2017-12-07T06:17:33Z | OWNER | In #159 I added a mechanism for easily customizing per-column displays, and I've added documentation showing an example of using this mechanism to set certain columns to display as unescaped HTML: http://datasette.readthedocs.io/en/latest/custom_templates.html#custom-templates This fixes item 3, so I'm closing this ticket! | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Ability to customize presentation of specific columns in HTML view 276842536 | |
349874709 | https://github.com/simonw/datasette/issues/164#issuecomment-349874709 | https://api.github.com/repos/simonw/datasette/issues/164 | MDEyOklzc3VlQ29tbWVudDM0OTg3NDcwOQ== | simonw 9599 | 2017-12-07T06:22:10Z | 2017-12-07T06:22:10Z | OWNER | Example usage: datasette skeleton parlgov.db -m parlgov.json Generates a `parlgov.json` file containing this: { "title": null, "description": null, "description_html": null, "license": null, "license_url": null, "source": null, "source_url": null, "databases": { "parlgov": { "title": null, "description": null, "description_html": null, "license": null, "license_url": null, "source": null, "source_url": null, "queries": {}, "tables": { "info_data_source": { "title": null, "description": null, "description_html": null, "license": null, "license_url": null, "source": null, "source_url": null }, "external_party_castles_mair": { "title": null, "description": null, "description_html": null, "license": null, "license_url": null, "source": null, "source_url": null }, "external_party_chess": { "title": null, "description": null, "description_html": null, "license": null, "license_url": null, "source": null, "source_url": null }, "external_party_huber_inglehart": { "title": null, "description": null, "description_html": null, … | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | datasette skeleton command for kick-starting database and table metadata 280013907 | |
349874844 | https://github.com/simonw/datasette/issues/164#issuecomment-349874844 | https://api.github.com/repos/simonw/datasette/issues/164 | MDEyOklzc3VlQ29tbWVudDM0OTg3NDg0NA== | simonw 9599 | 2017-12-07T06:22:58Z | 2017-12-07T06:22:58Z | OWNER | This metadata doesn't yet do anything - need to implement #165 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | datasette skeleton command for kick-starting database and table metadata 280013907 | |
350026183 | https://github.com/simonw/datasette/issues/165#issuecomment-350026183 | https://api.github.com/repos/simonw/datasette/issues/165 | MDEyOklzc3VlQ29tbWVudDM1MDAyNjE4Mw== | simonw 9599 | 2017-12-07T16:47:46Z | 2017-12-07T16:47:46Z | OWNER | Here's an example metadata.json file illustrating custom per-database and per- table metadata: { "title": "Overall datasette title", "description_html": "This is a <em>description with HTML</em>.", "databases": { "db1": { "title": "First database", "description": "This is a string description & has no HTML", "license_url": "http://example.com/", "license": "The example license", "queries": { "canned_query": "select * from table1 limit 3;" }, "tables": { "table1": { "title": "Custom title for table1", "description": "Tables can have descriptions too", "source": "This has a custom source", "source_url": "http://example.com/" } } } } } | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | metadata.json support for per-database and per-table information 280014287 | |
350026452 | https://github.com/simonw/datasette/issues/165#issuecomment-350026452 | https://api.github.com/repos/simonw/datasette/issues/165 | MDEyOklzc3VlQ29tbWVudDM1MDAyNjQ1Mg== | simonw 9599 | 2017-12-07T16:48:34Z | 2017-12-07T16:48:34Z | OWNER | Needs documentation, see #166 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | metadata.json support for per-database and per-table information 280014287 | |
350035741 | https://github.com/simonw/datasette/issues/166#issuecomment-350035741 | https://api.github.com/repos/simonw/datasette/issues/166 | MDEyOklzc3VlQ29tbWVudDM1MDAzNTc0MQ== | simonw 9599 | 2017-12-07T17:20:35Z | 2017-12-07T17:20:35Z | OWNER | http://datasette.readthedocs.io/en/latest/metadata.html | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Documentation for metadata.json and datasette skeleton 280023225 | |
350125953 | https://github.com/simonw/datasette/issues/167#issuecomment-350125953 | https://api.github.com/repos/simonw/datasette/issues/167 | MDEyOklzc3VlQ29tbWVudDM1MDEyNTk1Mw== | simonw 9599 | 2017-12-07T23:25:28Z | 2017-12-07T23:25:28Z | OWNER | My column/row HTML display logic has got way too convoluted. This is a sign I need to add proper unit tests for it and clean it up. The complexity comes from: * Displaying a rowid for tables that do not have a primary key * Showing an additional Link column for rows with a primary key * Not displaying that Link column on the individual row pages * Trying to get foreign keys working correctly in all cases, e.g. #152 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Nasty bug: last column not being correctly displayed 280315352 |
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]);
updated_at (date) 1 ✖