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
to help with refresh process, it is often a good idea not to prefix or suffix schema and user with environment notion.
for example, staging_pgbench is always complicated for common people to deal with the one in production prod_pgbench
staging_pgbench
prod_pgbench
if you really want to distinghish prod/preprod/stg, then you should do it at database or cluster level
raise a warning if schema starts or ends with some envt notion
The text was updated successfully, but these errors were encountered:
Done #16
Sorry, something went wrong.
No branches or pull requests
Description
Feature Definition
Is your feature request related to a problem? Please describe.
to help with refresh process, it is often a good idea not to prefix or suffix schema and user with environment notion.
for example,
staging_pgbench
is always complicated for common people to deal with the one in productionprod_pgbench
if you really want to distinghish prod/preprod/stg, then you should do it at database or cluster level
Describe the solution you'd like
raise a warning if schema starts or ends with some envt notion
The text was updated successfully, but these errors were encountered: