|
On Thu, May 14, 2015 at 1:45 PM, CRPence <crpbottle@xxxxxxxxx> wrote: > FWiW I find returning 'N' for the NULL value rather than using RETURNS > NULL ON NULL INPUT [¿or is that the default and the If..Null predicate is > always false?] seem rather contrary to the concept of NULL. Chuck, The reason a 'N' was returned for a NULL value was because our programmers seemed unable to grasp (even less to work with) the concept of a NULL field. It was decided by our Team leaders (who had the slightest knowledge of SQL that you can imagine) to use only 'Y' or 'N' as a the values returned by the function. The "CAST" was, I'm afraid, a not so well thought-out inclusion I have just made regarding the OP's request. Our original use of te function was for numeric data stored as character data. Regards, Luis P.S. Still have the same Team leaders, with about the same SQL knowledge... :-( Luis Rodriguez IBM Certified Systems Expert — eServer i5 iSeries --
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.
midrange.com
