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
n/a
any new, altered, or removed fields in a model should be represented by an appropriate migration script
in any event, old schema+migrations should produce an identical model to that contained in the wrapper code.
go test script can apply migrations, read column headers, and compare those to the model definition via introspection on the model definition
No response
all
The text was updated successfully, but these errors were encountered:
NeilHanlon
mstg
nazunalika
No branches or pull requests
Is this feature request related to a problem? If so, please describe it.
n/a
Describe the solution you'd like to see
any new, altered, or removed fields in a model should be represented by an appropriate migration script
in any event, old schema+migrations should produce an identical model to that contained in the wrapper code.
go test script can apply migrations, read column headers, and compare those to the model definition via introspection on the model definition
Have you considered alternative solutions/features? If so, please describe them.
No response
Version and Build Information
all
Additional Context
No response
The text was updated successfully, but these errors were encountered: