Thanks, Herbert, for the link.
The article raises one valid serious concern: The database backend
does nothing to prevent multiple user access. This is bad because
simultaneous access to the SQL database from multiple users will
almost surely cause data loss. On the other hand, the technology term
"SQL backend" will almost surely raise the user expectation that
multiple user access were possible, so for sure people will give it a
try. Since it will corrupt their data, we need to build in some
prevention measure - the equivalent of the "lock file", but inside the
SQL database. Ideas, anyone?
Also, it's amusing to me to see the "cutecash" project already
mentioned in there, even though it's only accessible through the SVN
sources :-)
Regards,
Christian
Zitat von Herbert Thoma <herbert.th...@iis.fraunhofer.de>:
http://lwn.net/SubscriberLink/387967/cc502c0dc33d97d3/
--
Herbert Thoma
Dipl.-Ing., MBA
Head of Video Group
Multimedia Realtime Systems Department
Fraunhofer IIS
Am Wolfsmantel 33, 91058 Erlangen, Germany
Phone: +49-9131-776-6130
Fax: +49-9131-776-6099
email: t...@iis.fhg.de
www: http://www.iis.fhg.de/
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
