docs: sections: 1 row where breadcrumbs contains "0.44 (2020-06-11)" and references = "[{"href": "https://github.com/simonw/datasette/issues/788", "label": "#788"}]"

1 row where breadcrumbs contains "0.44 (2020-06-11)" and references = "[{"href": "https://github.com/simonw/datasette/issues/788", "label": "#788"}]"

Search:

descending

id ▼	page	ref	title	content	breadcrumbs	references
changelog:permissions	changelog	permissions	Permissions	Datasette also now has a built-in concept of Permissions . The permissions system answers the following question: Is this actor allowed to perform this action , optionally against this particular resource ? You can use the new "allow" block syntax in metadata.json (or metadata.yaml ) to set required permissions at the instance, database, table or canned query level. For example, to restrict access to the fixtures.db database to the "root" user: { "databases": { "fixtures": { "allow": { "id" "root" } } } } See Defining permissions with "allow" blocks for more details. Plugins can implement their own custom permission checks using the new permission_allowed(datasette, actor, action, resource) hook. A new debug page at /-/permissions shows recent permission checks, to help administrators and plugin authors understand exactly what checks are being performed. This tool defaults to only being available to the root user, but can be exposed to other users by plugins that respond to the permissions-debug permission. ( #788 )	["Changelog", "0.44 (2020-06-11)"]	[{"href": "https://github.com/simonw/datasette/issues/788", "label": "#788"}]

Advanced export

JSON shape: default, array, newline-delimited, object

CREATE TABLE [sections] (
   [id] TEXT PRIMARY KEY,
   [page] TEXT,
   [ref] TEXT,
   [title] TEXT,
   [content] TEXT,
   [breadcrumbs] TEXT,
   [references] TEXT
);