Uploaded image for project: 'Hibernate ORM'
  1. HHH-11542

Allow the auto-commit resolution to be configurable for RESOURCE_LOCAL transactions

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.2.8
    • Fix Version/s: 5.2.10
    • Component/s: None
    • Labels:
      None

      Description

      For RESOURCE_LOCAL transactions, the Connection acquisition is not really delayed until the first Statement is needed to be executed because a Connection is acquired right after the Transaction has started since we need to read the auto-commit flag.

      However, if we know that we configured the underlying DataSource to set the auto-commit value to an explicit value, then we should provide a Hibernate configuration property which says what's that value so that we don't have to resolve it for every Connection that we fetch from the DataSource.

      By default, we fall back to the current behavior. But if the users want to optimize this process, they can provide that configuration property and bypass the check.

        Attachments

          Activity

            People

            • Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: