Run inplace upgrades after version update

[NikVolf]

In highly unlikely scenario when the bloom update fails it will at least try again on the next run

[rphmeier]

but following migrations which expect a bloom column to be populated won't find it if in any migration situation other than 10 -> 11. What about 9 -> 11? And also, it looks like the inplace migrations don't check version. Do they each have to include a check for whether they've already been run? That information should be available from the current version.

[NikVolf]

@rphmeier
this is just workaround for one particular hypothetical problem (that is unlikely ever happen), pr does not anwer all your concerns about such in-place migrations in any way :)

[rphmeier]

I think this can be superseded by https://github.com/ethcore/parity/pull/2420 if the inplace migration is moved to the ToV10 migration there.

[NikVolf]

@rphmeier that is my plan for master, i don't want to do it in beta

[gavofyork]

@rphmeier please mark looksgood/mustntgrumble (to allow merge) or grumble (to escalate further).

[rphmeier]

I'll mark it Looksgood although I don't really agree with the strategy as a whole because

• Beta will soon become stable
• stable will probably not see any future DB upgrades backported and won't be hit by the issues I've pinpointed