<Connection variable>.TransactionEnd (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

Help

WLanguage

Managing databases

Managing transactions

WLanguage functions

Prefix syntax

TransactionEnd

Presentation

Example

Error cases

Handling records during a transaction

Transactions and independent HFSQL context

OLE DB and Native Connectors

See also

<Connection variable>.TransactionEnd (Function)

In french: <Variable Connexion>.TransactionFin

Not available with this kind of connection

Validates the current transaction:

the modifications performed on the data file since the start of transaction (<Connection variable>.TransactionStart or <Connection variable>.Transaction) are validated.
the transaction file is deleted (if this transaction is the last transaction in progress for a network application).
the records locked in read-only by the transaction are unlocked.

The management of transactions is available for HFSQL Client/Server databases.

Example

MyConnection1 is Connection

// Start transaction on data files associated with MyConnection1
MyConnection1.TransactionStart()

// Code used to prepare the order to added
// ...

WHEN EXCEPTION IN
// Add the order
Order.Add()
// Validate the addition
MyConnection1.TransactionEnd()
DO
// Delete the order lines
MyConnection1.TransactionCancel()
END

Syntax

Validating a transaction in progress on a connection Hide the details

<Result> = <Connection>.TransactionEnd()

<Result>: Boolean

True if the transaction is ended,
False if a problem occurs. HErrorInfo returns more details about the error.
Caution: The function has no effect if a global transaction is started. The syntax 2 must be used.

<Connection>: Connection variable

Name of the Connection variable that describes the connection to use.

Validating a global transaction in progress Hide the details

<Result> = TransactionEnd()

<Result>: Boolean

True if the transaction is ended,
False if a problem occurs. HErrorInfo returns more details about the error.

Remarks

Error cases

Nesting transactions: Transactions cannot be nested (i.e. <Connection variable>.TransactionStart or <Connection variable>.Transaction cannot be called in a transaction). In this case, error 70031 occurs.
A fatal error is displayed in the following cases:
- A transaction is started on all the connections while there is at least one connection in transaction.
- A transaction is started on a connection while a transaction was already started on all the connections.
- A transaction is started on all the connections while there is at least one connection whose isolation mode is not "Read Uncommitted".

Handling records during a transaction

During a transaction, some rules must be complied with when handling the records. For more details, see Transactions: Handling records during a transaction.

Transactions and independent HFSQL context

When copying a context, if a transaction is in progress on the first context, the new context is not in transaction. You must call <Connection variable>.TransactionStart (or <Connection variable>.Transaction) to start a transaction in the new context.

OLE DB and Native Connectors

Only syntaxes with connection are taken into account by the Native Connectors (also called Native Accesses) that support transactions. You can also use SQLTransaction.

Component: wd270hf.dll