| Subject | Re: [firebird-support] Stored Procedure Scope |
|---|---|
| Author | Helen Borrie |
| Post date | 2005-10-22T01:28:07Z |
At 04:09 PM 21/10/2005 -0400, you wrote:
Like everything else inside a transaction, what's done is visible only to
the transaction that does it, until the work is committed. So, for
example, if you rattle off a series of SPs from a single transaction, each
doing something in the database on which the next SP depends, any change
posted by the previous SP is visible to the next....right up to the time
you end the transaction with commit or rollback. Rollback would undo
everything and the database state would be unaffected by anything done in
your transaction.
./heLen
>Just a quick question... or more, a confirmation of what I do/don't know...Yes
>
>Does what happen in a stored procedure belong to the transaction it was called
>in,
>or is it immediately applied,yes
>and seperate?No.
Like everything else inside a transaction, what's done is visible only to
the transaction that does it, until the work is committed. So, for
example, if you rattle off a series of SPs from a single transaction, each
doing something in the database on which the next SP depends, any change
posted by the previous SP is visible to the next....right up to the time
you end the transaction with commit or rollback. Rollback would undo
everything and the database state would be unaffected by anything done in
your transaction.
./heLen