The following four tables show the effects of combined StopCondition and Allocate properties, based on a TransactionMode setting of short.
The following table shows the effects of a TransactionMode property setting of short, an Allocate property of request, and a StopCondition property of error.
Condition/Status |
Effects of settings on processing |
---|---|
Does a rollback occur on an error? |
The transaction rolls back immediately. |
What is the status of the connection after an error occurs? |
The connection ends. |
What happens if a begin transaction occurs? |
A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? |
A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? |
The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? |
The batch ends and a rollback occurs. |
When completed, is a batch job committed? |
The batch commits if no errors occur. |
After the batch commits, what is the status of the connection? |
The connection ends. |
The following table shows the effects of a TransactionMode property setting of short, an Allocate property of request, and a StopCondition property of none.
Condition/Status |
Effects of settings on processing |
---|---|
Does a rollback occur on an error? |
A rollback does not occur. |
What is the status of the connection after an error occurs? |
The connection continues. |
What happens if a begin transaction occurs? |
A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? |
A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? |
The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? |
The batch continues executing. |
When completed, is a batch job committed? |
The batch is always committed. |
After the batch commits, what is the status of the connection? |
The connection ends. |
The following table shows the effects of a TransactionMode property setting of short, an Allocate property of connect, and a StopCondition property of error.
Condition/Status |
Effects of settings on processing |
---|---|
Does a rollback occur on an error? |
The transaction rolls back immediately. |
What is the status of the connection after an error occurs? |
The connection continues. |
What happens if a begin transaction occurs? |
A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? |
A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? |
The request behaves the same as TransactionMode=long. |
While in batch, what happens if an error occurs? |
The batch request ends. |
When completed, is a batch job committed? |
The batch commits if no errors occur. |
After the batch commits, what is the status of the connection? |
The connection continues. |
The following table shows the effects of a TransactionMode property setting of short, an Allocate property of connect, and a StopCondition of none.
Condition/Status |
Effects of settings on processing |
---|---|
Does a rollback occur on an error? |
A rollback does not occur. |
What is the status of the connection after an error occurs? |
The connection continues. |
What happens if a begin transaction occurs? |
A commit occurs and uses begin transaction behavior described in Table 5-9. |
When the client application issues a commit or rollback, what happens? |
A commit or rollback occurs. |
If the request is a cursor or dynamic request, how does it behave? |
The request behaves the same as TransactionMode=long. |
In batch mode, what happens if an error occurs? |
The batch continues. |
When completed, is a batch job committed? |
The batch commit occurs, if no errors occur. |
After the batch commits, what is the status of the connection? |
The connection continues. |
Copyright © 2005. Sybase Inc. All rights reserved. |