Search

4.6. Transaction Wrapping Modes

download PDF
You can set your transaction wrapping to one of the following modes:
  1. ON
    This mode always wraps every command in a transaction without checking whether it is required. This is the safest mode.
  2. OFF
    This mode never automatically wraps a command in a transaction or checks whether it needs to wrap a command. This mode can be dangerous as it will allow multiple source updates outside of a transaction without an error. This mode has best performance for applications that do not use updates or transactions.
  3. DETECT
    This mode assumes that the user does not know how to execute multiple source updates in a transaction. JBoss Data Virtualization checks every command to see whether it is a multiple source update and wraps it in a transaction. If it is single source then it uses the source level command transaction.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.