issue_comments
6 rows where issue = 612382643 sorted by updated_at descending
This data as json, CSV (advanced)
Suggested facets: reactions, created_at (date), updated_at (date)
issue 1
- Question: Access to immutable database-path · 6 ✖
| id | html_url | issue_url | node_id | user | created_at | updated_at ▲ | author_association | body | reactions | issue | performed_via_github_app |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 635195322 | https://github.com/simonw/datasette/issues/758#issuecomment-635195322 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYzNTE5NTMyMg== | clausjuhl 2181410 | 2020-05-28T08:23:27Z | 2020-05-28T08:23:27Z | NONE | @simonw I would prefer just the 7 character hash. No need to make the urls any longer than they need to be :) |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 | |
| 635102675 | https://github.com/simonw/datasette/issues/758#issuecomment-635102675 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYzNTEwMjY3NQ== | simonw 9599 | 2020-05-28T05:04:07Z | 2020-05-28T05:04:07Z | OWNER | @clausjuhl do you have any thoughts on what would be most useful for you in these JSON responses? The full |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 | |
| 634951605 | https://github.com/simonw/datasette/issues/758#issuecomment-634951605 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYzNDk1MTYwNQ== | simonw 9599 | 2020-05-27T21:29:19Z | 2020-05-27T21:29:19Z | OWNER | But... https://datasette-hash-urls-j7hipcg4aq-uw.a.run.app/fixtures-bda7daa.json doesn't expose that hash:
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 | |
| 634950200 | https://github.com/simonw/datasette/issues/758#issuecomment-634950200 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYzNDk1MDIwMA== | simonw 9599 | 2020-05-27T21:26:37Z | 2020-05-27T21:26:37Z | OWNER | https://latest.datasette.io/.json currently returns:
I published
https://datasette-hash-urls-j7hipcg4aq-uw.a.run.app/.json
|
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 | |
| 624797119 | https://github.com/simonw/datasette/issues/758#issuecomment-624797119 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYyNDc5NzExOQ== | simonw 9599 | 2020-05-06T17:53:46Z | 2020-05-06T17:53:46Z | OWNER | It's interesting to hear from someone who's using this feature - I'm considering moving it out into a plugin #647. |
{
"total_count": 1,
"+1": 1,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 | |
| 624796685 | https://github.com/simonw/datasette/issues/758#issuecomment-624796685 | https://api.github.com/repos/simonw/datasette/issues/758 | MDEyOklzc3VlQ29tbWVudDYyNDc5NjY4NQ== | simonw 9599 | 2020-05-06T17:52:54Z | 2020-05-06T17:52:54Z | OWNER | Thanks for the suggestion! I'll add this. |
{
"total_count": 0,
"+1": 0,
"-1": 0,
"laugh": 0,
"hooray": 0,
"confused": 0,
"heart": 0,
"rocket": 0,
"eyes": 0
} |
Question: Access to immutable database-path 612382643 |
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]);
user 2