Eclipse Community Forums: BIRT » Null Report Parameter Passed to Data Set

Help

Home

Home » Archived » BIRT » Null Report Parameter Passed to Data Set

Show: Today's Messages :: Show Polls :: Message Navigator

Null Report Parameter Passed to Data Set [message #256497]

Fri, 28 September 2007 07:22

Eclipse User

Originally posted by: aituoklis.gmail.com

Hi,

I found example (Bugzilla ID 182197) which illustrates handling a null
report parameter before using it in a data set parameter.
As I understood this workaround is used, because data set parameter can't
be null.
But sometimes you want to write something like this:

select *
from orderdetails
where (? is NULL OR CLASSICMODELS.ORDERDETAILS.ORDERNUMBER =? )

So we having the same result as in example, but
without using Birt scripting posibilities.
And it's working! So were is the problem? Problem is that J2EE server
(in my case JBoss 4.2.0GA) throwing errors like this:

org.eclipse.birt.data.engine.odaconsumer.ParameterMetaData
getRuntimeParameterType
SEVERE: Cannot get parameter type.
org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot get parameter
type.
SQL error #1: Unsupported feature
;
java.sql.SQLException: Unsupported feature
at
org.eclipse.birt.report.data.oda.jdbc.ParameterMetaData.getP arameterT
ype(ParameterMetaData.java:159)

So report is showing correct results, but J2EE server is throwing errors,
it's not critical, but not nice.

So my question is: is it planned to support null data set parameters in
BIRT? And if yes, so in which version?

Thank you in advance for answers.

Aivaras

Report message to a moderator

Re: Null Report Parameter Passed to Data Set [message #256540 is a reply to message #256497]

Fri, 28 September 2007 14:51

Virgil Dodson

Messages: 40
Registered: July 2009

Member

Hi Aivaras,

It seems that NULL parameters might be handled differently in BIRT 2.2.1
based on this resolved bug...

https://bugs.eclipse.org/bugs/show_bug.cgi?id=203100

Virgil Dodson
http://www.birt-echange.com

Aivaras Marcinkevicius wrote:
> Hi,
>
> I found example (Bugzilla ID 182197) which illustrates handling a null
> report parameter before using it in a data set parameter. As I
> understood this workaround is used, because data set parameter can't be
> null. But sometimes you want to write something like this:
> select *
> from orderdetails
> where (? is NULL OR CLASSICMODELS.ORDERDETAILS.ORDERNUMBER =? )
>
> So we having the same result as in example, but
> without using Birt scripting posibilities. And it's working! So were is
> the problem? Problem is that J2EE server (in my case JBoss 4.2.0GA)
> throwing errors like this:
>
> org.eclipse.birt.data.engine.odaconsumer.ParameterMetaData
> getRuntimeParameterType
> SEVERE: Cannot get parameter type.
> org.eclipse.birt.report.data.oda.jdbc.JDBCException: Cannot get
> parameter type.
> SQL error #1: Unsupported feature
> ;
> java.sql.SQLException: Unsupported feature
> at
> org.eclipse.birt.report.data.oda.jdbc.ParameterMetaData.getP arameterT
> ype(ParameterMetaData.java:159)
>
>
> So report is showing correct results, but J2EE server is throwing
> errors, it's not critical, but not nice.
> So my question is: is it planned to support null data set parameters in
> BIRT? And if yes, so in which version?
> Thank you in advance for answers.
>
> Aivaras
>
>

Report message to a moderator

Previous Topic:	Query with argumentlist ; VALUE in ('A','B','C')
Next Topic:	Websphere Memory utilization is HIGH (URGENT)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Sep 18 18:07:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter