[
http://mifosforge.jira.com/browse/MIFOS-3598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60070#action_60070
]
Udai Gupta commented on MIFOS-3598:
-----------------------------------
I think we know one issue with BIRT reports here, i.e column binding (name) is
case sensitive in BIRT.
http://dev.eclipse.org/newslists/news.eclipse.birt/msg15093.html
http://www.informit.com/articles/article.aspx?p=686166&seqNum=3
search "BIRT ROM Data Spec" (google) see column section in that doc
In MySQL the column name comparison is case insensitive.
"Column, index, stored routine, and event names are not case sensitive on any
platform, nor are column aliases. " --
http://dev.mysql.com/doc/refman/5.1/en/identifier-case-sensitivity.html
So here we have to understand that Mysql store columns in case sensitive way. A
JDBC resultset will have that column name in the case specified during
creation(DDL).
If you give a column name to MySQL(by query) it will compare it in case
insensitive way, BIRT does that comparison by asking(result set) column name
from database.
As per fix of http://mifosforge.jira.com/browse/MIFOS-1513, There are users
having column names in upper case when they upgrade to 1.6, so the reports are
working for them. Column names will be all lower case for new users when they
create mifos database so they may experience problem with parameters (column
binding).
This issue is just for Column binding(parameters) not for queries in the
reports as the queries goes to the mysql and mysql handles column in case
insensitive way.
The workaround for this issue is that we should have two versions of BIRT
reports.
1) pre 1.5 users (upper case column names in mifos database)
2) post 1.5 users (lower case column names in mifos database)
We can not have one report which will work for both user just by changing the
case in reports.
> Parameter errors with General Ledger and Branch Progress Report
> ---------------------------------------------------------------
>
> Key: MIFOS-3598
> URL: http://mifosforge.jira.com/browse/MIFOS-3598
> Project: mifos
> Issue Type: Bug
> Components: Reports Module
> Affects Versions: Release 1.6.0
> Environment: Window 7, Apache 6.0.24, MySql 5.1.47, Mifos 1.6 x-94
> Reporter: Jessica Cheng
> Assignee: Udai Gupta
> Priority: Critical
> Fix For: Release E - Iteration 7, Release 1.6.1, Release E
>
> Attachments: Error Msg.docx, GeneralLedgerReportModified.rptdesign,
> Mifos_1282641755671.png,
> ReportEngine_2010_09_02_10_39_45.log.BranchPerf_GenLedg.zip
>
>
> Enter date under date field, got error popup box (see msg below), cannot
> generate report.
> "The parameter "branchReportDate" is required."
--
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
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
