Skip to content

second table with same name is ignored without error #80

Description

@ftrotter

When the following pattern occurs:

somedatabase.dog
otherdatabase.dog

The first dog table will generate a class and the second should be ignored. Which is not actually terrible behavior... but it should raise an error when it gets to the second table with the same name... giving a warning that there are two and that this will cause confusing results...

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