Skip to content

Schema name must start with lower case  #430

@bartkrekelberg

Description

@bartkrekelberg

Bug Report

Description

A schema name that starts with an upper case character (MySchema) will be created fine and works for the most part, but

  1. an edr cannot be generated (the regexp in edr.m searching for data tiers enforces lower case)
  2. creates confusing errors for joins, because the search for foreignkeys in dj.Table returns duplicate entries and ultimately generates spurious error messages about duplicate fields that need to be projected out. These errors disappear after clear classes, but reappear on the second run of the same query;

Reproducibility

Include:

Expected Behavior

Probably the easiest fix is to enforce a lower-case letter at the start of a schema name when the schema is first created.

Metadata

Metadata

Assignees

No one assigned

    Labels

    awaiting-triageIssues awaiting proper priority/milestone assignment.bug

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions