home / github / issue_comments

Menu
  • Search all tables
  • GraphQL API

issue_comments: 1683435579

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/2143#issuecomment-1683435579 https://api.github.com/repos/simonw/datasette/issues/2143 1683435579 IC_kwDOBm6k_c5kVzA7 9599 2023-08-18T06:49:39Z 2023-08-18T06:49:39Z OWNER

My ideal situation then would be something like this:

  • Metadata itself is VERY clearly described, including sensible rules for metadata inheritance where it makes sense. There is a datasette.X method for accessing it which is much more intuitive than datasette.metadata().
  • It's possible that method should be an async method, because that would support things like plugins that lookup metadata in database tables better.
  • All templates etc switch to the new, clean, intuitive metadata mechanism before 1.0.
  • I'm interested in the option of metadata being able to live in a _datasette_metadata table in the databases themselves - either as a plugin or as a core feature. I think it makes a lot of sense for metadata to optionally live with the data that it describes.
  • Configuration gets split from metadata. The stuff that configures Datasette no longer lives in the metadata.yml file - it lives in config.yml (or even datasette.yml).

Currently we have three types of things:

  • Metadata - information about the data
  • Configuration - stuff like "these columns should be sortable" and "this is configured as fts_table" and suchlike
  • Settings - the stuff that you pass to datasette --setting x y on server start.

Should settings and configuration be separate? I'm not 100% sure that they should - maybe those two concepts should be combined somehow.

Configuration directory mode needs to be considered too: https://docs.datasette.io/en/stable/settings.html#configuration-directory-mode - interestingly it already has a thing where it can pick up settings from a settings.json file - where settings are things like datasette --setting sql_time_limit_ms 4000.

{
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
1855885427  
Powered by Datasette · Queries took 0.912ms · About: github-to-sqlite