Rollback changes on a transactional context

[Sergio Graça <se...@gmail.com>]

Hi all,

I would like to know if it is possible to create a transactional context
over repository operations.

For example, encapsulating two or more commands inside a transactional
context and in case one of them doesn't work, rollback all the previous
commands in the transaction.

Thank you very much,

Sergio

Re: Rollback changes on a transactional context

[Andy Levy <an...@gmail.com>]

On 8/23/07, Sergio Graça <se...@gmail.com> wrote:
> I am sorry,
>
> I didn't made myself clear enough.
>
> What I am asking is if it is possible to have two different svn commands in
> an unique transactional context.
>
> For example, two svn copy commands.

If they're in the same working copy, yes, it does this already.

If you need to operate on URLs, not a WC, look into svnmucc.

If you need to operate on multiple WCs, I don't think you can.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Rollback changes on a transactional context

[Sergio Graça <se...@gmail.com>]

I am sorry,

I didn't made myself clear enough.

What I am asking is if it is possible to have two different svn commands in
an unique transactional context.

For example, two svn copy commands.

thanks a lot



On 8/23/07, Andy Levy <an...@gmail.com> wrote:
>
> On 8/23/07, Sergio Graça <se...@gmail.com> wrote:
> > Hi all,
> >
> > I would like to know if it is possible to create a transactional context
> > over repository operations.
> >
> > For example, encapsulating two or more commands inside a transactional
> > context and in case one of them doesn't work, rollback all the previous
> > commands in the transaction.
>
> Maybe I'm missing something, but what you're asking for is one of the
> core features of Subversion. Every commit is atomic & transactional -
> if the entire commit doesn't succeed, none of the changes are saved in
> the repository. You can do multiple adds, deletes, moves, and content
> changes in each commit.
>

Re: Rollback changes on a transactional context

[Andy Levy <an...@gmail.com>]

On 8/23/07, Sergio Graça <se...@gmail.com> wrote:
> Hi all,
>
> I would like to know if it is possible to create a transactional context
> over repository operations.
>
> For example, encapsulating two or more commands inside a transactional
> context and in case one of them doesn't work, rollback all the previous
> commands in the transaction.

Maybe I'm missing something, but what you're asking for is one of the
core features of Subversion. Every commit is atomic & transactional -
if the entire commit doesn't succeed, none of the changes are saved in
the repository. You can do multiple adds, deletes, moves, and content
changes in each commit.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org