Factor out MigrationStorage #9

frioux opened this Issue Aug 18, 2012 · 0 comments


None yet
1 participant

frioux commented Aug 18, 2012

The full API of this is pending, but the gist is that the DeployMethod currently is in charge of where it gets the migrations, which is Not Great. Factoring out a MigrationStorage will allow us to easily get migrations from somewhere else, for example version control.

One of the interesting things that this can do for us is that the two different options right now for MigrationStorage can become subclasses or reimplementations of the MS instead of the DM. So for example, the first basic option is ignore_ddl, which really means any DDL that SQLT would have generated, ignore and regenerate. Well what would happen now is that ignore_ddl uses a special MS class that takes a coderef that knows how to "get" deployments from SQLT and skip the ones that would have been generated.

The next option is the ::Deprecated DM, which is more or less a straight subclass as it currently is, with the benefit that the actual DM will now stay exactly the same.

Another goal of this is that the MigrationStorage should be "queryable" in that the user can ask it what Migrations it has stored etc.

frioux was assigned Aug 18, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment