[
http://mifosforge.jira.com/browse/MIFOS-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Monsen updated MIFOS-2347:
-------------------------------
Description:
When attempting to run the Branch Cash Confirmation Report, database
name/port/user/pass are hardcoded in MifosReport.rptlibrary. That means if
someone changes the name of their database or user/pass to something else, the
report will still be hitting "mifos" (or will simply fail to execute).
Other reports (likely, those not using the scripted data source) are hitting
whatever database the system is configured to hit.
This is the more robust fix: remove hardcoded settings from
MifosReport.rptlibrary and make scripted data sources use the same database
connection settings used by Mifos itself.
MIFOS-2840 is the "quick fix" that will be completed for 1.5.0.2.
See also: MIFOS-2833
was:
When attempting to run the Branch Cash Confirmation Report, it is hardcoded
(somewhere) to hit "mifos" (as in, the name of the database). That means if
someone changes the name of their mifos database to something else, the report
will still be hitting "mifos".
Other reports are hitting whatever database the system is configured to hit.
> Branch Cash Confirmation Report is hardcoded to "mifos" db
> ----------------------------------------------------------
>
> Key: MIFOS-2347
> URL: http://mifosforge.jira.com/browse/MIFOS-2347
> Project: mifos
> Issue Type: Bug
> Components: Reports Module
> Affects Versions: Release 1.2
> Environment: Platform: All, OS: All
> Reporter: Ryan Whitney
> Assignee: mifosdeveloperqueue
> Priority: Major
> Fix For: Unscheduled
>
> Attachments: issue_2347_fix.patch
>
>
> When attempting to run the Branch Cash Confirmation Report, database
> name/port/user/pass are hardcoded in MifosReport.rptlibrary. That means if
> someone changes the name of their database or user/pass to something else,
> the report will still be hitting "mifos" (or will simply fail to execute).
> Other reports (likely, those not using the scripted data source) are hitting
> whatever database the system is configured to hit.
> This is the more robust fix: remove hardcoded settings from
> MifosReport.rptlibrary and make scripted data sources use the same database
> connection settings used by Mifos itself.
> MIFOS-2840 is the "quick fix" that will be completed for 1.5.0.2.
> See also: MIFOS-2833
--
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
------------------------------------------------------------------------------
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
