I chose to have a new column in SYSALISES rather than expanding RoutineAliasInfo becasue, like Satheesh brought it up in his following comment below, metadata extraction won't be straightforward if it was part of RoutineAliasInfo.
"It would become harder to extract this info from RoutineAliasInfo as it is a Java object for any metadata processing... like in dblook or for other GUI tools. We would have to document how RoutineAliasInfo gets generated as a character type and maintain that format in the future."
Mamta
Mamta
On 2/23/06, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Mamta Satoor wrote:
> Thanks for sharing your thoughts on this, Satheesh. I will spend more
> time on it to see if external security info can be added as another
> column to the SYSALIASES table rather than as another filed to
> RoutineAliasInfo.
Just curious as to why the new column approach was choosen, over the
existing RoutineAliasInfo column?
Dan.
