On Tue, 28 Dec 1999 14:41:01 PST, the world broke into rejoicing as
Dave Peticolas <[EMAIL PROTECTED]> said:
> > Perhaps we need a more distributed-data model? Whenever you have an
> > account 'open', you register a callback with the 'data store'. Then,
> > whenever someone modifies the data st
On 28 Dec 1999 11:23:44 EST, the world broke into rejoicing as
Derek Atkins <[EMAIL PROTECTED]> said:
> OTOH, you're right. I wouldn't want to be locked out of an account
> because someone else didn't close their windows when they went to
> lunch.
This is exactly why I was promoting the idea of
On Wed, 29 Dec 1999, you wrote:
> OTOH, you're right. I wouldn't want to be locked out of an account
> because someone else didn't close their windows when they went to
> lunch.
The "standard" DBMS way of handling this is to lock the record being updated
and apply a transaction timer such that
> So you are suggesting a flag-on-commit? The problem with CVS is that
> before you can commit you have to 'update' yourself and then, as a
> user, you have to clear any conflicts before you can actually commit.
> With an active repository with many users this is obviously a highly
> iterative pr
So you are suggesting a flag-on-commit? The problem with CVS is that
before you can commit you have to 'update' yourself and then, as a
user, you have to clear any conflicts before you can actually commit.
With an active repository with many users this is obviously a highly
iterative process. I'
I have no objection to the 'Data Store API'. If you plan to really
build a Data Store API, and along side you happen to build an
experimental (or reference) implementation that uses the API and it
happens to use a 'transaction-per-directory' model, that's fine with
me. It shows that the API work
Kevin A. Foss writes:
> On a vaguely related note -- as more of a user of GnuCash right now
> than anything, are there any plans to implement a way to separate out
> data for years. E.g., I would like to be able to keep a running
> register with cumuluative up-to-date statistics for all of d
> On Tue, 28 Dec 1999 00:10:50 -0500 (EST), [EMAIL PROTECTED] said:
linas> As I walk through my email, I haven't yet uncovered the
linas> original note, so I can't say. But how about trying an
it is in the archives, I am sure. :-)
linas> alternate approach: write out what a user might ty
