jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandru Popescu ☀" <the.mindstorm.mailingl...@gmail.com>
Subject Re: Isolation level inconsistency.
Date Fri, 20 Jul 2007 09:36:47 GMT
On 7/20/07, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> On 7/20/07, Alexandru Popescu ☀ <the.mindstorm.mailinglist@gmail.com> wrote:
> > On 7/20/07, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> > > Hi,
> > >
> > > On 7/20/07, Stefan Guggisberg <stefan.guggisberg@gmail.com> wrote:
> > > > AFAIK databases simply don't support the concept of transient changes.
> > > > please note that the JCR save() is not the equivalent of a db commit().
> > >
> > > Well said! A better analogue, as already mentoned, is Statement.execute().
> > >
> >
> > Hope you will not get angry on me :-), but an uncommitted change is a
> > transient change, so I do think RDBMS are using the transient concept.
>
> hehe, i won't ;) but i don't agree.

Great!

> IMO an INSERT, UPDATE or DELETE on
> database is the equivalent of a saved transient change in JCR.
>
> uncommitted (but saved) changes in JCR are the equivalent of uncommitted
> db changes. at least that's how i view it.
>

Now, you got me confused :-). What is a saved transient change and
what is an uncommitted but saved change?

tia,
./alex
--
.w( the_mindstorm )p.

> cheers
> stefan
>
> >
> > bests,
> > ./alex
> > --
> > .w( the_mindstorm )p.
> >
> > > BR,
> > >
> > > Jukka Zitting
> > >
> >
>
Mime
View raw message