issue_comments: 753398542

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/1168#issuecomment-753398542 https://api.github.com/repos/simonw/datasette/issues/1168 753398542 MDEyOklzc3VlQ29tbWVudDc1MzM5ODU0Mg== 9599 2021-01-01T22:37:24Z 2021-01-01T22:37:24Z OWNER

The direction I'm leaning in now is the following:

  • Metadata always lives in SQLite tables
  • These tables can be co-located with the database they describe (same DB file)
  • ... or they can be in a different DB file and reference the other database that they are describing
  • Metadata provided on startup in a metadata.json file is loaded into an in-memory metadata table using that same mechanism

Plugins that want to provide metadata can do so by populating a table. They could even maintain their own in-memory database for this, or they could write to the _internal in-memory database, or they could write to a table in a database on disk.

 
{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
 777333388