| Subject | Re: [IB-Architect] SQL Scripts |
|---|---|
| Author | Marco Lauria |
| Post date | 2001-12-10T15:24:58Z |
At 09.13 10/12/2001 -0500, you wrote:
on the server.
However I could have a single transaction in every job....
it's the same....
Also I use IB/FB for the most part of my time so I don't need them.
It was a spoke about nested transactions and I was explaining an
example in which I would have found them useful.
Regards
Marco
P.S. As I told in my message, every job was a part of a bigger job,
so that I would have the need to roll back only a part of the inner job and
not the entire transaction that is the entire JOB.
>----- Original Message -----I suppose that nested transactions are useful for implementing Long SQL Jobs
>From: "Marco Lauria" <mslauria@...>
>To: <IB-Architect@yahoogroups.com>
>Sent: Friday, December 07, 2001 5:45 PM
>Subject: Re: [IB-Architect] SQL Scripts
>
>
> > Also I am thinking now about nested transactions, but
> > FB doesn't support them...
> > and it is another story.
>
>Hi Marco,
>
>I can't catch the situation nested transactions is usefull for.
>It seems to me they are cumbersome somehow: if you are rollbacked from
>inside transaction because of another concurrent transaction changed record
>first
>then you should be rollbacked from outside transaction as well
>if concurrent transaction have been committed.
>
>or I missed something,
on the server.
However I could have a single transaction in every job....
it's the same....
Also I use IB/FB for the most part of my time so I don't need them.
It was a spoke about nested transactions and I was explaining an
example in which I would have found them useful.
Regards
Marco
P.S. As I told in my message, every job was a part of a bigger job,
so that I would have the need to roll back only a part of the inner job and
not the entire transaction that is the entire JOB.