Re: Blobs - Now is Field Reference File

Mark Lazarus 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.

>  I'm talking about the definition, not a specific table variable.  What
> happens if you try to add it again?  Will it overlay the current
> definition?  If this definition changes, is there a way to globally update
> all the affected databases?
> 

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.

Sounds simple, but it isn't. The AS/400 is kinda unique in the DB area.
There is only ONE (1) instance of the database on the AS/400 and I
consider that a drawback. The schema name is the library name. Again, if
scripted, you could change the schema name and run the scripts. Copy the
data and then rename the library.

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........



-- 
===========================================================
R. Bruce Hoffman, Jr.
 -- IBM Certified AS/400 Professional System Administrator
 -- IBM Certified AS/400 Professional Network Administrator

"The sum of all human knowledge is a fixed constant.
    It's the population that keeps growing!"
+---
| 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
+---