Tracking user info in schema_migrations

[achanda]

Is your feature request related to a problem? Please describe.
I am trying to use migrate in an internal project, one of our requirements is to be able to track which user applied a given migration and when.

Describe the solution you'd like

1. Add two new columns to schema_migrations, one to track the user and another to track timestamp. The user can be extracted from connection information.
2. Add an info subcommand that dumps information from that table.

Describe alternatives you've considered
Wrap migrate in a higher level abstraction and implement this functionality in the caller. However, I believe this feature might be beneficial for the community.

Additional context
For our use case, we need this feature only for Postgres. I am happy to go ahead and implement this if it sounds like something worth merging.

[dhui]

Interesting idea but it's not that straightforward to implement in a backwards compatible manner. e.g. how do you handle existing DB deployments?
Ideally, migrate would use itself to manage migrations for the schema_migrations table but it doesn't do that yet.

[achanda]

@dhui thanks for the reply. A stop-gap fix will be to check schema_migrations structure and add additional columns if they are not present, in each driver. That will handle backward incompatibility. The other way is to target this for a major version change release and giving up on backwards compatibility.

[dhui]

The other way is to target this for a major version change release and giving up on backwards compatibility.

This is not an option. There needs to be a path forward for existing users

A stop-gap fix will be to check schema_migrations structure and add additional columns if they are not present, in each driver. That will handle backward incompatibility.

migrate provides a framework for doing exactly this