We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is there a way to make db-sync use another schema instead of 'public'?
Say like passing a POSTGRES_SCHEMA env var with a different name?
This is really needed to properly take control over the setup and to manage better security permissions and versions.
The text was updated successfully, but these errors were encountered:
The schema looks to be hardcoded. I would support making this configurable
Sorry, something went wrong.
Thanks @sgillespie, we really need this. Also I'm about to suggest CF's Ledger Sync to take same approach earlier.
Yes it is harcoded all across the repo, on code, migration files and tests.
Example:
cardano-db-sync/cardano-db/src/Cardano/Db/Migration.hs
Line 289 in 045330d
db-sync currently uses the default schema of the db. One solution is to change it before starting db-sync
alter database <db> set search_path to <schema>;
then db-sync will use the correct one.
Btw the "public" reference in the link that you sent is only used for testing and shouldn't be a problem.
No branches or pull requests
Is there a way to make db-sync use another schema instead of 'public'?
Say like passing a POSTGRES_SCHEMA env var with a different name?
This is really needed to properly take control over the setup and to manage better security permissions and versions.
The text was updated successfully, but these errors were encountered: