Skip to content

Add [constraints] section to .pgschemaignore or to include a parameter to separate the creation of tables from the constraints. #429

@RicardoBorgesGO

Description

@RicardoBorgesGO

I have a scenario where the system is separated into large modules, each module has a separate schema, but there are foreign keys between these schemas, making it impossible to use pgschema for migrations.

One way to solve this would be to separate the table creation step from the constraint creation step, or to place the constraints in the .pgschemaignore file, where I would disable it initially and enable it on a second run.

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