We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I built this for:
But in writing the release notes (#58) I realized the tests don't actually cover this yet. The documentation should mention it too.
The text was updated successfully, but these errors were encountered:
I first did a round of manual testing:
sqlite-utils create-database sales.db sqlite-utils create-database marketing.db sqlite-utils create-table sales.db notes id integer --pk id sqlite-utils create-table sales.db customers id integer --pk id datasette -c perms.yml sales.db marketing.db --secret 1 --reload
Where perms.yml contained:
perms.yml
databases: marketing: permissions: create-table: id: pelican drop-table: id: pelican alter-table: id: pelican sales: tables: notes: permissions: alter-table: id: pelican
And I used a new datasette-unsafe-actor-debug plugin to help test.
datasette-unsafe-actor-debug
This worked, though it did show me I need to fix this:
Sorry, something went wrong.
03f7f53
Fixed bug in rename permissions
01d61ea
Refs #60, refs #59
Release 0.8a1
f167036
Refs #59, #60 Refs simonw/datasette#2294
No branches or pull requests
I built this for:
But in writing the release notes (#58) I realized the tests don't actually cover this yet. The documentation should mention it too.
The text was updated successfully, but these errors were encountered: