BSL277 — Not recommended using of RollbackTransaction method¶
Summary¶
Not recommended using of RollbackTransaction method
Identifiers¶
| Field | Value |
|---|---|
| Rule code | BSL277 |
| Compatible alias | WrongUseOfRollbackTransactionMethod |
| Severity | ERROR |
| Enabled by default | Yes |
| Implemented | Yes |
| Tags | transaction, error-handling |
Behavior¶
- The public identifier
BSL277and aliasWrongUseOfRollbackTransactionMethodare stable. - The rule reports the cases documented on this page.
- Suppressions and project configuration are applied before publication.
- The rule requires neither an external analyzer nor network access.
Configuration and suppression¶
BSL### is the primary stable identifier. The compatible alias is accepted
in select, ignore, and compatible block suppression comments.
All three suppression families support both a current line and a range. When an opening comment follows code, it affects only that line. Use any one form:
noqa:
bsl-disable:
- compatible
BSLLSform:
When the same opening comment is on a line by itself, it starts a range. Close it with the matching marker from the same family:
// noqa: BSL277
// code without this diagnostic
// noqa-enable: BSL277
// bsl-disable: BSL277
// code without this diagnostic
// bsl-enable: BSL277
// BSLLS:WrongUseOfRollbackTransactionMethod-off
// code without this diagnostic
// BSLLS:WrongUseOfRollbackTransactionMethod-on
To disable the rule until the end of the file, omit the closing
noqa-enable, bsl-enable, or BSLLS:…-on marker.
Opening and closing markers must belong to the same family.
Description¶
You should call at first RollbackTransaction method in Exception block, and then execute other actions if required.
Examples¶
BeginTransaction();
Attempt
CommitTransaction();
Exception
WriteLogEvent(NStr("en = 'OperationExecution'"),
EventLogLevel.Error,
,
,
DetailedErrorPresentation(InformationAboutError()));
RollbackTransaction();
CallException; // there is external transaction
EndTry;