You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
A note on how to perform the lookup from the ZomboDB maintainer:
you can do something like: SELECT * FROM pg_class WHERE oid = 'table_name'::regclass;
that'll resolve "table_name" to the first one on the search path and get you its row from pg_class
and if you know the schema, you can just WHERE oid = 'schema.table_name'::regclass;
Seems better than implementing the path resolution logic myself.
Right now unqualified table names are assumed to be in the
public
schema, but this is not quite right. There is nothing special aboutpublic
except that it is a default value in thesearch_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
The text was updated successfully, but these errors were encountered: