Skip to content

Fixing and standardizing UNIQUE_CONSTRAINTS and PKs - #9

Open
dpb-bah wants to merge 4 commits into
qatfrom
standardizing-pks-unique-constraints
Open

Fixing and standardizing UNIQUE_CONSTRAINTS and PKs#9
dpb-bah wants to merge 4 commits into
qatfrom
standardizing-pks-unique-constraints

Conversation

@dpb-bah

@dpb-bah dpb-bah commented May 21, 2026

Copy link
Copy Markdown
Contributor

Description:

Cleanup PR to standardize and fix the current PKs and UNIQUE_CONSTRAINTS.

Technical Details:

Added TODO to prioritize the uniqueness validation of the PK and UNIQUE_CONSTRAINTS.

Requirements for PR Merge:

  1. Unit & integration tests updated
  2. Documentation updated
  3. Data validation completed (examples listed below)
    1. Is performance impacted in the changes (e.g., API, pipeline, downloads, etc.)?
    2. Is the expected data returned with the expected format?
  4. Appropriate Operations ticket(s) created
  5. Jira Ticket(s)
    1. N/A
  6. Broker Developer Review
  7. USAS Developer Review

Explain N/A in above checklist:

Not ticket necessary as it's just cleanup.

@dpb-bah dpb-bah changed the title Fixing and standardizing unique_constraints and PKs Fixing and standardizing UNIQUE_CONSTRAINTS and PKs May 21, 2026
alburde1
alburde1 previously approved these changes May 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants