id,page,ref,title,content,breadcrumbs,references
upgrade_guide:metadata-fallback-has-been-removed,upgrade_guide,metadata-fallback-has-been-removed,"Metadata ""fallback"" has been removed","Certain keys in metadata like  license  used to ""fallback"" up the chain of ownership.
                        For example, if you set an  MIT  to a database and a table within that database did not have a specified license, then that table would inherit an  MIT  license. 
                     This behavior has been removed in Datasette 1.0. Now license fields must be placed on all items, including individual databases and tables.","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]",[]
upgrade_guide:upgrade-guide-v1-metadata-json-removed,upgrade_guide,upgrade-guide-v1-metadata-json-removed,The ,"As of Datasette  1.0a14 , the root level  /metadata.json  endpoint has been removed. Metadata for tables will become available through currently in-development extras in a future alpha.","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]",[]
upgrade_guide:upgrade-guide-v1-metadata-method-removed,upgrade_guide,upgrade-guide-v1-metadata-method-removed,The ,"As of Datasette  1.0a14 , the  .metadata()  method on the Datasette Python API has been removed. 
                     Instead, one should use the following methods on a Datasette class: 
                     
                         
                             get_instance_metadata() 
                         
                         
                             get_database_metadata() 
                         
                         
                             get_resource_metadata() 
                         
                         
                             get_column_metadata()","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]",[]
upgrade_guide:upgrade-guide-v1-metadata-removed,upgrade_guide,upgrade-guide-v1-metadata-removed,The ,"In Datasette  0.x  plugins could implement a  get_metadata()  plugin hook to customize how metadata was retrieved for different instances, databases and tables. 
                     This hook could be inefficient, since some pages might load metadata for many different items (to list a large number of tables, for example) which could result in a large number of calls to potentially expensive plugin hook implementations. 
                     As of Datasette  1.0a14  (2024-08-05), the  get_metadata()  hook has been deprecated: 
                     # ❌ DEPRECATED in Datasette 1.0
@hookimpl
def get_metadata(datasette, key, database, table):
    pass 
                     Instead, plugins are encouraged to interact directly with Datasette's in-memory metadata tables in SQLite using the following methods on the  Datasette class : 
                     
                         
                             get_instance_metadata()  and   set_instance_metadata() 
                         
                         
                             get_database_metadata()  and   set_database_metadata() 
                         
                         
                             get_resource_metadata()  and   set_resource_metadata() 
                         
                         
                             get_column_metadata()  and   set_column_metadata() 
                         
                     
                     A plugin that stores or calculates its own metadata can implement the  startup(datasette)  hook to populate those items on startup, and then call those methods while it is running to persist any new metadata changes.","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]",[]
upgrade_guide:upgrade-guide-v1-metadata-split,upgrade_guide,upgrade-guide-v1-metadata-split,,"Before Datasette 1.0, the  metadata.yaml  file became a kitchen sink if a mix of metadata, configuration, and settings. Now  metadata.yaml  is strictly for metaata (ex title and descriptions of database and tables, licensing info, etc). Other settings have been moved to a  datasette.yml  configuration file, described in  Configuration . 
                     To start Datasette with both metadata and configuration files, run it like this: 
                     datasette --metadata metadata.yaml --config datasette.yaml
# Or the shortened version:
datasette -m metadata.yml -c datasette.yml","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]",[]
upgrade_guide:upgrade-guide-v1-metadata-upgrade,upgrade_guide,upgrade-guide-v1-metadata-upgrade,Upgrading an existing ,"The  datasette-upgrade plugin  can be used to split a Datasette 0.x.x  metadata.yaml  (or  .json ) file into separate  metadata.yaml  and  datasette.yaml  files. First, install the plugin: 
                     datasette install datasette-upgrade 
                     Then run it like this to produce the two new files: 
                     datasette upgrade metadata-to-config metadata.json -m metadata.yml -c datasette.yml","[""Upgrade guide"", ""Datasette 0.X -> 1.0"", ""Metadata changes""]","[{""href"": ""https://github.com/datasette/datasette-upgrade"", ""label"": ""datasette-upgrade plugin""}]"