issue_comments

Table actions

2 rows where author_association = "OWNER" and issue = 1082765654 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: created_at (date), updated_at (date)

user 1

issue 1

  • add hash id to "_memory" url if hashed url mode is turned on and crossdb is also turned on · 2 ✖

author_association 1

  • OWNER · 2 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1072939780 https://github.com/simonw/datasette/issues/1561#issuecomment-1072939780 https://api.github.com/repos/simonw/datasette/issues/1561 IC_kwDOBm6k_c4_88ME simonw 9599 2022-03-19T04:45:40Z 2022-03-19T04:45:40Z OWNER

I ended up moving hashed URL mode out to a plugin in: - #647

If you're still interested in using it with _memory please open an issue in that repo here: https://github.com/simonw/datasette-hashed-urls

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 add hash id to "_memory" url if hashed url mode is turned on and crossdb is also turned on 1082765654  
997127784 https://github.com/simonw/datasette/issues/1561#issuecomment-997127784 https://api.github.com/repos/simonw/datasette/issues/1561 IC_kwDOBm6k_c47bvZo simonw 9599 2021-12-18T02:27:56Z 2021-12-18T02:27:56Z OWNER

Oh that's an interesting solution, combining the hashes of all of the individual databases.

I'm actually not a big fan of hashed_url mode - I implemented it right at the start of the project because it felt like a clever hack, and then ended up making it not-the-default a few years ago:

  • 418

  • 419

  • 421

I've since not found myself wanting to use it at all for any of my projects - which makes me nervous, because it means there's a pretty complex feature that I'm not using at all, so it's only really protected by the existing unit tests for it.

What I'd really like to do is figure out how to have hashed URL mode work entirely as a plugin - then I could extract it from Datasette core entirely (which would simplify a bunch of stuff) but people who find the optimization useful would be able to access it.

I'm not sure that the existing plugin hooks are robust enough to do that yet though.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 add hash id to "_memory" url if hashed url mode is turned on and crossdb is also turned on 1082765654  

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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]);