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

Jump to bottom

Cache results of permission checks for stored procedures [CORE2109] #2543

Open
firebird-automations opened this issue Oct 6, 2008 · 2 comments
Open

Cache results of permission checks for stored procedures [CORE2109] #2543

firebird-automations opened this issue Oct 6, 2008 · 2 comments
Labels
affect-version: 1.5.5 affect-version: 2.0.4 affect-version: 2.1.1 affect-version: 2.5 Alpha 1 component: engine component: security priority: major type: improvement

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: @pcisar

While results of permission checks made for user are cached for connection, it's not the case for called stored procedures. With many SP's and triggers that call other SP's it could be quite expensive to perform these checks even for simple permission schemes. In result, prepare times could be much bigger than necessary (or acceptable).
@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

IIRC, the permission checking logic (especially for [interdependent] stored procedures and triggers) has been significantly improved in v2.0. Is it still not good enough? Do you have a test case?

@firebird-automations
Copy link
Collaborator Author

Commented by: @pcisar

Yes, I can provide one. Actually, this was already discussed with Vlad before the conference, so I suppose he will comment on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affect-version: 1.5.5 affect-version: 2.0.4 affect-version: 2.1.1 affect-version: 2.5 Alpha 1 component: engine component: security priority: major type: improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@firebird-automations