You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Hudson <gh...@MIT.EDU> on 2004/12/20 17:14:48 UTC
Re: svn commit: r12445 - trunk/www
On Mon, 2004-12-20 at 11:30, dionisos@tigris.org wrote:
> @@ -924,6 +924,10 @@
> operations by comparing two trees. One tree is the usually the HEAD
> revision, and the other is often a temporary transaction-tree -- thus
> the need for write access.</p>
> +
> +<p>This limitation only applies to the bdb backend; the <a
> +href="http://svnbook.red-bean.com/svnbook-1.1/ch05.html#svn-ch-5-sect-1.2.A">FSFS
> +backend</a> does not exhibit this behaviour.</p>
This edit renders the answer a mismash of false and true information.
We never use a temporary transaction tree to perform a read-only
operation any more.
It seems like it should be possible to make BDB repositories read-only
for read operations. RPM manages it, after all. I think the last time
I checked, RPM opens the database without an environment if it doesn't
have write access, but I don't know if I remember that correctly and I
don't know if it's safe to do so.
(We'd also have to make sure we're not creating DB transactions for read
operations. There's never any reason to do so, right?)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn commit: r12445 - trunk/www
Posted by Erik Huelsmann <eh...@gmail.com>.
On Mon, 20 Dec 2004 12:14:48 -0500, Greg Hudson <gh...@mit.edu> wrote:
> On Mon, 2004-12-20 at 11:30, dionisos@tigris.org wrote:
> > @@ -924,6 +924,10 @@
> > operations by comparing two trees. One tree is the usually the HEAD
> > revision, and the other is often a temporary transaction-tree -- thus
> > the need for write access.</p>
> > +
> > +<p>This limitation only applies to the bdb backend; the <a
> > +href="http://svnbook.red-bean.com/svnbook-1.1/ch05.html#svn-ch-5-sect-1.2.A">FSFS
> > +backend</a> does not exhibit this behaviour.</p>
>
> This edit renders the answer a mismash of false and true information.
> We never use a temporary transaction tree to perform a read-only
> operation any more.
Ok. How about I change the question to include 'bdb' instead?
> It seems like it should be possible to make BDB repositories read-only
> for read operations. RPM manages it, after all. I think the last time
> I checked, RPM opens the database without an environment if it doesn't
> have write access, but I don't know if I remember that correctly and I
> don't know if it's safe to do so.
>
> (We'd also have to make sure we're not creating DB transactions for read
> operations. There's never any reason to do so, right?)
I'd love to do something like this, but as long as we don't have it, I
guess my edit to the faq is relevant (whatever the words may end up to
be) ....
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org