issue_comments
6 rows where "created_at" is on date 2019-12-22 and reactions = "{"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0}"
This data as json, CSV (advanced)
Suggested facets: issue_url
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
568268746 | https://github.com/simonw/datasette/issues/651#issuecomment-568268746 | https://api.github.com/repos/simonw/datasette/issues/651 | MDEyOklzc3VlQ29tbWVudDU2ODI2ODc0Ng== | simonw 9599 | 2019-12-22T14:37:37Z | 2019-12-22T14:37:37Z | OWNER | I've not yet been able to figure out what the escaping rule are for FTS5 queries. If we figure out how those work maybe we can bundle them as a custom function? select ... where docs_fts match fts_escape(:search) | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | fts5 syntax error when using punctuation 539590148 | |
568269476 | https://github.com/simonw/datasette/issues/651#issuecomment-568269476 | https://api.github.com/repos/simonw/datasette/issues/651 | MDEyOklzc3VlQ29tbWVudDU2ODI2OTQ3Ng== | simonw 9599 | 2019-12-22T14:46:37Z | 2019-12-22T14:47:03Z | OWNER | https://stackoverflow.com/a/43756146 says that an escaping mechanism that works is this one: select * from blah where term match '"bacon" "and" "eggs"' So split on whitespace and then encapsulate each search term in double quotes. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | fts5 syntax error when using punctuation 539590148 | |
568274520 | https://github.com/simonw/datasette/issues/654#issuecomment-568274520 | https://api.github.com/repos/simonw/datasette/issues/654 | MDEyOklzc3VlQ29tbWVudDU2ODI3NDUyMA== | simonw 9599 | 2019-12-22T15:51:58Z | 2019-12-22T15:51:58Z | OWNER | Proof of concept: ```diff diff --git a/datasette/views/base.py b/datasette/views/base.py index 5182479..39d1f77 100644 --- a/datasette/views/base.py +++ b/datasette/views/base.py @@ -1,6 +1,7 @@ import asyncio import csv import itertools +import json import re import time import urllib @@ -138,28 +139,31 @@ class BaseView(AsgiView): ) extra_template_vars.update(extra_vars) + template_context = { + **context, + **{ + "app_css_hash": self.ds.app_css_hash(), + "select_templates": select_templates, + "zip": zip, + "body_scripts": body_scripts, + "extra_css_urls": self._asset_urls( + "extra_css_urls", template, context + ), + "extra_js_urls": self._asset_urls( + "extra_js_urls", template, context + ), + "format_bytes": format_bytes, + "database_url": self.database_url, + "database_color": self.database_color, + }, + **extra_template_vars, + } + if request.args.get("_context"): + return Response.html("<pre>{}</pre>".format( + escape(json.dumps(template_context, default=repr, indent=4)) + )) return Response.html( - await template.render_async( - { - **context, - **{ - "app_css_hash": self.ds.app_css_hash(), - "select_templates": select_templates, - "zip": zip, - "body_scripts": body_scripts, - "extra_css_urls": self._asset_urls( - "extra_css_urls", template, context - ), - "extra_js_urls": self._asset_urls( - "extra_js_urls", template, context - … | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Template debug mode that outputs template context 541467590 | |
568274570 | https://github.com/simonw/datasette/issues/654#issuecomment-568274570 | https://api.github.com/repos/simonw/datasette/issues/654 | MDEyOklzc3VlQ29tbWVudDU2ODI3NDU3MA== | simonw 9599 | 2019-12-22T15:52:43Z | 2019-12-22T15:52:43Z | OWNER | One problem with this: what if secrets end up being dumped out in this debug view? This won't happen with default Datasette but could potentially happen with a plugin. This feature should be opt-in - maybe a `template_debug:1` config setting. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Template debug mode that outputs template context 541467590 | |
568276310 | https://github.com/simonw/datasette/issues/577#issuecomment-568276310 | https://api.github.com/repos/simonw/datasette/issues/577 | MDEyOklzc3VlQ29tbWVudDU2ODI3NjMxMA== | simonw 9599 | 2019-12-22T16:10:31Z | 2019-12-22T16:10:31Z | OWNER | The code in question currently lives in `BaseView.render()`: https://github.com/simonw/datasette/blob/d54318fc7f2565e6121920ce1ea9cb8b700e629a/datasette/views/base.py#L106-L163 Should `datasette.render_template()` do exactly this, or should it be slightly different? Plugins need the option to not pass a `request` object - so maybe that parameter becomes optional. Perhaps plugins should be able to render templates without other plugins getting to inject their own variables? Does it always make sense to dump in all of those extra template context variables? | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Utility mechanism for plugins to render templates 497171390 | |
568276548 | https://github.com/simonw/datasette/issues/654#issuecomment-568276548 | https://api.github.com/repos/simonw/datasette/issues/654 | MDEyOklzc3VlQ29tbWVudDU2ODI3NjU0OA== | simonw 9599 | 2019-12-22T16:13:11Z | 2019-12-22T16:13:11Z | OWNER | Documentation: https://datasette.readthedocs.io/en/latest/config.html#template-debug Demos: * https://latest.datasette.io/?_context=1 * https://latest.datasette.io/fixtures?_context=1 * https://latest.datasette.io/fixtures/roadside_attractions?_context=1 | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Template debug mode that outputs template context 541467590 |
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 ✖