-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Remove deprecated checkCanCreateSchema #15618
Remove deprecated checkCanCreateSchema #15618
Conversation
Retaining the deprecated method was not sufficient for maintaining compatibility, because the new method did not delegate to the old one. Thus, if an implementor kept implementing only the old method, the CREATE SCHEMA would get denied, irrespective of the implemented logic. Removing the deprecated method makes the incompatibility clearer, as it fails at the compilation time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The access control manager should have called both methods. But it's fine to remove the old one now.
Thank you |
How would it be better than delegating from the new one to the old one?
Agreed. |
Incorporate following changes Remove deprecated checkCanCreateSchema trinodb/trino#15618 trinodb/trino@0fac087 Disallow multiple masks on a given column trinodb/trino#15680 trinodb/trino@bdd1cb5
Incorporate following changes Remove deprecated checkCanCreateSchema trinodb/trino#15618 trinodb/trino@0fac087 Disallow multiple masks on a given column trinodb/trino#15680 trinodb/trino@bdd1cb5
Retaining the deprecated method was not sufficient for maintaining compatibility, because the new method did not delegate to the old one. Thus, if an implementor kept implementing only the old method, the CREATE SCHEMA would get denied, irrespective of the implemented logic. Removing the deprecated method makes the incompatibility clearer, as it fails at the compilation time.
Follows #15153 (comment)