kmradke_at_rockwellcollins.com wrote on Thu, Jun 30, 2011 at 13:46:46 -0500:
> Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote on 06/30/2011 01:41:51 PM:
> > > >> The reason SQLite was used is that rev props can be edited via svn
> > > >> prop*--revprop
> > > >>
> > > >> So you could also disable the pre-revprop-change hook during a
> backup
> > > >> and that should make you safe. And if you have not enabled it in
> the
> > > >> first place, then there is really no issue anyway.
> > > >>
> > > >
> > > > Inaccurate.
> > > >
> > > > The pre-revprop-change hook lives in libsvn_repos. It has zero
> effect
> > > > on API users that change revprop via libsvn_fs API's.
> > >
> > > OK, then what is accurate? Are you saying we do not support editing
> > > revision properties once they are packed? Is the SQLite db that
> > > stores revprops only written to by the pack process?
> >
> > It is possible to edit revprops both before and after 'svnadmin pack'.
> > In the 'after' case, a non-svn_fs_pack() process modifies revprops.db
> > in-place.
>
> I'm still not clear if a single .db file is used once a repo is packed,
> or if that .db file only holds the "packed" revprops and not the
> currently "unpacked" ones.
>
The latter.
> Or asked a different way, does a new commit update the revprop.db or
> does it just create files like 1.6 did and things are only added
> to the db during svnadmin pack...
>
The latter.
> Kevin R.
Received on 2011-06-30 20:49:29 CEST