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:
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
On Wednesday 19 May 2010, Herbert Thoma wrote:
http://lwn.net/SubscriberLink/387967/cc502c0dc33d97d3/
Nice article. It makes some valid points like the lack of a concurrent access
prevention measure when using a database backend and the limited documentation
currently available for the new
Hi Tao,
Thank you for your patch. Unfortunately, you are mixing several unrelated
changes into one big patch. I'd prefer to see this split into several separate
patches for good reasons.
Before I make a suggestion to split the changes, I'll add my comments in your
message:
On Tuesday 18 May
On Tuesday 18 May 2010, Bill Nottingham wrote:
1) libdbi, in its default configuration, puts the driver directory
in $libdir/dbd, not a hardcoded /usr/lib/dbd. Fix gnucash's configury
to use the same.
2) If GNC_DBD_DIR is not set, fall back to the libdbi compiled-in default
(whatever it may
Geert Janssens (janssens-ge...@telenet.be) said:
Obviously, it's easy to configure with --with-dbi-dbd-path pointing at the
proper location for development and all is well.
I just wonder if it's possible to rewrite configure in such a way that it
always does the right thing. I mean is
Dear Dev's,
The Windows nightly builds have not been successfully built since r19153. I
am sure you are already aware of this.
Regards,
Kim
--
View this message in context:
http://gnucash.1415818.n4.nabble.com/Window-Nightly-Build-Failed-tp2220988p2220988.html
Sent from the GnuCash - Dev
Valdis Vītoliņš valdis.vitol...@odo.lv writes:
The problem for newcomer is, that Hello world report doesn't seem as an
example
but as an superset of (too much) possibilities, which is hard to
understand.
If it is _really_ simple example, it is little bit scary...
The hello-world report is a
On Tuesday 18 May 2010, Kim Wood wrote:
Dear Dev's,
The Windows nightly builds have not been successfully built since r19153.
I am sure you are already aware of this.
Regards,
Kim
Thanks for the heads up. I wasn't following the windows builds.
It turns out an installer translation
Hi,
Tao Wang dancef...@gmail.com writes:
5) Update 'php-gettext' to 1.0.10
I cannot find any RPM package named php-gettext, so I have no idea how
to update this at all. Most likely this update will have to wait until
the system is upgraded to FC13.
I still don't see why we're going through
On Wednesday 19 May 2010, Derek Atkins wrote:
Hi,
Tao Wang dancef...@gmail.com writes:
5) Update 'php-gettext' to 1.0.10
I cannot find any RPM package named php-gettext, so I have no idea how
to update this at all. Most likely this update will have to wait until
the system is upgraded
On Thu, May 20, 2010 at 2:44 AM, Geert Janssens
janssens-ge...@telenet.be wrote:
On Wednesday 19 May 2010, Derek Atkins wrote:
Hi,
Tao Wang dancef...@gmail.com writes:
5) Update 'php-gettext' to 1.0.10
I cannot find any RPM package named php-gettext, so I have no idea how
to update this
I think I understand at least some of the reasons for GC being single-user,
but I'm curious if there's been any more thought lately to building
multi-user functionality into GnuCash in future?
Cheers,
-- Erik Anderson
On Wed, May 19, 2010 at 1:58 AM, Christian Stimming stimm...@tuhh.dewrote:
I think there is a big difference between concurrent multi use and serial multi
use. I would like to be able to use GnuCash with the same remote database, but
from different computers at different times. This would be serial multi use.
The system should ideally protect against any use that
Hi,
I'm working on Bug 618646, and it's almost done, but I have a problem
and don't know how to do it correctly.
The problem is that there is libgncmod*.dll are installed in
lib/gnucash, $pkglibdir, however, gnucash-bin.exe are installed in
bin/.
There are some libgncmod*.dll are linked with
On Wed, May 19, 2010 at 6:58 PM, Christian Stimming stimm...@tuhh.de wrote:
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
Derek et al,
A chargeback as you mentioned, would work if we had line item feature.
Inventory module is excessive, as basically I just open the box/bag and look
to see how many jacks I have left. The whole intent here is to provide an
invoice, an expense report, as exempt, otherwise, it's common
I am using GnuCash 2.2.9 and customizing fancy-invoice.scm (and trying
to learn Guile/Scheme) I am trying to display the Job ID on the invoice
but nothing I try works and I can't seem to find any samples that use
any sort of gncJobGetID or such. I feel like a monkey pounding on a
keyboard.
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
On Thu, May 20, 2010 at 2:23 AM, Geert Janssens
janssens-ge...@telenet.be wrote:
On Tuesday 18 May 2010, Kim Wood wrote:
Dear Dev's,
The Windows nightly builds have not been successfully built since r19153.
I am sure you are already aware of this.
Regards,
Kim
Thanks for the heads up.
Tao,
Your solution to block the whole database is good enough for me.
Thanks,
Per.
On May 19, 2010, at 2:26 PM, Tao Wang wrote:
On Wed, May 19, 2010 at 6:58 PM, Christian Stimming stimm...@tuhh.de wrote:
The article raises one valid serious concern: The database backend does
nothing to
On 19 May 2010, at 11:47 PM, Per Kjeldaas wrote:
Your solution to block the whole database is good enough for me.
It's a real shame that a system fundamentally designed to offer multi
user access to data should be crippled in such a fashion. In the
process, virtually all reasons to use a
22 matches
Mail list logo
