Strange behavior of GNUCash on large database

[Mike or Penny Novack]

Perhaps you might tell us how you "poured in" those transactions. I take 
it that since you are talking about a large volume, you weren't entering 
them one at a time by hand.

Many of us have been using gnucash for years and so have lots of 
transactions. So rather than consider where there is some "limitation" 
the first step should be to confirm that what you "poured in" were 
correct transactions.

Might be a language problem, but what did you mean by "It mixes income 
and expenses column" (and displays sum incorrectly). In basic accounting 
terms, there are income and expense ACCOUNTS and each of these has a 
debit side and a credit side (columns). Normally a transaction entered 
into an expense account would have the amount in the debit column and a 
transaction entered into an income account would have the mount in the 
credit column.

Michale D Novack

On 1/23/2017 3:43 AM, perillamint via gnucash-user wrote:
> Hello,
>
> I'm trying to write NodeJS lib which manipulates GNUCash's postgres DB.
>
> In small number of transactions (10k), it works fine. However, When I
> pour lots of transactions(about 50k) in DB, it starts strange behavior.
>
> It mixes income and expenses column and displays sum incorrectly.
> (negative value)
>
> I guess this caused by limitation of GNUcash's ability to handle large
> data. Is there any documented limitation of GNUcash? or does anyone have
> experience like this?
>
> Thanks.