hi UDAI,

Thanks a lot for the references supplied in the attached email.
I have been experiencing similar problems mentioned on this thread
(Branch progress report and GL report problems), particularly with the
progress report and the GL report for mifos 2.1.
I am doing a follow up on the same to know if there is any
documentations/Work-around on how to resolve the Column Binding issue
for post 1.5 reports. Also, from the thread I managed download the
Modified GL report but it still did not bring the GL computation, only
the report header and footer.

please advice.

On Sep 16 2010, 4:51 pm, Udai Gupta <[email protected]> wrote:
> Hi,
>
> I think we know one issue with BIRT reports here, i.ecolumnbinding
> (name) is case sensitive in BIRT.
>
> http://dev.eclipse.org/newslists/news.eclipse.birt/msg15093.htmlhttp://www.informit.com/articles/article.aspx?p=686166&seqNum=3
> search "BIRT ROM Data Spec" (google) seecolumnsection in that doc
>
> In MySQL thecolumnname comparison is case insensitive.
> "Column, index, stored routine, and event names are not case sensitive
> on any platform, nor arecolumnaliases. " 
> --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 thatcolumnname in the case
> specified during creation(DDL).
>
> If you give acolumnname to MySQL(by query) it will compare it in
> case insensitive way, BIRT does that comparison by asking(result 
> set)columnname from database.
>
> As per fix ofhttp://mifosforge.jira.com/browse/MIFOS-1513,  There are
> users havingcolumnnames in upper case when they upgrade to 1.6, so
> the reports are working for them.Columnnames will be all lower case
> for new users when they create mifos database so they may experience
> problem with parameters (columnbinding).
>
> This issue is just forColumnbinding(parameters) not for queries in
> the reports as the queries goes to the mysql and mysql handlescolumn
> 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 casecolumnnames in mifos database)
> 2) post 1.5 users (lower casecolumnnames in mifos database)
>
> We can not have one report which will work for both user just by
> changing the case in reports.
>
> Udai
>
> ------------------------------------------------------------------------------
> 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-users mailing list
> [email protected]https://lists.sourceforge.net/lists/listinfo/mifos-users

------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload 
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve 
application availability and disaster protection. Learn more about boosting 
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Mifos-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-users

Reply via email to