Phil,
Thank you for enlighting the multiuser/concurrent usage problem.
I wouldn't like to suppress the importance of point 3) and especially point
1).
Just, let me couple of thoughts on point 2) since I walked into that.
jsled noted that resolving ad 2) would require some serious re-a
Phil Longstaff wrote:
> 1) locking/transactions - db transactions are used whenever an object is
> written or updated. However, no locking is done, and there are certain cases
> where related objects are not saved in the same db transaction, because the
> back-end does not have enough informat
Thanks for the info. I have added some more comments inside your replies.
>From what I understood by following the dev list, converting gnucash to a true
db based application is at best a long-term goal. That would solve the multi-
user aspects automatically, as the consistency in concurrent acce
On September 6, 2009 06:37:32 am Geert Janssens wrote:
> Hi,
>
> I'm very interested to use the new db backend in the upcoming 2.4 series.
>
> Thinking about this, I was wondering if the current implementation deals
> well with multi-user access to the same db. I mean can two users from two
> diffe
Hi,
I'm very interested to use the new db backend in the upcoming 2.4 series.
Thinking about this, I was wondering if the current implementation deals well
with multi-user access to the same db. I mean can two users from two different
computers use gnucash with the same (postgres or mysql) gnuc
