|
Bruce, At 08:10 AM 8/27/99 -0400, you wrote: >> Interesting. Is this handled on a global or a library or some other >> grouping basis? What happens if the variable already exists? Will a >> different attribute overlay it or be rejected? >Money becomes a type available to ALL tables, just like decimal, char or >integer. The database manager presents this. (For OS/400, just read that >"system".) How would you handle distributions to clients, ensuring that a global definition is maintained and does not clash w/ an existing definition? >As for the variable, what variable are you talking about? The money is a >TYPE, not a variable. The table is being created, not altered. If you >want, you can drop a column and then add a column in the alter table statements. 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? -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-2025 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.