Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix: integration should be unique per environment #1889

Merged
merged 1 commit into from Mar 20, 2024
Merged

fix: integration should be unique per environment #1889

merged 1 commit into from Mar 20, 2024

Commits on Mar 20, 2024

  1. fix: integration should be unique per environment 

    The unique constraint for integration is for unique_key, environment_id
and deleted_at which can be null. However null values are not considered
equal by default by postgres. :/

from postgres doc at https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-UNIQUE-CONSTRAINTS
> By default, two null values are not considered equal in this
comparison. That means even in the presence of a unique constraint it is
possible to store duplicate rows that contain a null value in at least
one of the constrained columns. This behavior can be changed by adding
the clause NULLS NOT DISTINCT
    @TBonnin
    TBonnin committed Mar 20, 2024
    Configuration menu
    Copy the full SHA
    66c9730 View commit details
    Browse the repository at this point in the history