issue_comments
9 rows where "updated_at" is on date 2019-06-25 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: issue_url, created_at (date)
user 3
- simonw 6
- chrismp 2
- nathancahill 1
id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
505635729 | https://github.com/simonw/datasette/issues/498#issuecomment-505635729 | https://api.github.com/repos/simonw/datasette/issues/498 | MDEyOklzc3VlQ29tbWVudDUwNTYzNTcyOQ== | simonw 9599 | 2019-06-25T21:48:46Z | 2019-06-25T21:48:46Z | OWNER | Hmmm... you know I think I actually need this for my https://github.com/simonw/fara-datasette project... |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Full text search of all tables at once? 451513541 | |
505424665 | https://github.com/simonw/datasette/pull/529#issuecomment-505424665 | https://api.github.com/repos/simonw/datasette/issues/529 | MDEyOklzc3VlQ29tbWVudDUwNTQyNDY2NQ== | nathancahill 1383872 | 2019-06-25T12:35:07Z | 2019-06-25T12:35:07Z | NONE | Opps, wrote this late last night, didn't see you'd already worked on the issue. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Use keyed rows - fixes #521 460396952 | |
505422550 | https://github.com/simonw/datasette/issues/521#issuecomment-505422550 | https://api.github.com/repos/simonw/datasette/issues/521 | MDEyOklzc3VlQ29tbWVudDUwNTQyMjU1MA== | simonw 9599 | 2019-06-25T12:28:48Z | 2019-06-25T12:28:48Z | OWNER | Still needed before merge: documentation! I can expand this section: https://datasette.readthedocs.io/en/stable/custom_templates.html#custom-templates |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Easier way of creating custom row templates 459621683 | |
505421892 | https://github.com/simonw/datasette/issues/521#issuecomment-505421892 | https://api.github.com/repos/simonw/datasette/issues/521 | MDEyOklzc3VlQ29tbWVudDUwNTQyMTg5Mg== | simonw 9599 | 2019-06-25T12:26:54Z | 2019-06-25T12:26:54Z | OWNER | This is starting to shape up. Example template:
```
{% for row in display_rows %}
{{ row["First_Name"] }} {{ row["Last_Name"] }}{% if row["Link_to_Photo"] %} {% endif %} {% for cell in row.cells[3:] %} {% if cell.raw and cell.column != "createdTime" %}{{ cell.column }}: {{ cell.value }} {% endif %} {% endfor %}{% endfor %} ``` |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Easier way of creating custom row templates 459621683 | |
505405030 | https://github.com/simonw/datasette/issues/521#issuecomment-505405030 | https://api.github.com/repos/simonw/datasette/issues/521 | MDEyOklzc3VlQ29tbWVudDUwNTQwNTAzMA== | simonw 9599 | 2019-06-25T11:34:21Z | 2019-06-25T11:34:21Z | OWNER | Actually I'm OK here - |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Easier way of creating custom row templates 459621683 | |
505280611 | https://github.com/simonw/datasette/issues/521#issuecomment-505280611 | https://api.github.com/repos/simonw/datasette/issues/521 | MDEyOklzc3VlQ29tbWVudDUwNTI4MDYxMQ== | simonw 9599 | 2019-06-25T04:46:10Z | 2019-06-25T04:46:10Z | OWNER | Of course I can't do it in this part of he code because it's constructing plain JSON objects here. I'll need to do it in the section that prepares special objects for the HTML. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Easier way of creating custom row templates 459621683 | |
505279560 | https://github.com/simonw/datasette/issues/521#issuecomment-505279560 | https://api.github.com/repos/simonw/datasette/issues/521 | MDEyOklzc3VlQ29tbWVudDUwNTI3OTU2MA== | simonw 9599 | 2019-06-25T04:40:16Z | 2019-06-25T04:40:38Z | OWNER | I think the trick is to redefine what a "cell_row" is. Each row is currently a list of cells: I can redefine the row (the |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Easier way of creating custom row templates 459621683 | |
505232675 | https://github.com/simonw/datasette/issues/514#issuecomment-505232675 | https://api.github.com/repos/simonw/datasette/issues/514 | MDEyOklzc3VlQ29tbWVudDUwNTIzMjY3NQ== | chrismp 7936571 | 2019-06-25T00:43:12Z | 2019-06-25T00:43:12Z | NONE | Yep, that worked to get the site up and running at ``` !/bin/bash/home/chris/Env/datasette/bin/datasette serve -h 0.0.0.0 -p 80 /home/chris/digital-library/databases/*.db --cors --metadata /home/chris/digital-library/metadata.json ``` I got this error.
|
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Documentation with recommendations on running Datasette in production without using Docker 459397625 | |
505228873 | https://github.com/simonw/datasette/issues/498#issuecomment-505228873 | https://api.github.com/repos/simonw/datasette/issues/498 | MDEyOklzc3VlQ29tbWVudDUwNTIyODg3Mw== | chrismp 7936571 | 2019-06-25T00:21:17Z | 2019-06-25T00:21:17Z | NONE | Eh, I'm not concerned with a relevance score right now. I think I'd be fine with a search whose results show links to data tables with at least one result. |
{ "total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0 } |
Full text search of all tables at once? 451513541 |
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