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
Summary
Postgres doesn't like dashes in identifiers. To solve this, we can double-quote identifiers. We currently do this for tables and rolenames, but we don't do it for schemas. As a result, a spec like the below will cause an error:
Postgres will complain that there is a syntax error at or near "-". To resolve this, we should double-quote all schemas as well.
Key Actions
Identify all places where schemas are used and ensure they are double-quoted. This will likely just be modifying the queries within context.py to make sure they all double-quote schemas, but there may be downstream places that do comparisons / lookups of a schema and don't double-quote it.
In addition, the submodules that use schemas (ownerships.py and privileges.py) will need to quote schemas that they are working with to make sure lookups with context.py work properly.
This is true for all other issues as well, but we definitely want a test here to verify that this behavior works as expected.
The text was updated successfully, but these errors were encountered:
Summary
Postgres doesn't like dashes in identifiers. To solve this, we can double-quote identifiers. We currently do this for tables and rolenames, but we don't do it for schemas. As a result, a spec like the below will cause an error:
Postgres will complain that there is a
syntax error at or near "-"
. To resolve this, we should double-quote all schemas as well.Key Actions
ownerships.py
andprivileges.py
) will need to quote schemas that they are working with to make sure lookups with context.py work properly.The text was updated successfully, but these errors were encountered: