Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-1266

Ensure referential integrity between subscription and subscription_capacity

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • 2023-05-30 - API
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      Currently, there is no foreign key relationship between subscription and subscription_capacity (even though both have a subscription_id column).  As part of SWATCH-1202 we need referential integrity between these two tables.

      We need to update the subscription syncing process in such a way that we aren't ending up with subscription_capacity records that don't have corresponding entries in the subscription table.

      Done:

      • No columns in subscription_capacity with subscription_ids that do not exist in the subscription table
      • Records will not be created in subscription_capacity that do not have corresponding records in subscription

            khowell@redhat.com Kevin Howell
            awood1@redhat.com Alex Wood
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: