While you could do much of this directly in your imbedded sql, and not use
the function, I like the ideal of the function for a number of reasons:
1 - Not having to do a DIGITS on each SUBSTR operation. That has to
improve performance.
2 - The error trapping in there to convert the return value to a null if
the numeric date is invalid. This allows you to do something like
Select coalesce(dec2date(file.field), :myDefaultValue) into :pgmfield from
file
where coalesce will convert a null date into some default value. Yes, you
could do that in the udf, but leaving it outside of the udf will allow a
programmer who might prefer to receive a null value to indicate an invalid
date to do so. That way they don't have to worry if they actually have a
transaction on 01/01/01 or some such thing.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.
midrange.com
