Rolling back migrations in a shared database

[hugoaboud]

I'm building a project where multiple small APIs built with AdonisJS use the same database.

I've found a scenario which raised some concerns for the long-term development:

1. API 1 runs migration '00_api1'
2. API 2 runs migration '00_api2'
3. API 1 tries to rollback migration '00_api1'
4. It fails, since AdonisJS is looking for the last migration on the table, '00_api2'

This scenario only happens on development (and rarely on staging), when sometimes there's the need for rollback to avoid creating multiple migrations before a "initial deploy".
I thought of two possible solutions:

1. The ability to cherry-pick migrations. However this might introduce a lot of mistakes.
2. Binding the migration row to the project, so a rollback looks for the last migration of the current project.

The current workaround is rolling back all the migrations down to the one on the current project, then running them all again. On a scenario with 3~5 APIs this is unpractical.
Is this a desired feature?