Need to handle additional fields that fail data migration
---------------------------------------------------------
Key: MIFOS-4320
URL: http://mifosforge.jira.com/browse/MIFOS-4320
Project: mifos
Issue Type: Bug
Components: QuestionGroups/Surveys/PPI
Affects Versions: Release E
Reporter: jbrewster
Assignee: Jakub Sławiński
Priority: Major
Fix For: Release E - Iteration 13, Release E
During testing with GK data, Jakub noted that some of the additional fields
failed to migrate due problems like null values. Testing found for almost
2000000 additional fields migrated, there were 120 broken ones.
How do we handle these failures - can cleanup and manual migration occur after
upgrade? Do we create a validation script to be run prior to upgrade to
determine if problems are coming?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
new data types, scalar functions, improved concurrency, built-in packages,
OCI, SQL*Plus, data movement tools, best practices and more.
http://p.sf.net/sfu/oracle-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
