Subject | Re: [Firebird-Architect] Autonomous Transaction Routines |
---|---|
Author | Adriano dos Santos Fernandes |
Post date | 2007-11-02T14:51:59Z |
Jim Starkey wrote:
FWIW, the more useful thing would be if the autonomous block can see the
preceding change from the parent.
But this totally breaks the transaction control, as the autonomous block
may commit and the parent not. I.e., this is READ UNCOMMITTED.
that want FB to be stagnated without any other feature.
Adriano
> The implementation of commit retaining uses related transactions withFor what you want this?
> record visibility suitably fudged. The mechanism and fudge could
> probably be extended to take autonomous sub-transactions visible to the
> parent transactions.
>
FWIW, the more useful thing would be if the autonomous block can see the
preceding change from the parent.
But this totally breaks the transaction control, as the autonomous block
may commit and the parent not. I.e., this is READ UNCOMMITTED.
> If this discussion had started with a state of requirements rather thanSorry, but I'll not comment anymore on this type of comments from people
> a solution to an unstated problem, the choice might be easier.
>
> Gentlemen, may I suggest (again) that problems should precede solutions?
that want FB to be stagnated without any other feature.
Adriano