Skip to content

Parsing problem with table CASE #92

@gerritgriebel

Description

@gerritgriebel

It's not wise to call a table "CASE", but it's unfortunately the case with our schema. Extension stops parsing the rest of the package for that reason, as you can see by the drop down:

Bildschirmfoto 2022-02-19 um 11 50 21

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions