|
> Now here's the rub. Putting those features in SQL would make SQL
> non-compatible w/ the rest of the world. So all the cross platform
> compatibility arguments fall my the wayside. So now we're back where we
> started from - IBM may as well enhance DDS and get it over with.
What about the Domain keyword that most every SQL implementation I know of
other than DB2 UDB supports? Then you can say that this field is a
AccountNumber field and it would take on the attributes of the Domain
AccountNumber.
The syntax for the command is
Create Domain AccountNumber as Integer
Or you could be more creative and add check constraints to the domain
Create Domain AccountNumber as Integer
Check((Value >= 100) Or Value Is Null)
Then you will have the Handy Dandy AccountNumber DataType available for your
SQL enjoyment :-)
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.