Re: Referencing Package from another schema

And you would do well to observe some good programming practices and use functions to get and set the value of that package variable. It may be GLOBAL to the package, but it should be considered PRIVATE elsewhere.

And the variable name suggests something fishy happening. Why would you want a trigger to change a value called IDENTITY?

Last suggestion befor I go. I use a function available in any package I build. the function name is WHOAMI(). It takes no parameters and returns the release information of the package, which usually includes: name, release/build date, and release number (typically an RCS or similar rev number) The value returned by the WHOAMI function is private to the package and there is not way to change it other than compiling a new release.

have a good day,
ed Received on Wed Dec 29 2004 - 12:23:06 CST