[ 
http://mifosforge.jira.com/browse/MIFOS-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62835#action_62835
 ] 

Adam Monsen commented on MIFOS-4317:
------------------------------------

Kojo, I committed a fix in 
[48a61e457efde70766654389abd69693e31b740c|http://mifos.git.sourceforge.net/git/gitweb.cgi?p=mifos/head;a=commit;h=48a61e457efde70766654389abd69693e31b740c].
 Will you review my work and
* resolve this issue fixed if I did it correctly
* commit a fix if I did not ?

> Create mifos-v2.0-schema map for system info page
> -------------------------------------------------
>
>                 Key: MIFOS-4317
>                 URL: http://mifosforge.jira.com/browse/MIFOS-4317
>             Project: mifos
>          Issue Type: Improvement
>          Components: Database
>    Affects Versions: Release E
>            Reporter: jbrewster
>            Assignee: Kojo Gambrah-Sampaney
>             Fix For: Release E - Iteration 13, Release E
>
>
> Before we ship release E, we should add a friendly mapping name for the 
> Database schema so it's clear when customers are running the official 2.0 DB 
> version as described in this developer list thread:
> http://tinyurl.com/396bgbj
> "mifos releases require a particular database schema. Create a map
> (either in a flat file or in Java source code) of a set of NSDU upgrade
> IDs (UNIX timestamps) to a friendly schema version name. If the
> applied_upgrades table contains the set exactly, the UI (Admin →
> View System Information → Mifos Database Version) would display the
> friendly schema version name. For instance:
>   1280122010,1280183000,1280187884,... -> mifos-v2.0-schema "

-- 
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

Reply via email to