Transactions

A transaction is a group of write operations that can be committed or rolled back as a unit. A write operation is any operation that changes the existence or content of data on the Patterns server. The following is a complete list of write operations:

•

Table load, delete, move, checkpoint, and restore

•

Record add, delete, update, and replace

•

Thesaurus create and delete

•

Character Map create

•

Learn Model create and delete

Each DevKit function associated with a write operation has two versions: the backwards-compatible non-transactional version and a new transactional version that takes an additional transaction ID parameter. The transactional functions are named by the convention of suffixing “T” to the non-transactional name. For example, lkt_dbload for transactional would be lkt_dbloadT.

Calling a transactional function with an LPAR_NULL transaction parameter is the same as calling the non-transactional version.

If the application uses transactions, or if a cluster is in use, DevKit functions might return error codes which include: DVK_ERR_TRAN_UNKNOWN, DVK_ERR_TRAN_IN_USE, and DVK_ERR_TRANCONFLICT. For more information, see the TIBCO Patterns Concepts guide.

Read operations are not affected by the use of transactions.