|
| Re: BIRT Parameter overhead [message #769748 is a reply to message #769183] |
Thu, 22 December 2011 16:15  |
|
Mike
You are correct. I would also make this a text box parameter. You
could always write a driver report that runs the dynamic parameter and
calls your current report with the selected parameter for preview mode.
Jason
On 12/21/2011 9:34 AM, Mike Wulkan wrote:
> I have a question regarding the processing required with regards to
> parameters in BIRT.
>
> I have several parameters that must be supplied to my report. The
> parameters are specified as combobox lists that are pre-populated by a
> DB query. The datatype is Date Time.
> The database query can return a lot of entries (eg., thousands) that all
> must be populated into this combobox control.
>
> This is fine for when I am developing the report and bringing up the
> parameters via the preview function; however in my deployed application,
> the parameters are supplied from the outside and thus none of the lists
> really need to be queried or populated since the specific value is
> already supplied in the URL.
> I have noticed that BIRT requires that the time value supplied in the
> URL must exactly match one of the entries that would have been shown in
> the combobox. This of course implies that at least the overhead of doing
> the DB query must still be taking place even if the parameters dialog is
> not shown.
>
> Is this a correct assumption? If so then would it be true that I would
> be better off just making the parameters simple textbox controls with no
> DB association. This would work fine for the deployed application (since
> it provides the complete URL) and would only make the usability of the
> preview mode less friendly.
>
> Thanks in advance for your thoughts on this
> Mike
|
|
|
Powered by
FUDForum. Page generated in 0.03390 seconds
] 
Search
Help
Register
Login
Home
