[jira] [Commented] (FINERACT-1535) Migration from Mifos to Fineract

["Sifiso Mtetwa (Jira)" <ji...@apache.org>]

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

Sifiso Mtetwa commented on FINERACT-1535:
-----------------------------------------

Example bugs in 1.6.0 migration script V79__schelude_job_tables.sql

Statement

CREATE TABLE `scheduled_job_runhistory` 

Correction

CREATE TABLE `job_run_history` 

> Migration from Mifos to Fineract
> --------------------------------
>
>                 Key: FINERACT-1535
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1535
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Database, Migration Scripts
>    Affects Versions: 1.7.0
>            Reporter: Sifiso Mtetwa
>            Assignee: Aleksandar Vidakovic
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: MifostoFineract.sql
>
>
> Dear All,
>  
> Since Mifos 18.03.01 we have encountered many bugs trying to migrate to Fineract. This has prohibited some long standing Mifos users to efficiently move to Fineract without facing some challenges. Some migration scripts have been included but most schema changes have yet to be dealt with. While some fixes have been applied to isolated instances there is need to provide official support to this bug. And to cleanup the current script on the latest stable release 1.6.0. Therefore using schema diffs and manually debugging we have come up with a solution providing  the entire migration script. 
> However the tenantUpgradeService obviously includes a good chunk of the script but a lot is still missing and some of it has code errors.
> Can we include this script removing the script that is added already to the service automatically deployed on startup. Is there a quick way of identifying which script has been left out from Fineract so that some of the queries are not duplicated?  
> Any suggestions and or solutions will be very much appreciated.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)