[p4] Perforce transactional processing - Stephen Vance - com.perforce.perforce-user

8 messages in com.perforce.perforce-user[p4] Perforce transactional processing

From	Sent On	Attachments
Slawek Pelka	05 May 2003 06:14
Stephen Vance	05 May 2003 07:13
Slawek Pelka	06 May 2003 01:43
Stephen Vance	06 May 2003 04:01
Slawek Pelka	06 May 2003 04:07
Stephen Vance	06 May 2003 06:16
Slawek Pelka	06 May 2003 06:24
Stephen Vance	06 May 2003 06:37

Subject:	[p4] Perforce transactional processing
From:	Stephen Vance (ste...@vance.com)
Date:	05/06/2003 04:01:12 AM
List:	com.perforce.perforce-user

Are you looking for a form of distributed super-changelist? It sounds like you are looking for transactional boundaries around multiple submissions. This can be partially achieved by isolating the sequence of changelists to a dedicated branch. Then they will integrate back to the parent as a single transaction, but you will have the history of all three in the integration history.

I don't understand step 2. Why would you put it to another machine before calling Perforce? Please clarify.

At 10:43 AM 5/6/2003 +0200, Slawek Pelka wrote:

It's OK. I use something like you described. But lets imagine such a scenario: 1. gather all info about change and files which are contained there 2. send those info to the other machine 3. on the other machine: put data to perforce and update info in db what has been replicated If db operation went bad I would need a method of get the change back from the perforce.

In other words: I'd love to have a functionality like this:

perforce.openTransaction perforce.putChange perforce.putChange perforce.putChange if something_goes_wrong perforce.rollbackTransaction else perforce.commitTransaction

Greets, Slawek

----- Original Message ----- From: "Stephen Vance" <steve at vance.com> To: "Slawek Pelka" <Slawek.Pelka at globalintech.pl>; <perforce-user at perforce.com> Sent: Monday, May 05, 2003 4:13 PM Subject: Re: [p4] Perforce transactional processing

I will attempt an answer, but I'm not sure I understand your question. If I miss the mark, please clarify the question.

Perforce changelists give you nice atomic transactions. You can automate changelist submissions with the -i and -o flags. This is particularly easy with "here" files in Bourne and Korn shell scripting. You can also modify the change template to insert comments or manipulate the file list through a good text manipulation language like Perl. The following captures the basic idea:

p4 change -o 1234 | manipulatethechangelist.pl | p4 submit -i

At 03:14 PM 5/5/2003 +0200, Slawek Pelka wrote:

While working on the preforce replication project I'd found that there is one very nice feature missing. I couldn't implement transactional processing of inserting changes into perforce.

Has anybody solved that issue?

Stephen Vance mailto:steve at vance.com http://www.vance.com/