[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: API policy

From: Greg Stein <gstein_at_gmail.com>
Date: Mon, 28 Mar 2011 08:26:44 -0400

On Mar 28, 2011 8:23 AM, "Philip Martin" <philip.martin_at_wandisco.com> wrote:
> Greg Stein <gstein_at_gmail.com> writes:
> > I recognize we need to grow the scope of transactions for speed
> > but let's do it in a way based on semantics rather than implementation.
> > example: to speed checkout, we could have an API to add a complete
> > of nodes, rather than an API to start/end a txn across those single
> > additions.
> That doesn't seem to fit with our current editor. When we want to add a
> directory we don't know the nodes. If we delay adding the directory
> until the nodes are known we would have to store the entire checkout
> somewhere else.

I'm well aware of the implications. I'm just trying to say: let's try to
avoid poisoning our entire WC library with SQL transaction concepts, which
should be restricted to just the internals of wc_db.

Received on 2011-03-28 14:27:15 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.