Add a DB migration to add params to schema.

[rposborne]

Might need to add a note to the readme.

[jgrau]

Thanks @rposborne. The migration files in the upgrade_migrations directory have been a source of confusion to me. Mainly

• how do I run a migration in a specific directory
• the files are named with the version number but are they run run automatically on updates
• are the name of the files the version you update FROM or TO

I suspect other devs might be confused about this as well.

Adding this file is a good addition and I will merge it no matter what, but if you're up for adding text to the readme regarding this file and how it works then I would much appreciate it. Let me know if you don't have the time for that and we'll just merge this as is.

[rposborne]

@jgrau There are a few hints in the changelog that point out that these were expected to be running manually... I guess specifying the explicit migration.

It looks like there are a handful of better patterns for this. Either adding the migrations to the migration load path or copying them over via a generator. As this stands now, having a record of this in the repo I think is a win, but ideally we should wire up a way to make the upgrade process more streamlined.

[jgrau]

Thanks for the contribution and the research on better ways to handle this. I've added this as a feature request #247