Me too. I just did that to show an easy way to inject bad data to see how
a file defined with SQL would stop bad data, while a DDS defined file
would allow it.
I think it goes back to history. Not uncommon in the bad old days for
someone desperate to add a new field to hijack an old unused numeric field
and store alphabetic data in it. Especially with internally defined
files. Externally, a DS would work. Not everyone needed that Sumatran
currency exchange rate column supported by their software vendor. That's
why DDS allows crap in numeric fields. When SQL came out they said no.
DDS will not allow crap into date, time or timestamp fields - they're new
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