Fix queries to consider role membership as well as table ownership #46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this change, the introspections that looked to see whether the current user owned a particular table only considered direct ownership. But in the case of a table owned by a role, any user that has that role also effectively owns the table, and has permission to operate on the table as if they were the direct owner.
This change updates the
get_referring_fksandis_table_ownerintrospection functions to consider both direct ownership and also indirect ownership via role membership.