Re: [Perl-workflow-devel] AutoCommit in workflow

[Jonas B. N. <jo...@gm...>]

On 06/04/2008, at 23.50, Andrew O'Brien wrote:
>
>> Hello all,
>
>> Workflow defaults to AutoCommit and I was wondering if there would be
>> any interest in allowing this to be a passed in parameter. We could
>> still allow AutoCommit to be set, but we could also put in manual
>> commits at appropriate points in a transaction. This would result in
>> some warnings from DBI whan you manually ran the commits (unless we
>> shielded the commits with a test for AutoCommit).
>>
>> Any thoughts one way or the other?
>
> I certainly don't see any issue with allowing the AutoCommit setting  
> to
> be overridden as long as the default remains the same so we don't
> surprise too many people :)
>
> I know that we assume AutoCommit is on by default, for example.
>
> As long at the extra commits that are added into the Workflow codebase
> are optionally executed depending on the AutoCommit setting then the
> real question then becomes one of intent:
>
> Are you intending that Workflow still commits regularly internally
> (which is what I think you're saying) or are you intending to never  
> call
> commit in the Workflow codebase at all and leave that to the external
> application?
>

Hmmm this might be the actual challenge, from my standpoint; the  
workflow engine should keep it own state and transactions. But getting  
this to balance with transactions in applications utilizing Workflow,  
might be a question of discipline and can prove - difficult.

> Cheers,
>
> Andrew
>

jonasbn