issue_comments
20 rows where "created_at" is on date 2019-05-03 sorted by reactions
This data as json, CSV (advanced)
Suggested facets: reactions, updated_at (date)
id | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions ▼ | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
488874364 | https://github.com/simonw/datasette/pull/432#issuecomment-488874364 | https://api.github.com/repos/simonw/datasette/issues/432 | MDEyOklzc3VlQ29tbWVudDQ4ODg3NDM2NA== | simonw 9599 | 2019-05-03T00:04:23Z | 2019-05-03T00:04:23Z | OWNER | Abandoning this in favour of #445 - which contains the code from this branch but updated to incorporate recent changes in master. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Refactor facets to a class and new plugin, refs #427 432893491 | |
489060765 | https://github.com/simonw/datasette/issues/419#issuecomment-489060765 | https://api.github.com/repos/simonw/datasette/issues/419 | MDEyOklzc3VlQ29tbWVudDQ4OTA2MDc2NQ== | russss 45057 | 2019-05-03T11:07:42Z | 2019-05-03T11:07:42Z | CONTRIBUTOR | Are you planning on removing inspect entirely? I didn't spot this work before I started on datasette-geo, but ironically I think it has a use case which really needs the inspect functionality (or some replacement). Datasette-geo uses it to store the bounding box of all the geographic features in the table. This is needed when rendering the map because it avoids having to send loads of tile requests for areas which are empty. Even with relatively small datasets, calculating the bounding box seems to take around 5 seconds, so I don't think it's really feasible to do this on page load. One possible fix would be to do this on startup, and then in a thread which watches the database for changes. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Default to opening files in mutable mode, special option for immutable files 421551434 | |
489076725 | https://github.com/simonw/datasette/issues/359#issuecomment-489076725 | https://api.github.com/repos/simonw/datasette/issues/359 | MDEyOklzc3VlQ29tbWVudDQ4OTA3NjcyNQ== | simonw 9599 | 2019-05-03T12:20:38Z | 2019-05-03T12:20:38Z | OWNER | { "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Faceted browse against a JSON list of tags 349827640 | ||
489105665 | https://github.com/simonw/datasette/pull/434#issuecomment-489105665 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTEwNTY2NQ== | eyeseast 25778 | 2019-05-03T14:01:30Z | 2019-05-03T14:01:30Z | CONTRIBUTOR | This is exactly what I needed. Thank you. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 | |
489138554 | https://github.com/simonw/datasette/pull/434#issuecomment-489138554 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTEzODU1NA== | simonw 9599 | 2019-05-03T15:36:48Z | 2019-05-03T15:36:48Z | OWNER | Here's my first working deployment: https://datasette-j7hipcg4aq-uc.a.run.app/fixtures-c35b6a5/facetable?_facet_array=tags I deployed it using this:
The second time I ran the command I got an error:
So I ran the command it suggested and then everything worked:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 | |
489154360 | https://github.com/simonw/datasette/pull/434#issuecomment-489154360 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTE1NDM2MA== | simonw 9599 | 2019-05-03T16:18:18Z | 2019-05-03T16:18:18Z | OWNER | Documentation is now available here: https://datasette.readthedocs.io/en/latest/publish.html#publishing-to-google-cloud-run |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 | |
489162365 | https://github.com/simonw/datasette/pull/442#issuecomment-489162365 | https://api.github.com/repos/simonw/datasette/issues/442 | MDEyOklzc3VlQ29tbWVudDQ4OTE2MjM2NQ== | simonw 9599 | 2019-05-03T16:44:29Z | 2019-05-03T16:44:29Z | OWNER | I'm going to merge this and add a unit test. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Suppress rendering of binary data 438450757 | |
489163939 | https://github.com/simonw/datasette/pull/434#issuecomment-489163939 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTE2MzkzOQ== | rprimet 10352819 | 2019-05-03T16:49:45Z | 2019-05-03T16:50:03Z | CONTRIBUTOR |
Yes, I was able to reproduce this; I used to get prompted for a run region interactively by the Not sure which course of action is best: making |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 | |
489167692 | https://github.com/simonw/datasette/issues/446#issuecomment-489167692 | https://api.github.com/repos/simonw/datasette/issues/446 | MDEyOklzc3VlQ29tbWVudDQ4OTE2NzY5Mg== | simonw 9599 | 2019-05-03T17:02:24Z | 2019-05-03T17:02:24Z | OWNER | I looked at using namedtuples for this but hey have one major constraint: there isn't a clean way to convert them to dictionary-style JSON: https://bugs.python.org/issue30343 So something that uses a class which knows how to be rendered as JSON would be a better fit. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Define mechanism for plugins to return structured data 440134714 | |
489190440 | https://github.com/simonw/datasette/pull/447#issuecomment-489190440 | https://api.github.com/repos/simonw/datasette/issues/447 | MDEyOklzc3VlQ29tbWVudDQ4OTE5MDQ0MA== | simonw 9599 | 2019-05-03T18:13:56Z | 2019-05-03T18:13:56Z | OWNER | This appears to fix a very weird error we were getting just on Python 3.7-dev: https://travis-ci.org/simonw/datasette/jobs/527858613 That weird error boiled down to ``` { "columns": ["pk", "distance", "frequency"], "name": "units", "count": 3, "hidden": False, "foreign_keys": {"incoming": [], "outgoing": []}, "fts_table": None, "primary_keys": ["pk"], } compared to:{ "name": "units", "columns": ["pk", "distance", "frequency"], "primary_keys": ["pk"], "count": None, "hidden": False, "fts_table": None, "foreign_keys": {"incoming": [], "outgoing": []}, } ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Use dist: xenial and python: 3.7 on Travis 440159137 | |
489194450 | https://github.com/simonw/datasette/pull/442#issuecomment-489194450 | https://api.github.com/repos/simonw/datasette/issues/442 | MDEyOklzc3VlQ29tbWVudDQ4OTE5NDQ1MA== | simonw 9599 | 2019-05-03T18:26:48Z | 2019-05-03T18:26:48Z | OWNER | Demo here: https://latest.datasette.io/fixtures/binary_data I slightly tweaked the copy: |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Suppress rendering of binary data 438450757 | |
489204605 | https://github.com/simonw/datasette/issues/446#issuecomment-489204605 | https://api.github.com/repos/simonw/datasette/issues/446 | MDEyOklzc3VlQ29tbWVudDQ4OTIwNDYwNQ== | simonw 9599 | 2019-05-03T18:59:51Z | 2019-05-03T18:59:59Z | OWNER | Potential design: ```python from collections import OrderedDict class DataSpec: slots = []
class Output(DataSpec): slots = ["body", "content_type", "status_code"] ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Define mechanism for plugins to return structured data 440134714 | |
489209255 | https://github.com/simonw/datasette/issues/446#issuecomment-489209255 | https://api.github.com/repos/simonw/datasette/issues/446 | MDEyOklzc3VlQ29tbWVudDQ4OTIwOTI1NQ== | simonw 9599 | 2019-05-03T19:15:23Z | 2019-05-03T19:16:34Z | OWNER | The Alternative would be to support default values for properties of the
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Define mechanism for plugins to return structured data 440134714 | |
489221481 | https://github.com/simonw/datasette/issues/446#issuecomment-489221481 | https://api.github.com/repos/simonw/datasette/issues/446 | MDEyOklzc3VlQ29tbWVudDQ4OTIyMTQ4MQ== | russss 45057 | 2019-05-03T19:58:31Z | 2019-05-03T19:58:31Z | CONTRIBUTOR | In this particular case I don't think there's an issue making all those required. However, I suspect we might have to allow optional values at some point - my preferred solution to russss/datasette-geo#2 would need one. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Define mechanism for plugins to return structured data 440134714 | |
489222223 | https://github.com/simonw/datasette/issues/446#issuecomment-489222223 | https://api.github.com/repos/simonw/datasette/issues/446 | MDEyOklzc3VlQ29tbWVudDQ4OTIyMjIyMw== | russss 45057 | 2019-05-03T20:01:19Z | 2019-05-03T20:01:29Z | CONTRIBUTOR | Also I have a slight preference against (ab)using |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Define mechanism for plugins to return structured data 440134714 | |
489240609 | https://github.com/simonw/datasette/issues/448#issuecomment-489240609 | https://api.github.com/repos/simonw/datasette/issues/448 | MDEyOklzc3VlQ29tbWVudDQ4OTI0MDYwOQ== | simonw 9599 | 2019-05-03T21:09:13Z | 2019-05-03T21:09:13Z | OWNER | It may be that some facet implementations ( |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
_facet_array should work against views 440222719 | |
489240874 | https://github.com/simonw/datasette/pull/367#issuecomment-489240874 | https://api.github.com/repos/simonw/datasette/issues/367 | MDEyOklzc3VlQ29tbWVudDQ4OTI0MDg3NA== | simonw 9599 | 2019-05-03T21:10:13Z | 2019-05-03T21:10:13Z | OWNER | This is a neat fix, thanks! |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mark codemirror files as vendored 374675798 | |
489241377 | https://github.com/simonw/datasette/pull/367#issuecomment-489241377 | https://api.github.com/repos/simonw/datasette/issues/367 | MDEyOklzc3VlQ29tbWVudDQ4OTI0MTM3Nw== | simonw 9599 | 2019-05-03T21:12:09Z | 2019-05-03T21:12:09Z | OWNER | Before applying this fix, GitHub showed the following statistics:
Afterwards, it shows:
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Mark codemirror files as vendored 374675798 | |
489250828 | https://github.com/simonw/datasette/pull/434#issuecomment-489250828 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTI1MDgyOA== | simonw 9599 | 2019-05-03T21:50:44Z | 2019-05-03T21:50:44Z | OWNER | Since there's a useful error message I'm OK with revisiting this in a few weeks to see if they change the CLI tool. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 | |
489104146 | https://github.com/simonw/datasette/pull/434#issuecomment-489104146 | https://api.github.com/repos/simonw/datasette/issues/434 | MDEyOklzc3VlQ29tbWVudDQ4OTEwNDE0Ng== | simonw 9599 | 2019-05-03T13:56:45Z | 2019-05-03T13:56:45Z | OWNER | This is amazing - works an absolute treat. Thank you very much! |
{ "total_count": 1, "+1": 0, "-1": 0, "laugh": 0, "hooray": 1, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
"datasette publish cloudrun" command to publish to Google Cloud Run 434321685 |
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 9