This data as json
|777333388||MDU6SXNzdWU3NzczMzMzODg=||1168||Mechanism for storing metadata in _metadata tables||9599||open||0||20||2021-01-01T18:47:27Z||2021-06-27T00:05:51Z||OWNER||
Original title: Perhaps metadata should all live in a
Inspired by #1150 - metadata should be exposed as an API, and for large Datasette instances that API may need to be paginated. So why not expose it through an in-memory database table?
One catch to this: plugins. #860 aims to add a plugin hook for metadata. But if the metadata comes from an in-memory table, how do the plugins interact with it?
The need to paginate over metadata does make a plugin hook that returns metadata for an individual table seem less wise, since we don't want to have to do 10,000 plugin hook invocations to show a list of all metadata.
If those plugins write directly to the in-memory table how can their contributions survive the server restarting?