Subject | alter procedure, metadata cache |
---|---|
Author | Brian Gooch |
Post date | 2010-07-28T13:27:42Z |
Thought for the day: Each of us is here to realise our own potential with the least inconvenience to others.
Philip,
Helen's 'The Firebird Book' pp 633/4; extracts from the notes follow
A proc which is in use by any transaction cannot be dropped. This is s special issue in systems where procs are being called from transacations that are committed using CommitRetaining.
if any other objects in the database refer to or call the proc, it is necessary to alter the dependent objects to remove any references and commit that work before the proc can be dropped.
A recursive proc cannot be dropped without first removing the recursive calls and committing that change. Similar probs occur when that proc calls others, which in turn may call the proc you wish to drop.
Kind Regards,Brian Gooch 'Great engineering is simple engineering'
[Non-text portions of this message have been removed]
Philip,
Helen's 'The Firebird Book' pp 633/4; extracts from the notes follow
A proc which is in use by any transaction cannot be dropped. This is s special issue in systems where procs are being called from transacations that are committed using CommitRetaining.
if any other objects in the database refer to or call the proc, it is necessary to alter the dependent objects to remove any references and commit that work before the proc can be dropped.
A recursive proc cannot be dropped without first removing the recursive calls and committing that change. Similar probs occur when that proc calls others, which in turn may call the proc you wish to drop.
Kind Regards,Brian Gooch 'Great engineering is simple engineering'
[Non-text portions of this message have been removed]