[
http://mifosforge.jira.com/browse/MIFOS-3359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58945#action_58945
]
Kojo Gambrah-Sampaney edited comment on MIFOS-3359 at 7/11/10 4:45 PM:
-----------------------------------------------------------------------
fixed in git commit bbeeccce850823a2b86ab6d33bdef916118079a7
was (Author: kgambrah):
fixed in bbeeccce850823a2b86ab6d33bdef916118079a7
> Let Developer manually manage the applied_upgrades table entries
> ----------------------------------------------------------------
>
> Key: MIFOS-3359
> URL: http://mifosforge.jira.com/browse/MIFOS-3359
> Project: mifos
> Issue Type: Dev Task
> Reporter: Kojo Gambrah-Sampaney
> Assignee: Kojo Gambrah-Sampaney
> Priority: Major
> Fix For: Release E - Iteration 2
>
>
> The current implementation of NSDU is such that the developer does not have
> to write SQL insert commands for the applied_upgrades table. DatabaseMigrator
> makes these entries automatically. The problem of arises when comparing the
> upgraded database to latest-schema and latest-data.
> Udai also pointed out that this obscures things a bit and could make
> debugging and such difficult.
--
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
