Uploaded image for project: 'TorqueBox'
  1. TorqueBox
  2. TORQUE-732

Don't Automatically Attempt XA Connections to Non-Standard Database Keys in database.yml

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Done
    • 2.0.0.CR1
    • 2.0.0
    • None
    • None

    Description

      Right now we attempt an XA connection for one of development/test/production and any other non-standard keys we find in database.yml. Instead, only attempt XA for the database matching the current environment and require users to add xa: true to their database.yml to enable any others.

      It's way too common for users to have more than just development/test/production keys in database.yml and we don't want to fail a deployment just because we can't connect to a database that's not even needed.

      Attachments

        Activity

          People

            bbrownin@redhat.com Ben Browning
            bbrownin@redhat.com Ben Browning
            Archiver:
            samahaja@redhat.com Sagar Mahajan

            Dates

              Created:
              Updated:
              Resolved:
              Archived: