We need to prevent multi-user access to the SQL backend (Re: New GnuCash article on LWN)
Derek Atkins
warlord at MIT.EDU
Thu May 20 12:33:28 EDT 2010
Valdis Vītoliņš <valdis.vitolins at odo.lv> writes:
> I vote for not over-engineered solution and, I suppose simple lock for
> all database (only one can write) is OK.
>
> My clients/partners will not use SQL backend. They use Gnucash because
> it can be installed and used as many other standalone applications.
> It is important, that Gnucash save data in file, which can be easy
> copied, opened from shared filesystem, and it can be easily opened by
> doubleclick
> similarly to other used files in office applications.
FWIW, SQLite provides that.
> There are plenty of client-server accounting applications, I have looked
> at LedgerSMB and even play around Openbravo.
> But these are much more complicated, than Gnucash (especially on Linux)
> which can install every accountant himself.
>
> I believe most of Gnucash users are still private, not business users,
> so
> please don't rate easiness too outdated and/or unimportant.
>
> Valdis
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
warlord at MIT.EDU PGP key available
More information about the gnucash-devel
mailing list