Automatic price quotes & PostgreSQL backend

[David]

So, it is an in-RAM app, with a big save?  The C++ and JAVA container objects lure one in that direction, along with virtual memory and large modern RAM.

Any chance it will grow up and use an RDBMS more normally?  When I hit enter, I expect the transaction left behind to be committed to disk, but instead the save button lights up!  There is not any auto-save, either.  No rollback button, either.    Why the failure to write?

 

 

 

-----Original Message-----
From: Derek Atkins <derek at ihtfp.com>
To: David <dgpickett at aol.com>
Cc: janssens-geert <janssens-geert at telenet.be>; gnucash-user <gnucash-user at gnucash.org>
Sent: Wed, Nov 6, 2013 4:09 pm
Subject: Re: Automatic price quotes & PostgreSQL backend



On Wed, November 6, 2013 3:56 pm, David wrote:
> No, I am xml, I just extended a related topic.  With SQL, there would not
> need to be locks outside the transactional ones of the RDBMS.

You would think so, but you would be wrong.

GnuCash loads all data into Core Memory at start time and runs it out of
there.  It does a full "database lock" to prevent a second instance from
writing into the database because the first instance would never see the
changes.

> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

-derek

-- 
       Derek Atkins                 617-623-3745
       derek at ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant