Open topic with navigation

TIBCO® Patterns 6.1.2

# 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.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO® Patterns

Copyright © 2010-2025. Cloud Software Group, Inc. All Rights Reserved.