When running against an empty database, all migrations are displayed

[ewjoachim]

This was found by @k4nar.

It seems that when we start with a scheme corresponding to version N, the migrations before N are not run, but they're still displayed, and they should not be.

Let's fix this.