issue_comments
1 row where issue = 432870248 and "updated_at" is on date 2019-04-13
This data as json, CSV (advanced)
Suggested facets: created_at (date)
id ▼ | html_url | issue_url | node_id | user | created_at | updated_at | author_association | body | reactions | issue | performed_via_github_app |
---|---|---|---|---|---|---|---|---|---|---|---|
482872210 | https://github.com/simonw/datasette/issues/431#issuecomment-482872210 | https://api.github.com/repos/simonw/datasette/issues/431 | MDEyOklzc3VlQ29tbWVudDQ4Mjg3MjIxMA== | simonw 9599 | 2019-04-13T19:37:57Z | 2019-04-13T19:37:57Z | OWNER | You should be able to see the reload happening in the console logs: <img width="1045" alt="tmp_—_sqlite3_fixtures_db_—_80×25_and_tmp_—_Python_◂_datasette_--reload_fixtures_db_-p_8052_—_154×57_and_datasette_—_python3_7__usr_local_Cellar_pipenv_2018_11_26_libexec_bin_pipenv_shell_▸_bash_—_147×43" src="https://user-images.githubusercontent.com/9599/56084524-d347ba80-5de8-11e9-9fc8-6e902244a92a.png"> I'm doing some work at the moment to handle mutating files MUCH better - #419 - my goal is to have Datasette work against SQLite files that are being updated out-of-the box, and change the current immutable behaviour to be an option rather than the default. | {"total_count": 0, "+1": 0, "-1": 0, "laugh": 0, "hooray": 0, "confused": 0, "heart": 0, "rocket": 0, "eyes": 0} | Datasette doesn't reload when database file changes 432870248 |
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 ✖