You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
toqueries-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 EnglishThe text was updated successfully, but these errors were encountered: