Home » Archived » BIRT » dataset parameter binding in RC3
| dataset parameter binding in RC3 [message #243320] |
Tue, 19 June 2007 11:18  |
Eclipse User |
|
|
|
Have found some odd behavior in the interface. It's actually kind of a
blocker.
I cannot get parameters to bind to a query in a dataset, whether a new query
in a new report, a new query in an existing report (created in 2.1 or RC0)
or in modifying an existing query. Here's what happens:
-create data set with query with hard-wired parameters. Verify that output
columns are displayed.
-create parameter bound to report parameter; replace ID value in query with
?
-output columns will disappear (it does not throw any SQL error, however).
In 2.1 I always found some odd behavior where if I modified a single
character in a query, the dataset parameters already created would
disappear. But I could always recreate them and the output columns would
return. I found that was NOT the case in RC0 and was pleasantly surprised
(parameters would be retained if you made an immaterial change to the
query).
In RC3, that behavior is back, but like the situation above, I cannot get
the output columns back. Steps for this behavior are:
-open existing query inside an existing report with a bound parameter.
-make any text change in the query (remove a return, add a space)
-output columns will disappear
To see if I was hallucinating, I launched RC0, which I still have installed,
and could bind the same queries in the same reports without any problems.
I can log this in bugzilla, but wanted to see if anyone else was seeing
this.
|
|
|
| Re: dataset parameter binding in RC3 [message #243538 is a reply to message #243320] |
Wed, 20 June 2007 10:05  |
| Eclipse User |
|
|
|
Originally posted by: Martin.Ahrer.gmx.at
Jeff,
I can confirm this, I do have the same problem. This was working in 2.1!
Jeff Reid schrieb:
> Have found some odd behavior in the interface. It's actually kind of a
> blocker.
>
> I cannot get parameters to bind to a query in a dataset, whether a new query
> in a new report, a new query in an existing report (created in 2.1 or RC0)
> or in modifying an existing query. Here's what happens:
>
> -create data set with query with hard-wired parameters. Verify that output
> columns are displayed.
> -create parameter bound to report parameter; replace ID value in query with
> ?
> -output columns will disappear (it does not throw any SQL error, however).
>
> In 2.1 I always found some odd behavior where if I modified a single
> character in a query, the dataset parameters already created would
> disappear. But I could always recreate them and the output columns would
> return. I found that was NOT the case in RC0 and was pleasantly surprised
> (parameters would be retained if you made an immaterial change to the
> query).
>
> In RC3, that behavior is back, but like the situation above, I cannot get
> the output columns back. Steps for this behavior are:
> -open existing query inside an existing report with a bound parameter.
> -make any text change in the query (remove a return, add a space)
> -output columns will disappear
>
> To see if I was hallucinating, I launched RC0, which I still have installed,
> and could bind the same queries in the same reports without any problems.
>
> I can log this in bugzilla, but wanted to see if anyone else was seeing
> this.
>
>
|
|
|
| Re: dataset parameter binding in RC3 [message #243543 is a reply to message #243320] |
Wed, 20 June 2007 10:08 |
| Eclipse User |
|
|
|
Originally posted by: no_spam.no________spam.spam
Jeff,
I have exactly the same problem. Sorry I read your news after I posted
my own ("Birt 2.2RC3 DataSet with parameter bug").
I can't check with RC0.
Perhaps Jason has an idea?
Stefan
Jeff Reid wrote:
> Have found some odd behavior in the interface. It's actually kind of a
> blocker.
>
> I cannot get parameters to bind to a query in a dataset, whether a new query
> in a new report, a new query in an existing report (created in 2.1 or RC0)
> or in modifying an existing query. Here's what happens:
>
> -create data set with query with hard-wired parameters. Verify that output
> columns are displayed.
> -create parameter bound to report parameter; replace ID value in query with
> ?
> -output columns will disappear (it does not throw any SQL error, however).
>
> In 2.1 I always found some odd behavior where if I modified a single
> character in a query, the dataset parameters already created would
> disappear. But I could always recreate them and the output columns would
> return. I found that was NOT the case in RC0 and was pleasantly surprised
> (parameters would be retained if you made an immaterial change to the
> query).
>
> In RC3, that behavior is back, but like the situation above, I cannot get
> the output columns back. Steps for this behavior are:
> -open existing query inside an existing report with a bound parameter.
> -make any text change in the query (remove a return, add a space)
> -output columns will disappear
>
> To see if I was hallucinating, I launched RC0, which I still have installed,
> and could bind the same queries in the same reports without any problems.
>
> I can log this in bugzilla, but wanted to see if anyone else was seeing
> this.
>
>
|
|
|
| Re: dataset parameter binding in RC3 [message #243629 is a reply to message #243543] |
Wed, 20 June 2007 12:58 |
| Eclipse User |
|
|
|
Originally posted by: jasonweathersby.alltel.net
Can you log a bugzilla entry for this?
I was not able to reproduce this problem. I used the 2.2 RC3 allinone
download, created a report with the query
Select * from orderdetails where order number = ?
I created a report parameter with int type and set def value to 10101.
I then binded this parameter to ds parameter and it worked. I never saw
the columns go away.
Jason
Stefan Risto wrote:
> Jeff,
>
> I have exactly the same problem. Sorry I read your news after I posted
> my own ("Birt 2.2RC3 DataSet with parameter bug").
> I can't check with RC0.
>
> Perhaps Jason has an idea?
>
> Stefan
>
> Jeff Reid wrote:
>> Have found some odd behavior in the interface. It's actually kind of a
>> blocker.
>>
>> I cannot get parameters to bind to a query in a dataset, whether a new
>> query in a new report, a new query in an existing report (created in
>> 2.1 or RC0) or in modifying an existing query. Here's what happens:
>>
>> -create data set with query with hard-wired parameters. Verify that
>> output columns are displayed.
>> -create parameter bound to report parameter; replace ID value in query
>> with ?
>> -output columns will disappear (it does not throw any SQL error,
>> however).
>>
>> In 2.1 I always found some odd behavior where if I modified a single
>> character in a query, the dataset parameters already created would
>> disappear. But I could always recreate them and the output columns
>> would return. I found that was NOT the case in RC0 and was pleasantly
>> surprised (parameters would be retained if you made an immaterial
>> change to the query).
>>
>> In RC3, that behavior is back, but like the situation above, I cannot
>> get the output columns back. Steps for this behavior are:
>> -open existing query inside an existing report with a bound parameter.
>> -make any text change in the query (remove a return, add a space)
>> -output columns will disappear
>>
>> To see if I was hallucinating, I launched RC0, which I still have
>> installed, and could bind the same queries in the same reports without
>> any problems.
>>
>> I can log this in bugzilla, but wanted to see if anyone else was
>> seeing this.
>>
|
|
|
| Re: dataset parameter binding in RC3 - releated to ORACLE jdbc drivers? [message #243789 is a reply to message #243629] |
Thu, 21 June 2007 03:15 |
| Eclipse User |
|
|
|
Originally posted by: no_spam.no________spam.spam
Jason,
I did the same steps as you did and I don't see the problem - the
parameter list is preinitialized withe the one parameter.
In my case the problem occurs when using an oracle database, perhaps it
is an issue related to oracles jdbc driver.
Using the sample datasource everything seems to be working fine.
So I will log a bugzilla entry for this.
Thanks for your help
Stefan
Jason Weathersby wrote:
> Can you log a bugzilla entry for this?
>
> I was not able to reproduce this problem. I used the 2.2 RC3 allinone
> download, created a report with the query
> Select * from orderdetails where order number = ?
>
> I created a report parameter with int type and set def value to 10101. I
> then binded this parameter to ds parameter and it worked. I never saw
> the columns go away.
>
> Jason
>
> Stefan Risto wrote:
>> Jeff,
>>
>> I have exactly the same problem. Sorry I read your news after I posted
>> my own ("Birt 2.2RC3 DataSet with parameter bug").
>> I can't check with RC0.
>>
>> Perhaps Jason has an idea?
>>
>> Stefan
>>
>> Jeff Reid wrote:
>>> Have found some odd behavior in the interface. It's actually kind of
>>> a blocker.
>>>
>>> I cannot get parameters to bind to a query in a dataset, whether a
>>> new query in a new report, a new query in an existing report (created
>>> in 2.1 or RC0) or in modifying an existing query. Here's what happens:
>>>
>>> -create data set with query with hard-wired parameters. Verify that
>>> output columns are displayed.
>>> -create parameter bound to report parameter; replace ID value in
>>> query with ?
>>> -output columns will disappear (it does not throw any SQL error,
>>> however).
>>>
>>> In 2.1 I always found some odd behavior where if I modified a single
>>> character in a query, the dataset parameters already created would
>>> disappear. But I could always recreate them and the output columns
>>> would return. I found that was NOT the case in RC0 and was pleasantly
>>> surprised (parameters would be retained if you made an immaterial
>>> change to the query).
>>>
>>> In RC3, that behavior is back, but like the situation above, I cannot
>>> get the output columns back. Steps for this behavior are:
>>> -open existing query inside an existing report with a bound parameter.
>>> -make any text change in the query (remove a return, add a space)
>>> -output columns will disappear
>>>
>>> To see if I was hallucinating, I launched RC0, which I still have
>>> installed, and could bind the same queries in the same reports
>>> without any problems.
>>>
>>> I can log this in bugzilla, but wanted to see if anyone else was
>>> seeing this.
>>>
|
|
| |
| Re: dataset parameter binding in RC3 [message #243818 is a reply to message #243320] |
Thu, 21 June 2007 05:54 |
| Eclipse User |
|
|
|
Originally posted by: Martin.Ahrer.gmx.at
I have tested this now on a HSQLDB where this bug does not accur!
Jeff Reid schrieb:
> Have found some odd behavior in the interface. It's actually kind of a
> blocker.
>
> I cannot get parameters to bind to a query in a dataset, whether a new query
> in a new report, a new query in an existing report (created in 2.1 or RC0)
> or in modifying an existing query. Here's what happens:
>
> -create data set with query with hard-wired parameters. Verify that output
> columns are displayed.
> -create parameter bound to report parameter; replace ID value in query with
> ?
> -output columns will disappear (it does not throw any SQL error, however).
>
> In 2.1 I always found some odd behavior where if I modified a single
> character in a query, the dataset parameters already created would
> disappear. But I could always recreate them and the output columns would
> return. I found that was NOT the case in RC0 and was pleasantly surprised
> (parameters would be retained if you made an immaterial change to the
> query).
>
> In RC3, that behavior is back, but like the situation above, I cannot get
> the output columns back. Steps for this behavior are:
> -open existing query inside an existing report with a bound parameter.
> -make any text change in the query (remove a return, add a space)
> -output columns will disappear
>
> To see if I was hallucinating, I launched RC0, which I still have installed,
> and could bind the same queries in the same reports without any problems.
>
> I can log this in bugzilla, but wanted to see if anyone else was seeing
> this.
>
>
|
|
| | | | | | | |
| Re: dataset parameter binding in RC3 - releated to ORACLE jdbc drivers? [message #245840 is a reply to message #245809] |
Mon, 02 July 2007 05:10 |
| Eclipse User |
|
|
|
Hi,
The fix in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=193656 is just
to ensure fetching all available output columns once the paramter has been
set correctly. On the issue that the parameter cannot automantically
generated, it is not for Birt's bug, it is just Oracle driver do not
supported this operation. We got an UnsupportedOperationException from
driver's PreparedStatement.getParameterMetaData, so it is requested user
should enter the parameter manually.
Thanks
Mingxia
"Martin Ahrer" <Martin.Ahrer@gmx.at> wrote in message
news:f6a8np$lq9$1@build.eclipse.org...
> opened a bug again https://bugs.eclipse.org/bugs/show_bug.cgi?id=195087.
>
> Martin Ahrer schrieb:
>> This morning I have retested this function for the final release 2.2
>> (which is the 0625 stable build with the same experience, however if I
>> add the parameter manually the output columns are visible!
>>
>> So there is a possible workaround - still I feel that I will report it
>> again as a bug.
>>
>>
>>
>> Stefan Risto schrieb:
>>> Martin Ahrer schrieb:
>>>> Stefan Risto schrieb:
>>>>> The bug report is entered in Bugzilla, ID: 193656
>>>>
>>>> Have you retested this recently. As the bug has been reported as fixed
>>>> on 22-6-2007, I tried it with the rcp-report-designer-2.2.0-S20070626
>>>> build and still see the same behaviour with a 10.2.0.3 Oracle driver!
>>>
>>> I used the rcp-report-designer-2.2.0-S20070625 Stable build to verify
>>> the error using an oracle driver 9.2.0.6, but I could not test it
>>> thoroughly due to some time restrictions this week.
>>>
>>> If you create a new dataset using a parameter, the editor still does not
>>> recognize the query parameters as it does when using the sample derby
>>> database. But when I entered the parameters manually I was able to get
>>> the list of columns and in contrast to RC3 and RC4 they were always
>>> visible. So for me the more important part (calculation of the output
>>> columns) seems to be working, but as I said before I did not have much
>>> time to test it.
>>>
>>> So please tell me, what are your experiences? Do you see the output
>>> columns if you enter the parameters manually?
>>>
>>> I hope there is no regression between S20070625 and S20070626.
>>>
>>> Regards,
>>> Stefan
|
|
|
Goto Forum:
Current Time: Thu May 22 03:54:27 EDT 2025
Powered by FUDForum. Page generated in 0.08521 seconds |
Home