[
http://mifosforge.jira.com/browse/MIFOS-1876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Van Mittal-Henkle updated MIFOS-1876:
-------------------------------------
Priority: Minor (was: Major)
> Named constraints in MIFOS db scripts
> -------------------------------------
>
> Key: MIFOS-1876
> URL: http://mifosforge.jira.com/browse/MIFOS-1876
> Project: mifos
> Issue Type: Improvement
> Components: Misc
> Affects Versions: Release 1.1
> Environment: Platform: All, OS: Windows XP
> Reporter: anagri
> Assignee: mifosdeveloperqueue
> Fix For: Unscheduled
>
>
> I came across this issue when I tried to drop some of the columns in MIFOS.
> There were Foreign Key anonymous/unnamed constraints that failed sql for
> dropping those columns. So for dropping these columns first I have to drop
> these
> FK constraints, since they were not named but the constraint name were
> generated
> when creating tables, I had to rely on the auto generated naming sequence.
> This can be an issue when in some cases were the auto generated constraint
> names
> are different for different deployments.
> By naming the constraint following some convention, this issue can be avoided
> in
> the future.
--
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
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
