You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins-Sussman <su...@newton.ch.collab.net> on 2001/03/06 20:57:19 UTC
svn_fs_commit_txn
To Do: svn_fs_commit_txn() probably needs to take a "log message"
argument.
If the system crashes after the commit succeeds, but before we call
svn_fs_revision_prop (log_msg), then we'd end up with a new revision
sans log message. We need to make the "setting the log message" part
of the *same* db txn that executes within svn_fs_commit_txn --
probably by passing it right in.
Re: svn_fs_commit_txn
Posted by Jim Blandy <ji...@zwingli.cygnus.com>.
Ben Collins-Sussman <su...@newton.ch.collab.net> writes:
> To Do: svn_fs_commit_txn() probably needs to take a "log message"
> argument.
>
> If the system crashes after the commit succeeds, but before we call
> svn_fs_revision_prop (log_msg), then we'd end up with a new revision
> sans log message. We need to make the "setting the log message" part
> of the *same* db txn that executes within svn_fs_commit_txn --
> probably by passing it right in.
It would be more graceful, I think, to add properties to transactions,
just as we have properties for revisions. When a transaction is
successfully committed, its properties would become the revision's
properties.