You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the documentation regarding built-in privileges in section "Profiles reference", both "usage_on_schemas" and "usage_on_schema" appear. Only the first parameter is correct; the second one can be misleading and doesn't work.
The text was updated successfully, but these errors were encountered:
You're right @tstepien0 !
The error is actually in the Profile all_on_schemas section.
The privilege __usage_on_schema__ must be __usage_on_schemas__ to be functional!
Actually, this was a bug in configuration defaults fixed in 643f138 . Which mean 6.1 has a bug in default configuration. __all_on_schemas__ does not effectively include __usage_on_schemas__.
Please keep the issue open so I track a final task on this issue : prevent regression by controlling consistency of default configuration, add a CI job to ensure generated docs is up2date with the code.
In the documentation regarding built-in privileges in section "Profiles reference", both "usage_on_schemas" and "usage_on_schema" appear. Only the first parameter is correct; the second one can be misleading and doesn't work.
The text was updated successfully, but these errors were encountered: