|
Bruce, At 11:21 AM 8/31/99 -0400, you wrote: >> How would you handle distributions to clients, ensuring that a global >> definition is maintained and does not clash w/ an existing definition? >You would need unique names. Prefixing comes to mind. >This was in a previous response. You get a message about the UDF >existing. You could create a new UDF and then change the files, or if >the entire thing is scripted, just run the scripts. As in SQL scripts? Sorry about the duplication, I was a day behind and it kinda crossed in the mail. >What I am not clear on is IBM's intent on the UDFs. If they allow the >qualification of the UDF to the schema name (library) then we should be >able to change the UDFs at will. If not........ If it's completely global, then that's a large potential problem, since software vendors couldn't really take advantage of it. Plus, from a definition standpoint it doesn't really make much sense either. LARGE_AMOUNT may mean one thing to one application and something totally different to another. BTW, is this in V4R4 only? How are the UDB features manipulated / viewed, etc? Will there be a native implementation? -mark +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.