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

The schema name should be configurable #2

Open
rdlrt opened this issue Feb 27, 2025 · 1 comment
Open

The schema name should be configurable #2

rdlrt opened this issue Feb 27, 2025 · 1 comment

Comments

@rdlrt
Copy link

rdlrt commented Feb 27, 2025

Currently, following install scripts as-is ends up with hard-coded schema cardano which could be a very generic name creating conflict.
A better workflow could be users setting up schema name as an input variable during install.

@Fell-x27
Copy link
Collaborator

A better workflow could be users setting up schema name as an input variable during install.

Due to the specifics of the extension build pipeline, this will be somewhat tricky to achieve. It will require dynamically modifying SQL migrations during installation.

In the future, it might make more sense to simply replace the schema with pg_cardano to reduce the likelihood of collisions rather than making it dynamic. This is especially relevant given that the schema is explicitly mentioned in the documentation examples.

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

No branches or pull requests

2 participants