Open topic with navigation

TIBCO® Patterns 6.1.2

# TIBCO Patterns Transactions versus RDBMS Transactions

Although transactions in TIBCO Patterns are similar to transactions in an RDBMS, the following are key differences:

| • | All reads are dirty reads: with most RDBMS, users can specify an isolation level when working with records and tables. That is, whether they want to see only the committed state or the “dirty” version of an object. TIBCO Patterns always shows the latest version of an object, even if that version has not yet been committed.

| • | Locks are not held between operations: instead of leaving items locked between operations within a transaction, TIBCO Patterns simply marks them as belonging to the transaction that updated them. If another operation, not associated with the same transaction, attempts to update the same item, instead of blocking that item, an error is returned.

These differences have many implications that are described in the following sections.

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.