sql-ledger-users

[SL] Error in converting an offer to an order

[Eric S. <eri...@fk...>]

Hello,

The actual version of sql-ledger that is in use is 2.8.13 and we are 
working with comma not
with decimal points.

When we have articles or services with a comma 113,50 for once piece 
after converting
an offer to an order.  The price of this item is converted to 1135,00.


Best regards,

Eric

[SL] Qty Precision

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

hello...we are testing our upgrade from 2.4.11 to 2.8.14 and the default
precison is set to 2. Everything seems fine but the qty. for an example
invoice went from 10.83 to 10.8299999237061. My guess is that the
precision doesn't apply to qty. anyone knows how i can fix this? This line
item was shipping so for most of the time it isn't an integer. Sending a
customer an invoice with this many decimal place seems confusing...thanks
ahead for your help...regards, tim

Re: [SL] Qty Precision

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

No response as of yet on this one...

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
(probably during some alter table modify column command) as the original
value was entered as 10.83. I can probably use some more time to look into
this, but for now I have updated the io.pl to format qty like sellprice.

$form->format_amount(\%myconfig, $form->{"qty_$i"}, $decimalplaces, $zero)

This issue impact only existing invoice (I hope) and I can now get old
invoices to print only the two decimal place. Any input on if this is
gonna break anything would be great. For now, I can only rerun the yearend
reports using the old and new systems an hoping that their bottom lines
match. It would be annoying for them to be off by $0.01.

Thanks ahead for any comments!

Tim



> hello...we are testing our upgrade from 2.4.11 to 2.8.14 and the default
> precison is set to 2. Everything seems fine but the qty. for an example
> invoice went from 10.83 to 10.8299999237061. My guess is that the
> precision doesn't apply to qty. anyone knows how i can fix this? This line
> item was shipping so for most of the time it isn't an integer. Sending a
> customer an invoice with this many decimal place seems confusing...thanks
> ahead for your help...regards, tim
>
>
> -------------------------------------------------------------------------
> 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
>

Re: [SL] Qty Precision

[Armaghan S. <sa...@le...>]

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.

--

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
>

Re: [SL] Qty Precision

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

Oops...never mind that I used the old version of pg_dumpall to export the
data and now using the 8.3 version to do the export all seems fine
now...tim
>
> 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
>>
>
>
>
> -------------------------------------------------------------------------
> 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
>

[SL] Postgres replication

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

hello all...our business has now the need to replicate our sl/postgres db
from our main office in ca to ny as the ny system (public and outside of
our firewall) has the need to generate non-critical read only invoice and
inventory reports. our requirements are real simple and slony-i seems to
be an overkill. we have also evaluated pgpool-ii but it was ruled out as
it doesn't support x509 ssl connection (a must for business data). oralce
and informix would have been nice as they both provide standby read-only
databases that are very simple to manage. it is too bad that you cannot
access a standby postgres database.

so my question is anyone has any comments on what other tools out there
that may allow us to create a postgres standby read-only database? if
nothing we may just have to walk down the slony-i path...thanks ahead for
any comments.

regards,

tim

Re: [SL] Postgres replication (me three)

[Dr E. L. <el...@li...>]

Tim,

we would be extremely interested in a solution for exactly this issue.
Not only for SL, by the way, we have another database that we would like
to replicate read-only in a simple fashion.

Please post any solution that you may find, or if it's not of interest
to the list, please email me directly.

greetings, el

on 5/28/08 8:04 AM la...@cl... said the following:
> hello all...our business has now the need to replicate our sl/postgres db
> from our main office in ca to ny as the ny system (public and outside of
> our firewall) has the need to generate non-critical read only invoice and
> inventory reports. our requirements are real simple and slony-i seems to
> be an overkill. we have also evaluated pgpool-ii but it was ruled out as
> it doesn't support x509 ssl connection (a must for business data). oralce
> and informix would have been nice as they both provide standby read-only
> databases that are very simple to manage. it is too bad that you cannot
> access a standby postgres database.
> 
> so my question is anyone has any comments on what other tools out there
> that may allow us to create a postgres standby read-only database? if
> nothing we may just have to walk down the slony-i path...thanks ahead for
> any comments.
> 
> regards,
> 
> tim
						
-- 
Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
PO Box 8421             \     /   Please do NOT email to this address
Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way

Re: [SL] Postgres replication

[Adam V. <amv...@gm...>]

la...@cl... wrote:
> hello all...our business has now the need to replicate our sl/postgres db
> from our main office in ca to ny as the ny system (public and outside of
> our firewall) has the need to generate non-critical read only invoice and
> inventory reports. our requirements are real simple and slony-i seems to
> be an overkill. we have also evaluated pgpool-ii but it was ruled out as
> it doesn't support x509 ssl connection (a must for business data). oralce
> and informix would have been nice as they both provide standby read-only
> databases that are very simple to manage. it is too bad that you cannot
> access a standby postgres database.
>
> so my question is anyone has any comments on what other tools out there
> that may allow us to create a postgres standby read-only database? if
> nothing we may just have to walk down the slony-i path...thanks ahead for
> any comments.
>
> regards,
>
> tim
If you go the route you intent on, I'd guess slony is your best option.  
Of course there are other ways to do this too, like manually scripting a 
db export import daily.

However with knowing just the info you provided, setting up a 
master-slave itself seems like overkill.  What about a VPN?  Or setting 
up SL on it's own host?  My SL server isn't sharing it's IP with other 
domains, so for me a default to deny firewall covers virtually all my 
security needs.  You can always run SSL on it if you like.

-- 
Adam Vandemore
Systems Administrator
IMED Mobility

Re: [SL] Postgres replication

[Dr E. L. <el...@li...>]

With sufficient bandwidth it'll be trivial to pg_dump every hour or even
more often. But that does not solve the issue of having access to the
invoice data in real time.

ANd, I don't think setting someting up is overkill because you only
do it once. Unless of course the learning curve is very steep and/or
the overhead is large.

If someone comes up with a plan, please publish the cookbook on how
to do it :-)-O

MySQL has got this feature too, hasn't it?

el

on 5/28/08 3:27 PM Adam Vandemore said the following:
> la...@cl... wrote:
>> hello all...our business has now the need to replicate our sl/postgres db
>> from our main office in ca to ny as the ny system (public and outside of
>> our firewall) has the need to generate non-critical read only invoice and
>> inventory reports. our requirements are real simple and slony-i seems to
>> be an overkill. we have also evaluated pgpool-ii but it was ruled out as
>> it doesn't support x509 ssl connection (a must for business data). oralce
>> and informix would have been nice as they both provide standby read-only
>> databases that are very simple to manage. it is too bad that you cannot
>> access a standby postgres database.
>>
>> so my question is anyone has any comments on what other tools out there
>> that may allow us to create a postgres standby read-only database? if
>> nothing we may just have to walk down the slony-i path...thanks ahead for
>> any comments.
>>
>> regards,
>>
>> tim
> If you go the route you intent on, I'd guess slony is your best option.  
> Of course there are other ways to do this too, like manually scripting a 
> db export import daily.
> 
> However with knowing just the info you provided, setting up a 
> master-slave itself seems like overkill.  What about a VPN?  Or setting 
> up SL on it's own host?  My SL server isn't sharing it's IP with other 
> domains, so for me a default to deny firewall covers virtually all my 
> security needs.  You can always run SSL on it if you like.
> 

-- 
Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
PO Box 8421             \     /   Please do NOT email to this address
Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way

Re: [SL] Postgres replication

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

Dear Dr.

Yes, we do need the data near real time and it seems that Postgres is
currently working on a readable hot standby so if you can wait may be it
is a good idea to deploy the readable hot standby when it is available. We
are probably going to head down the direction of Slony-I and there is a
catch with it as it does require the replicated tables to have a primary
key. That probably shouldn't be an issue as it may be alright to add a
primary key if there isn't one by the way of composite pirmay key or just
plain adding a new column.

BTW, as for the steps there are more then a few...

http://slony.info/documentation/

Regards,

Tim

> With sufficient bandwidth it'll be trivial to pg_dump every hour or even
> more often. But that does not solve the issue of having access to the
> invoice data in real time.
>
> ANd, I don't think setting someting up is overkill because you only
> do it once. Unless of course the learning curve is very steep and/or
> the overhead is large.
>
> If someone comes up with a plan, please publish the cookbook on how
> to do it :-)-O
>
> MySQL has got this feature too, hasn't it?
>
> el
>
> on 5/28/08 3:27 PM Adam Vandemore said the following:
>> la...@cl... wrote:
>>> hello all...our business has now the need to replicate our sl/postgres
>>> db
>>> from our main office in ca to ny as the ny system (public and outside
>>> of
>>> our firewall) has the need to generate non-critical read only invoice
>>> and
>>> inventory reports. our requirements are real simple and slony-i seems
>>> to
>>> be an overkill. we have also evaluated pgpool-ii but it was ruled out
>>> as
>>> it doesn't support x509 ssl connection (a must for business data).
>>> oralce
>>> and informix would have been nice as they both provide standby
>>> read-only
>>> databases that are very simple to manage. it is too bad that you cannot
>>> access a standby postgres database.
>>>
>>> so my question is anyone has any comments on what other tools out there
>>> that may allow us to create a postgres standby read-only database? if
>>> nothing we may just have to walk down the slony-i path...thanks ahead
>>> for
>>> any comments.
>>>
>>> regards,
>>>
>>> tim
>> If you go the route you intent on, I'd guess slony is your best option.
>> Of course there are other ways to do this too, like manually scripting a
>> db export import daily.
>>
>> However with knowing just the info you provided, setting up a
>> master-slave itself seems like overkill.  What about a VPN?  Or setting
>> up SL on it's own host?  My SL server isn't sharing it's IP with other
>> domains, so for me a default to deny firewall covers virtually all my
>> security needs.  You can always run SSL on it if you like.
>>
>
> --
> Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
> el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
> PO Box 8421             \     /   Please do NOT email to this address
> Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way
>
> -------------------------------------------------------------------------
> 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
>