Re: [SL] Qty Precision

[<la...@cl...>]

Thank you for the reply! I thought about doing something like that but as
the yearends for 05, 06, and 07 all checkout so I am gonna leave it alone
in the db as it is for now. I am sure that there is an explanation on how
real and double precision numbers are stored in the db and hence the
difference.

On another question, I am also testing the upgrade of Postgres from 7.2 to
8.3, and any idea on what the 8.3 database locale should be? The default
8.3 database locale is LATIN9 and the pg_dumpall of SL from 7.2 is
SQL_ASCII. You think I should init the 8.3 db using SQL_ASCII instead of
the default LATIN9? Using LATIN9 and I did the import the yearend report
are all messed up?

Regards,

Tim



> On Wed, May 21, 2008 at 11:04 PM,  <la...@cl...> wrote:
>> Looked further into the issue, it seems during the database upgrade the
>> qty type had went from real to double precision. It seems weired that
>> the
>> value had went from 10.83 to 10.8299999237061 and not 10.8300000000000
>
> Following query should sort out the issue for the past data. New data
> will always be correctedly recorded. (Take backup before running it)
>
> UPDATE invoice SET qty = ROUND(qty,2);
>
> Regards
> --
> http://wiki.ledger123.com/
>
> * Purpose-built SQL-Ledger Hosting. Free trial.
> * SQL-Ledger VMware Appliance. Free download.
>
> --
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>