Skip to content
New issue

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

Detect conflict between RLS and OLS #6

Open
otykier opened this issue Nov 8, 2017 · 0 comments
Open

Detect conflict between RLS and OLS #6

otykier opened this issue Nov 8, 2017 · 0 comments

Comments

@otykier
Copy link
Collaborator

otykier commented Nov 8, 2017

From @marcosqlbi on November 8, 2017 2:30

If a user belongs to two roles applying filters on the same table with row level security (RLS) in one role, and object level security in another role (OLS), the connection is not possible by design.

you can’t have RLS and OLS on the same table in different roles – that would prevent the connection from being opened

A Best Practices Analyzer rule could identify the presence or roles applying different filter types (RLS/OLS) over the same tables. If the developer knows that this will never happen (because a user cannot belong to two incompatible roles), there should be a way to disable the BPA (what could we use for that? Special annotations?).

Copied from original issue: TabularEditor/TabularEditor#113

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant