Uploaded image for project: 'PuppetDB'
  1. PuppetDB
  2. PDB-4314

Look for improperly used unique constraints

    Details

    • Type: Bug
    • Status: Ready for Engineering
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: PuppetDB
    • Labels:
      None
    • Template:
    • Team:
      PuppetDB
    • Method Found:
      Needs Assessment
    • QA Risk Assessment:
      Needs Assessment

      Description

      In PDB-4312, we discovered that the unique constraint on the resource_events table didn't work as desired, since one of the columns allowed null.

      Look through the schema and find any unique constraints that have columns that allow nulls and address accordingly (via migrations, etc)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              robert.roland Robert Roland
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Zendesk Support