id,page,ref,title,content,breadcrumbs,references pages:databaseschemaview,pages,databaseschemaview,Database schema,"Use /database-name/-/schema to see the complete schema for a specific database. The .md and .json extensions work here too. The JSON returns an object with ""database"" and ""schema"" keys.","[""Pages and API endpoints"", ""Schemas""]",[] pages:databaseview-hidden,pages,databaseview-hidden,Hidden tables,"Some tables listed on the database page are treated as hidden. Hidden tables are not completely invisible - they can be accessed through the ""hidden tables"" link at the bottom of the page. They are hidden because they represent low-level implementation details which are generally not useful to end-users of Datasette. The following tables are hidden by default: Any table with a name that starts with an underscore - this is a Datasette convention to help plugins easily hide their own internal tables. Tables that have been configured as ""hidden"": true using hidden . *_fts tables that implement SQLite full-text search indexes. Tables relating to the inner workings of the SpatiaLite SQLite extension. sqlite_stat tables used to store statistics used by the query optimizer.","[""Pages and API endpoints"", ""Database""]",[] pages:instanceschemaview,pages,instanceschemaview,Instance schema,"Access /-/schema to see the complete schema for all attached databases in the Datasette instance. Use /-/schema.md to get the same information as Markdown. Use /-/schema.json to get the same information as JSON, which looks like this: { ""schemas"": [ { ""database"": ""content"", ""schema"": ""create table posts ..."" } }","[""Pages and API endpoints"", ""Schemas""]",[] pages:pages-schemas,pages,pages-schemas,Schemas,Datasette offers /-/schema endpoints to expose the SQL schema for databases and tables.,"[""Pages and API endpoints""]",[] pages:queryview,pages,queryview,Queries,"The /database-name/-/query page can be used to execute an arbitrary SQL query against that database, if the execute-sql permission is enabled. This query is passed as the ?sql= query string parameter. This means you can link directly to a query by constructing the following URL: /database-name/-/query?sql=SELECT+*+FROM+table_name Each configured canned query has its own page, at /database-name/query-name . Viewing this page will execute the query and display the results. In both cases adding a .json extension to the URL will return the results as JSON.","[""Pages and API endpoints""]",[] pages:tableschemaview,pages,tableschemaview,Table schema,"Use /database-name/table-name/-/schema to see the schema for a specific table. The .md and .json extensions work here too. The JSON returns an object with ""database"" , ""table"" , and ""schema"" keys.","[""Pages and API endpoints"", ""Schemas""]",[]