home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 1294007024

This data as json

html_url issue_url id node_id user created_at updated_at author_association body reactions issue performed_via_github_app
https://github.com/simonw/datasette/issues/1868#issuecomment-1294007024 https://api.github.com/repos/simonw/datasette/issues/1868 1294007024 IC_kwDOBm6k_c5NIPrw 9599 2022-10-27T20:05:44Z 2022-10-27T20:05:52Z OWNER

So given this scheme, the URL design would look like this:

  • POST /db/table/-/insert - insert a single row
  • POST /db/table/-/insert-many - insert multiple rows (might just keep that on /-/insert with a JSON array rather than object though)
  • POST /db/table/-/drop - drop a table
  • POST /db/table/-/alter - alter a table
  • POST /db/table/-/upsert - upsert, https://sqlite-utils.datasette.io/en/stable/python-api.html#upserting-data
  • POST /db/table/-/create - could be an endpoint for explicitly creating a table, or should that live at /db/-/create instead?

And for rows (pks here since compound primary keys are supported):

  • POST /db/table/pks/-/update - update row
  • POST /db/table/pks/-/delete - delete row
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
1426195437  
Powered by Datasette · Queries took 0.812ms · About: github-to-sqlite