Skip to content

resolve unqualified names according to search_path #127

@ethanpailes

Description

@ethanpailes

Right now unqualified table names are assumed to be in the public schema, but this is not quite right. There is nothing special about public except that it is a default value in the search_path. Databases can have other search paths configured, and therefore other default schemas. To correctly determine the schema of an unqualified name, I need to query the database.

This bug seems super uncommon though, so I'm going to mark it low priority.

See: https://www.postgresql.org/docs/13/runtime-config-client.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    P-lowbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions