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
The documentation states that
Warning: golang-migrate interprets migration filenames numerically. However, sqlc parses migration files in lexicographic order.
I was thinking if it possible to add some configuration key allowing sqlc to interpret migrations numerically instead? I don't know, something like
sqlc
schema_ordering: numeric | lexicographic
And let it be lexicographic by default. Is there any conceptual blocker for that?
lexicographic
I checked the issues and could not find anything related, sorry if it's a duplicate.
No database engines should be changed
No specific backends should be changed.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What do you want to change?
The documentation states that
I was thinking if it possible to add some configuration key allowing
sqlc
to interpret migrations numerically instead? I don't know, something likeAnd let it be
lexicographic
by default. Is there any conceptual blocker for that?I checked the issues and could not find anything related, sorry if it's a duplicate.
What database engines need to be changed?
No database engines should be changed
What programming language backends need to be changed?
No specific backends should be changed.
The text was updated successfully, but these errors were encountered: