-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Migration Table add "sql" VARCHAR col (traceability) #22
Comments
Another argument for this is for use cases when a manual migration must be run. Thus, again losing traceability of what has exactly run. For example, what if the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So currently the
migrations
table hasid
,name
, andrun_on
as columns. I am proposing to either add asql
column to actually save off what has run for traceability.Granted this is pumped to stdout and could just be utilized in your CI architecture.
Even if this is not accepted would it be possible to make
createMigrationsTable
's options more flexible so that custom columns could be added more easily.Seems hardcoded here
The text was updated successfully, but these errors were encountered: