[jira] [Commented] (FINERACT-979) Flyway cannot apply migrations because default schema history table name in new Flyway version now is flyway_schema_history instead of schema_version

["Michael Vorburger (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FINERACT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108923#comment-17108923 ] 

Michael Vorburger commented on FINERACT-979:
--------------------------------------------

I've just run into this problem myself, while working on FINERACT-970... I would have to wipe the Demo DB on https://www.fineract.dev, which seems like a shame - if we can easily avoid it. Based on last night's posts on the mailing list, this may be relatively easy - I'll try it.

> Flyway cannot apply migrations because default schema history table name in new Flyway version now is flyway_schema_history instead of schema_version
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-979
>                 URL: https://issues.apache.org/jira/browse/FINERACT-979
>             Project: Apache Fineract
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: 1.4.0
>
>
> as outlined in issue summary, based on dev mailing list discussion on https://markmail.org/thread/qhhxtdnylwlu5xcu thread ("Re: Migration to latest"), probably (?) because of FINERACT-810.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)