[
https://issues.apache.org/jira/browse/FINERACT-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sifiso Mtetwa updated FINERACT-1535:
------------------------------------
Description:
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.
was:
Dear All,
Since Mifos 18.03.01 we have encountered many bugs on migrating to the Fineract
Database schema. This has prohibited some long standing Mifos users to
efficiently move to Fineract without facing some challenges. Some migration
script has 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. Therefore using schema diffs we have come
up with a solution the whole migration scripts,
While the tenantUpgradeService has included some of the migration script a lot
is still missing. So now the script attached actually migrates everything and
Fineract includes a chunk. The idea is to reproduce one script that does not
double on what has already been added to the Mifos CoreDB migration.
> 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: Migration18.03.01.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)
