Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On Fri, 27 Dec 2013 15:57:47 +0000
Tom Davies <> wrote:

Hi :)
Are you saying you have solved this problem yourself without help from
the list or has the problem just changed a bit?

To summarize it for posterity:

I wasn't able to appreciate if any change I was doing to the type used
(NUMERIC(N, M) or FLOAT or DOUBLE) in SQL operations was effective since
all I could get out from the DB was 2 decimals either in "simple" format
(1234567898,31) or scientific format (6,23E+015).

Not being able to see any change tricked me into thinking that no
matter what type I was using there was no effect on precision since I'm
used to something like:

test=# select 1.01::numeric(4,2)*2.02::numeric(4,2);
(1 row)

The problem was just a problem of output format that can be set once
you run the query, and in the result window right click on the column
name and change the format.

Thanks for the moral support anyway.

Ivan Sergio Borgonovo

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.