You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@fineract.apache.org by "Michael Vorburger (Jira)" <ji...@apache.org> on 2020/05/16 20:44:00 UTC

[jira] [Resolved] (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

     [ https://issues.apache.org/jira/browse/FINERACT-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Vorburger resolved FINERACT-979.
----------------------------------------
    Resolution: Fixed

> 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: Blocker
>             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)