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 have been thinking about the readonly role. There is very little benefit offered by adding this role for the additional surface area introduced.
We already make this simple in Supabase dashboard, so let's remove it from the default database setup.
The text was updated successfully, but these errors were encountered:
Clear #27 Supabase Postgres 0.13.0 Checklist items
4e792e3
- #23 Remove readonly role - #24 Add pgjwt extension - #25 Add pgsql-http extension - #26 Add plpgsql_check extension - Add pljava - Add WAL-G - Add daemontools - Set row_security to ON
No branches or pull requests
I have been thinking about the readonly role. There is very little benefit offered by adding this role for the additional surface area introduced.
We already make this simple in Supabase dashboard, so let's remove it from the default database setup.
The text was updated successfully, but these errors were encountered: