Skip to content

Distinct null values on IssueLink constraints #2537

@La0

Description

@La0

While working on #2536 I found out that we can have duplicate IssueLink with the same positioning arguments (nb_lines, line, char), provided one of these values is NULL.

This is because Django defaults (and the databases default behaviour) makes the nullable values as distinct ones (so it does not trigger the constraint).

If I understand correctly the notes on Django doc, only Postgresql 15+ is supported to use nulls_distinct=False

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions