Clarity

Hi , While xogging in the one of the attribute (Data Type – Number ) of custom object using process -  if the Value is like 80.01499999999999593083807973962571196094 then it goes in the database like 80.015 (rounded off value ).

However if it is like 80.014567801593083807973962571196094 then it goes like 80.01456780159309.  Is this the clarity functionality or  I am missing something ?

If I have to xog the value as it is ( no round off ), is there any way I can achieve it .

Please advice . Thanks .

Not answering your question, but 80.01499999999999593083807973962571196094 rounded to the same precision as 80.01456780159309 (14 decimal places) is 80.01499999999999 and since the next digit is a '5' then this would mathematically be rounded as 80.015.

So your example is a bit confusing to me as to where the "problem" is without further details, like what format the column is for example (I mean have you specified a number of decimal places for it)

Hi David , I haven't specified any decimal places for rounding  off in my sql or gel script , so preciously it is rounding off to "14 decimal places by default " and xogging in . So xog will by default round off up to 14 decimal places and xog it in -  if not specified by user in the query .  

Please confirm if I understood it correctly .

Thanks .

Hi RKP,

Are you using these values in a custom attribute?

If yes, probably you can specify the number of decimal place in a custom attribute and then the XOG.

Thanks!

Regards

Gaurav 

Hi Gaurav , Yes - using in custom attribute . 

Thanks.

RKP wrote:

 

Hi David , I haven't specified any decimal places for rounding  off in my sql or gel script , so preciously it is rounding off to "14 decimal places by default " .

Well I was referring to the definition of the attribute in the application (and hence the business-layer that XOG is communicating with - i.e. if you'd specified 1 decimal place I'd expect everything to be rounded to 1dp and so on) not in the "code" that you are presenting the data to XOG with. I'll assume you did not specify anything though since I think the most you can specify is 6 decimals.

But I'm afraid that I don't know whether there is an application default scale to numbers - it might be influenced by the database defaults (on Oracle I believe this is a precision of 38 unless otherwise specified) or it might just be something defaulted in the PPM code when you don't provide a "decimal places" on the attribute setup.