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

ALTER DOMAIN <name> TO <newname> fails if there are dependencies [CORE6359] #6600

Open
firebird-automations opened this issue Jul 8, 2020 · 2 comments

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Wilfredo (wpomier)

I can understand when the ALTER DOMAIN fails because the type is being changed and there are dependencies.
But renaming the DOMAIN doesn't have any data integrity risk, am I wrong?
IMO It should be simply allowed.

@firebird-automations
Copy link
Collaborator Author

Commented by: @dyemanov

If a procedure declares local variable based on domain, how it should look after renaming the domain?

@firebird-automations
Copy link
Collaborator Author

Commented by: Wilfredo (wpomier)

I completely agree when there are dependencies in code (stored procedures, triggers, etc.), but when the dependencies affect only data e.g. a huge chain of constraints (pks, fks, uks) and indexes, it takes a lot of work just to rename a domain.

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

No branches or pull requests

1 participant