Database PGSQL vs XML from Digest, Vol 157, Issue 20

[Serge Chabert]

Good morning,

Could you please tell me how to stop receiving emails as I think I have unsubscribed from the listing.

If not, please tell me how to unsubscribe.

I look forward to hearing from you.

Serge Chabert
photographyworks at aim.com
07939597293
Room 11
1 Orangefield place
Greenock
Inverclyde
PA15 1YX
United Kingdom

> On Apr 14, 2016, at 8:12 AM, Colin Law <clanlaw at gmail.com> wrote:
> 
> On 14 April 2016 at 01:14, John Angelico <talldad at kepl.com.au> wrote:
>> ...
>> Pardon me gentlemen, but are not the two parts of this reply in conflict?
> 
> No, though I see a possible ambiguity.
> 
>> 
>> First, "As Colin already writes" the database backend will write each change
>> immediately, not at the end of the session.
>> 
>> Then "the other part of Colin's reply is also correct" gnucash reads the
>> entire database into memory, and works there until the end of the session,
>> leading to the risk of data conflicts and corruption.
> 
> Gnucash does work in memory *and* it writes out changes to the db as
> they are entered.  The working is still in memory.  The key point is
> that it does not see any changes made by other users (if that were
> allowed), which could mean that the changes it later writes back could
> make the db inconsistent.
> 
>> 
>> Is there already a difference between the file handling under XML vs SQL?
> 
> Yes, as described, when it comes to the saving algorithm
> 
> Colin
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.