Allow custom metadata-table names? #24
Description
Flyway can be configured to use a metadata-table with a name other than schema_version. Making the metadata table(s) (either the Flyway one or all of them) configurable would not be difficult... but is there a good use-case for this?
The myway tables are namespaced and so unlikely to collide with application tables, but Flyway's schema_version is sufficiently generic that a clash is foreseeable. Possibly it would be valid to allow customisation of the Flyway metadata table only.
Any such addition is, of course, likely to cause chaos when different migrations are inevitably accidentally performed against different metadata tables... :(
(Potentially one of the fixed myway tables could record the name of the variable Flyway table?)