issue_comments

Table actions

4 rows where issue = 1421544654 and "updated_at" is on date 2022-10-25 sorted by updated_at descending

✎ View and edit SQL

This data as json, CSV (advanced)

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

user 2

author_association 2

issue 1

  • API to insert a single record into an existing table · 4 ✖
id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1291228502 https://github.com/simonw/datasette/issues/1851#issuecomment-1291228502 https://api.github.com/repos/simonw/datasette/issues/1851 IC_kwDOBm6k_c5M9pVW eyeseast 25778 2022-10-25T23:02:10Z 2022-10-25T23:02:10Z CONTRIBUTOR

That's reasonable. Canned queries and custom endpoints are certainly going to give more room for specific needs. 

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API to insert a single record into an existing table 1421544654  
1291226367 https://github.com/simonw/datasette/issues/1851#issuecomment-1291226367 https://api.github.com/repos/simonw/datasette/issues/1851 IC_kwDOBm6k_c5M9oz_ simonw 9599 2022-10-25T22:58:30Z 2022-10-25T22:58:30Z OWNER

The datasette insert concept included plugin support, with the idea of being able to support things like SpatiaLite files: - #1160

I think this API mechanism is going to be a bit less exciting than that - it will be low-level for inserting rows, and if you want to do something fancier you can use a canned query that feeds incoming GeoJSON to a SpatiaLite function instead.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API to insert a single record into an existing table 1421544654  
1290615599 https://github.com/simonw/datasette/issues/1851#issuecomment-1290615599 https://api.github.com/repos/simonw/datasette/issues/1851 IC_kwDOBm6k_c5M7Tsv eyeseast 25778 2022-10-25T14:05:12Z 2022-10-25T14:05:12Z CONTRIBUTOR

This could use a new plugin hook, too. I don't want to complicate your life too much, but for things like GIS, I'd want a way to turn regular JSON into SpatiaLite geometries or combine X/Y coordinates into point geometries and such. Happy to help however I can.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API to insert a single record into an existing table 1421544654  
1289865317 https://github.com/simonw/datasette/issues/1851#issuecomment-1289865317 https://api.github.com/repos/simonw/datasette/issues/1851 IC_kwDOBm6k_c5M4chl simonw 9599 2022-10-25T01:42:47Z 2022-10-25T01:42:47Z OWNER

This is going to tie into Datasette's existing permissions mechanism, so plugins will be able to define their own custom mechanisms for tokens to be attached to a specific identity: https://docs.datasette.io/en/stable/authentication.html

There's only one plugin for API tokens at the moment, which is this one: https://datasette.io/plugins/datasette-auth-tokens

I'm actually planning on adding another, default token mechanism to Datasette itself as part of this work:

  • 1852

It may well be that datasette-sandstorm-support needs to add something custom here too.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 API to insert a single record into an existing table 1421544654  

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