Skip to content

Handle tables with missing PK #221

Open
@fernandinand

Description

@fernandinand

Currently, geodiff copy command fails if a given target tables does not have a PK implemented.
Despite this is not generally the best approach (not to have any PK), we need to handle this properly and provide some hints/output to user and not a error message.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions