On Fri, Jul 24, 2009 at 4:30 PM, Nikunj R. Mehta<[email protected]> wrote: > > On Jul 24, 2009, at 3:57 PM, Aaron Boodman wrote: > >> In some models (non-SQL) it may be easier to >> arrange a large update in the application layer and commit it all at >> once. In SQL, this is less true so it is important to provide API that >> makes conflicts impossible while a multi-step update is in progress. > > This problem exists in the WebStorage model [1]. More specifically, there is > no way to perform multiple updates atomically in it.
I agree. > The proposal that I have sketched about B-trees [2] does not have this > problem since it is possible to work with transactions to get the atomicity > as well as a desired isolation level. I take it that there are no issues > with that proposal since I have not heard anyone say so. I haven't reviewed that. I only chimed into this conversation because it looked like there were some misunderstandings and I worked on it early-on. - a
