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

Allow for specifying all role names #207

Open
Tracked by #211
io7m opened this issue Nov 30, 2024 · 1 comment
Open
Tracked by #211

Allow for specifying all role names #207

io7m opened this issue Nov 30, 2024 · 1 comment
Assignees
Labels
bug Something isn't working enhancement New feature or request
Milestone

Comments

@io7m
Copy link
Member

io7m commented Nov 30, 2024

Because the application picks its own cardant and cardant_read_only role names, you can't really have two cardant instances in the same database cluster, because the schema setup will try to drop and recreate the roles (which will fail, because there are database objects elsewhere that mention the role).

@io7m io7m added bug Something isn't working enhancement New feature or request labels Nov 30, 2024
@io7m io7m self-assigned this Nov 30, 2024
@io7m
Copy link
Member Author

io7m commented Nov 30, 2024

The problem is really just the dropping and re-creating. We could keep things largely the same if the code just altered the role on startup. Maybe the creation/update should be moved outside of the trasco statements.

@io7m io7m added this to the 1.0.0 milestone Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant