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

RDB$TIME_ZONE_UTIL package has wrong privilege for PUBLIC [CORE6236] #6480

Closed
firebird-issue-importer opened this issue Jan 22, 2020 · 4 comments
Closed

Comments

@firebird-issue-importer

Submitted by: @asfernandes

RDB$TIME_ZONE_UTIL has USAGE privilege for PUBLIC.

But for packages the correct privilege is EXECUTE.

Commits: e93a729 6753656

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 22, 2020

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 2 [ 10888 ]

assignee: Adriano dos Santos Fernandes [ asfernandes ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 23, 2020

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Deferred

Test Details: Can not see changes in 4.0.0.1740 (23-jan-2020) vs 4.0.0.1714.
Sent letter to Adriano, 23.01.2020 09:05, waiting for reply.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 23, 2020

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: Deferred => Done successfully

Test Details: Can not see changes in 4.0.0.1740 (23-jan-2020) vs 4.0.0.1714.
Sent letter to Adriano, 23.01.2020 09:05, waiting for reply.

=>

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 23, 2020

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

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

Successfully merging a pull request may close this issue.

None yet
2 participants