issue_comments

Table actions

4 rows where issue = 1425029242, "updated_at" is on date 2022-11-15 and user = 9599 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

  • simonw · 4 ✖

issue 1

  • Update a single record in an existing table · 4 ✖

author_association 1

id html_url issue_url node_id user created_at updated_at ▲ author_association body reactions issue performed_via_github_app
1315812212 https://github.com/simonw/datasette/issues/1863#issuecomment-1315812212 https://api.github.com/repos/simonw/datasette/issues/1863 IC_kwDOBm6k_c5ObbN0 simonw 9599 2022-11-15T20:12:02Z 2022-11-15T20:12:02Z OWNER

If the update succeeds it will return {"ok": true}.

For consistency with /db/table/-/insert you can pass "return": true and it will return a "row" key with the now-updated full row.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Update a single record in an existing table 1425029242  
1315809867 https://github.com/simonw/datasette/issues/1863#issuecomment-1315809867 https://api.github.com/repos/simonw/datasette/issues/1863 IC_kwDOBm6k_c5ObapL simonw 9599 2022-11-15T20:09:44Z 2022-11-15T20:09:44Z OWNER

I'm also not going to implement "alter": true yet (which would add any missing columns based on the update) - I'll hold that off for a later feature.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Update a single record in an existing table 1425029242  
1315809260 https://github.com/simonw/datasette/issues/1863#issuecomment-1315809260 https://api.github.com/repos/simonw/datasette/issues/1863 IC_kwDOBm6k_c5Obafs simonw 9599 2022-11-15T20:09:11Z 2022-11-15T20:09:11Z OWNER

I'm going to use the error format I've been experimenting with here: - #1875

json { "type": "https://example.net/validation-error", "title": "Your request is not valid.", "errors": [ { "detail": "must be a positive integer", "pointer": "#/age" }, { "detail": "must be 'green', 'red' or 'blue'", "pointer": "#/profile/color" } ] } I'm not quite ready to commit to a type URL though, so I'll leave that to be solved later should I fully embrace that RFC.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Update a single record in an existing table 1425029242  
1315808062 https://github.com/simonw/datasette/issues/1863#issuecomment-1315808062 https://api.github.com/repos/simonw/datasette/issues/1863 IC_kwDOBm6k_c5ObaM- simonw 9599 2022-11-15T20:08:04Z 2022-11-15T20:08:04Z OWNER

The initial design I'm going to implement will look like this:

POST /db/table/1/-/update Authorization: Bearer xxx Content-Type: application/json json { "update": { "name": "New name" } } Any fields that are not yet columns will return an error.

Should it enforce types, in as much as an integer column should have a JSON integer passed to it, or should it allow strings containing valid integers?

I'm going to allow strings, mainly as a workaround for the fact that JavaScript integers have a maximum size.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 Update a single record in an existing table 1425029242  

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