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

verify: Use managed databases #3416

Closed
kyleconroy opened this issue Jun 5, 2024 · 0 comments · Fixed by #3425
Closed

verify: Use managed databases #3416

kyleconroy opened this issue Jun 5, 2024 · 0 comments · Fixed by #3425
Labels
enhancement New feature or request
Milestone

Comments

@kyleconroy
Copy link
Collaborator

Once #3415 has landed, the verify command will change to use a managed database instead of a sqlc Cloud hosted database server. Verify will still require that you push your queries to sqlc Cloud.

Changing the default behavior

When run without any arguments, verify will ensure that the current queries work with the current database schema. Before, verify fetched the latest queries for your project, which is not always what you want to have happen.

Rename against to queries-from

While more of a mouthful, the against parameter is confusingly named. sqlc pulls queries from the given branch name to verify against the current schema. against makes is sound like the schema is being pulled instead. The --queries-from parameter makes the command read correctly in English

$ sqlc verify --queries-from main
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🛳 Shipped
Development

Successfully merging a pull request may close this issue.

1 participant