Issue Details (XML | Word | Printable)

Key: DOC-57
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Helen Borrie
Reporter: Paul Vinkenoog
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

2.5 RlsNotes: Warn against possible breakage of PSQL modules with ALTER COLUMN ... TYPE

Created: 08/Jan/11 10:44 PM   Updated: 08/Jan/11 10:45 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

 Description  « Hide
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 CORE-3303)

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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.