Re: COALESCE not working as I expected -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

None of that documentation says what happens if the string_expression does not represent a valid number.

It does say that if any argument of TO_NUMBER is null, the result will be null.

On a v7r2 box,

values(to_number('0045E1020040'))

....+....1....+....2....+....3....+....4..
VALUES
++++++++++++++++++++++++++++++++++++++++++
******** End of data ********

values(coalesce(to_number('0045E1020040'),0))

....+....1....+....2....+....3....+....4..
VALUES
++++++++++++++++++++++++++++++++++++++++++
******** End of data ********

On 4/10/2020 2:46 PM, Rob Berendt wrote:

Actually to_number is plainly document in the database section of the IBM i Knowledge Center. Get into the habit of starting there. Bookmark the site.
Basically it says it is a duplicate of DECFLOAT_FORMAT.
https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_74/db2/rbafzscatonumber.htm

One could also look up valid floating decimal formats there although one may have to research further in that same center for that.

I just not feeling activating the VPN to try out some samples.

Rob Berendt

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.