× 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.


  1.  Home
  2. MIDRANGE-L
  3. February 2016

RE: SQL precision problem

Whoops, I typed that backwards. You are correct it's doing low order truncation.



-----Original Message-----
From: John Yeung [mailto:gallium.arsenide@xxxxxxxxx]
Sent: Friday, February 12, 2016 1:20 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: SQL precision problem

On Fri, Feb 12, 2016 at 1:58 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:
So what you're saying is that truncation is mandatory, so DB2 is doing high order truncation instead of low order.

Before we get any more confused, let me say that I read "high order truncation" as "chopping off the high-order digits". I suppose you could conceivably mean "keeping the high-order digits" instead, but I think that would be an unusual use of terminology.

Anyway, what DB2 is actually doing is chopping off low-order digits.
Your entire (intermediate) result just happens to fall into the lowest-order digits.

John Y.


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.