Re: hamsterdb Transactional Storage (thanks to all of you)
Date: Wed, 22 Jul 2009 04:21:18 -0700 (PDT)
Message-ID: <cda19040-d15e-4d76-a60a-13eea150427f_at_13g2000prl.googlegroups.com>
On Jul 20, 2:26 am, Christoph Rupp <cruppst..._at_gmail.com> wrote:
> Whitepaper:http://hamsterdb.com/public/dl/hamsterdb2_technical_overview.pdf
quoting now from the white paper:
>> (a conflict occurs if another active Transaction is modifying the same Database key. >>If a conflict is discovered, the operation returns with an error. in other words, a transaction locks a key.
>> only one Transaction isolation level is supported: "read committed"
no, it is not.
yes you prevent dirty reads, but concurrent transactions must all
finish
(unless one rolls itself back on a constraint violation).
you have to support concurrency before "isolation level" makes any
sense.
you still don't understand the basic concepts.
philip Received on Wed Jul 22 2009 - 13:21:18 CEST