Ben Collins-Sussman <email@example.com> writes:
> > I think he meant:
> > Jane starts a Subversion txn.
> > Bill starts a Subversion txn.
> > Jane makes a change to node N in her txn.
> > Bill makes a change against the same base revision of N, in his txn.
> > Jane aborts her txn.
> > Bill commits his txn.
> Yup. Aborted transactions result in deleted node-revisions.
> My thoughts weren't as complex as Karl's, though; if Jane begins and
> then aborts a transaction -- acting alone -- the deleted node-revision
> numbers will never be recycled, right? The next person who comes
> along and clones the same node as Jane is going to get the "next"
> node-rev num, beyond the deleted one.
No, they will be recycled. Remember, when Jane aborts her txn, all
new node revisions created in that txn get deleted from the database
(those node revs are invisible to the revision roots -- they're
"garbage", in the sense that a floodfill from the any revision root
can never reach them).
Received on Sat Oct 21 14:36:25 2006
This is an archived mail posted to the Subversion Dev