I wrote:
I just spent the afternoon bypassing the whole "pass the library to the UDF" thing by way of a strategy that requires the UDF calls in a VIEW definition to be library-qualified.

Now, I'm getting error messages to the effect of "Column FOO not in specified tables," where FOO is the library where the specific instance of my DISPLAYVAL UDF lives, and with which I'm qualifying the calls thereto, e.g., FOO/DISPLAYVAL(9106, BAR).

Have I just wasted my afternoon doing something not permitted in an SQL SELECT?

Or is the UDF guaranteed to be the one found at view creation time, making qualification unnecessary so long as the "right" one was the first one that RUNSQLSTM found when it created the view?

In which case, only the hour I spent painstakingly qualifying the UDF calls would have been wasted?


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].