Use the SQL Transaction builder to define a sequence of SQL DataSources, Statements, and Transforms that are to be executed as part of a transaction.
This builder scans the model in which it resides and locates these SQL builders and then makes them available as input choices for constructing transaction steps. Similar to an action list entry, a transaction step allows you to combine these other SQL builders in different ways. Thus you can create unique transactions that leverage and reuse DataSources and Transforms.
To create a transactional context, this builder caches JDBC connections obtained from the DataSources defined in the transaction steps. As a result, JDBC connections may be held open by this builder until the model executes a commit or rollback on the transaction. Once such an operation occurs, the cached connections are released to the DataSource. If your model uses the SQL Transaction builder, you should make sure that any executed transactions are explicitly committed or rolled back by the model. Failure to do so may result in the underlying DataSources running out of JDBC connections.
This builder provides the following input groups:
A builder name, isolation level, and one or more named transaction steps are required inputs.Transaction timeout settings
(optional) Used to determine the action taken (commit or rollback) when a transaction times out for any reason.Events, statistics and logging
(optional) Used to enable and disable events and statistics gathering related to the transaction.
Remember to commit
Parent topic: Builder Reference: wpf7
About using the builder call editor: wpf7
Working with a database: wpf7