You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Davies Tobi Alex (Jira)" <ji...@apache.org> on 2023/11/22 11:37:00 UTC

[jira] [Closed] (FINERACT-1708) the unique constraint name in `fineract_default` database `m_savings_account_transaction` is `transaction_ref_no` instead of `ref_no` which cause migration to fail.

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

Davies Tobi Alex closed FINERACT-1708.
--------------------------------------
    Resolution: Not A Problem

> the unique constraint name in `fineract_default` database `m_savings_account_transaction` is `transaction_ref_no` instead of `ref_no` which cause migration to fail.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-1708
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1708
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Migration Scripts
>    Affects Versions: 1.7.0
>            Reporter: Davies Tobi Alex
>            Assignee: Davies Tobi Alex
>            Priority: Minor
>
> When upgrading from version 1.6.0 to version 1.7.0 the following exception is thrown
> > can not drop unique constraint `ref_no` make sure it exists. 
> and fineract would not start.
> the unique constraint name in `fineract_default` database `m_savings_account_transaction` is `transaction_ref_no` instead of `ref_no` which cause migration to fail.
> So I applied the fix manually to the database and fineract started just fine.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)