Skip to content

persistent-postgresql getColumn throws an error when a column has more than one foreign key constraint #1009

@jkeuhlen

Description

@jkeuhlen

As discussed on #979, there is currently a bug in persistent-postgresql that causes migrations to fail when there is more than one constraint on a single column.

This is an issue when you have e.g. a foreign key to a field and a compound foreign key with that same field included as shown in #979 (comment).

I've already written a failing test on another branch, and @robbassi has an incoming PR to fix this issue, so this is just for documentation purposes.

Metadata

Metadata

Assignees

No one assigned

    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