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

allow setting row permissions using range type columns #2882

Open
andrewalex opened this issue Sep 14, 2019 · 3 comments
Open

allow setting row permissions using range type columns #2882

andrewalex opened this issue Sep 14, 2019 · 3 comments
Assignees
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed c/console Related to console c/server Related to server k/enhancement New feature or improve an existing feature p/medium non-urgent issues/features that are candidates for being included in one of the upcoming sprints

Comments

@andrewalex
Copy link

I seem unable to set any row select permissions for tstzrange columns in the user interface the dropdown is blank.
image

@praveenweb praveenweb added the c/console Related to console label Sep 18, 2019
@rikinsk rikinsk added c/server Related to server k/enhancement New feature or improve an existing feature labels Sep 19, 2019
@rikinsk
Copy link
Member

rikinsk commented Sep 19, 2019

@andrewalex We currently don't support range type fields in permission rules.

Could you share a little more information about the permission rule you are trying to set up to help us understand the use case better.

@rikinsk rikinsk changed the title Unable to set row select permissions on tstzrange columns allow setting row select permissions on range type columns Sep 19, 2019
@rikinsk rikinsk changed the title allow setting row select permissions on range type columns allow setting row permissions using range type columns Sep 19, 2019
@andrewalex
Copy link
Author

andrewalex commented Sep 19, 2019

given all design of permissions, I don't think there is anything you can do at the moment. I was hoping a "greater than now/today"
More details:
I have a function that returns some date ranges, in a custom table. I am trying to make it so that role 'user' can see all ranges, and role 'anonymous' can only see future ranges..
The only solution I can think of involves 2 different functions, and 2 different identical empty tables. 1 for each role.

@andrewalex
Copy link
Author

@rikinsk to keep this individual issue simple (and not combine with needed scalar function calls) the supported ideal supported range operators would be the following
https://www.postgresql.org/docs/9.3/functions-range.html

@vaishnavigvs vaishnavigvs added the a/authz Issues related to "authorization" and the policy engine after session claims are procesed label Jun 28, 2021
@0x777 0x777 added the p/medium non-urgent issues/features that are candidates for being included in one of the upcoming sprints label Oct 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/authz Issues related to "authorization" and the policy engine after session claims are procesed c/console Related to console c/server Related to server k/enhancement New feature or improve an existing feature p/medium non-urgent issues/features that are candidates for being included in one of the upcoming sprints
Projects
None yet
Development

No branches or pull requests

6 participants