Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct schema name quoting #44

Closed
wants to merge 3 commits into from

Conversation

Gastove
Copy link

@Gastove Gastove commented Jul 20, 2018

Currently, certain ALTER... SCHEMA statements will fail if they address a
schema whose name contains a hyphen, which can happen, for instance, managing
the personal schema of a user whose name contains a hyphen. This commit wraps
the schema name in quotes for the two affected sql queries, and bumps pgbedrock
to 0.3.2.

Closes #43.

Currently, certain `ALTER... SCHEMA` statements will fail if they address a
schema whose name contains a hyphen, which can happen, for instance, managing
the personal schema of a user whose name contains a hyphen. This commit wraps
the schema name in quotes for the two affected sql queries, and bumps pgbedrock
to 0.3.2.

Closes #43.
@coveralls
Copy link

coveralls commented Jul 20, 2018

Pull Request Test Coverage Report for Build 172

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 167: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

2.7.3 breaks against current versions of glibc
There exists a test for a role with a dash in it having a personal schema.
However, the test case is too simple, and does not force pgbedrock to configure
default permissions. This test case *does* force default permission
configuration, so we can see that roles with dashes and personal schemas is, in
fact, broken.
@Gastove Gastove closed this Jul 30, 2018
@Gastove
Copy link
Author

Gastove commented Jul 30, 2018

This isn't going to fix the problem, which is very deep, and gets us in to complex questions of YAML and deep restructurings. This seems unrelated to #7; in fact it is entirely about that, way down in the guts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants