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

2.5 RlsNotes: Warn against possible breakage of PSQL modules with ALTER COLUMN ... TYPE [DOC57] #64

Closed
firebird-automations opened this issue Jan 9, 2011 · 2 comments

Comments

@firebird-automations
Copy link

Submitted by: @paulvink

It used to be impossible to alter a column's type if the column was referenced in an SP or trigger, even if the change wouldn't break the PSQL code.

In 2.5 and up, such changes are permitted - even if they *do* break the code. This has not been clearly documented yet.

No error is raised if the code is broken. In most cases, the module's RDB$VALID_BLR flag will be set to 0, so the problem will be discovered "sooner or later".
But there are alo cases where RDB$VALID_BLR is kept at 1, and then anything can happen. (See CORE3303)

I think there should be a clear warning against this risk in the RlsNotes. One in the section Procedural SQL :: Borrow Database Column Type for a PSQL Variable, and possibly also a general warning somewhere in the DDL chapter, because this concerns not only "TYPE OF COLUMN" parameters and variables, but also the use of table/view columns in SQL statements within the PSQL code.

@firebird-automations
Copy link
Author

Commented by: @paulvink

To keep you off the streets ;-)

@firebird-automations
Copy link
Author

Modified by: @paulvink

assignee: Paul Vinkenoog [ paulvink ] => Helen Borrie [ helebor ]

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

3 participants