Bug while using string parameter values in postgresql query

Question

Hi,
I have the following query for the postgresql database:
Code:
<queryString><![CDATA[SELECT
evt_src_mgr_rpt_v."evt_src_mgr_name" AS esm_name,
evt_src_collector_rpt_v."evt_src_collector_name" AS collector_name,
evt_src_grp_rpt_v."evt_src_grp_name" AS grp_name,
evt_src_grp_rpt_v."state_ind" AS state_ind,
evt_src_rpt_v."evt_src_name" AS src_name,
evt_src_rpt_v."date_modified" AS date_modified,
evt_src_rpt_v."date_created" AS date_created,
CASE WHEN $P{mysortfield} = 'evt_src_mgr_name' THEN evt_src_mgr_name
WHEN $P{mysortfield} = 'evt_src_collector_name' THEN evt_src_collector_name
WHEN $P{mysortfield} = 'evt_src_grp_name' THEN evt_src_grp_name
ELSE evt_src_name END as sort
FROM
"evt_src_mgr_rpt_v" evt_src_mgr_rpt_v
LEFT JOIN
"evt_src_collector_rpt_v" evt_src_collector_rpt_v
ON EVT_SRC_MGR_RPT_V."evt_src_mgr_id" = evt_src_collector_rpt_v."evt_src_mgr_id"
LEFT JOIN
"evt_src_grp_rpt_v" evt_src_grp_rpt_v
ON evt_src_collector_rpt_v."evt_src_collector_id" = evt_src_grp_rpt_v."evt_src_collector_id"
LEFT JOIN
"evt_src_rpt_v" evt_src_rpt_v
ON evt_src_grp_rpt_v."evt_src_grp_id" = evt_src_rpt_v."evt_src_grp_id"
LEFT JOIN
"evt_src_offset_rpt_v" evt_src_offset_rpt_v
ON evt_src_rpt_v."evt_src_id" = evt_src_offset_rpt_v."evt_src_id"
WHERE
$P!{mysortfield} LIKE '$P!{searchvalue}' || '%']]></queryString>
That is I try to select only the records where the field which is
selected by user as report parameter ($P{mysortfield}) contains data
starting with the text entered by user as a report parameter
($P{searchvalue}).
When I try to run the report in iReport with active connection to the
database the report is generated as expected.
But when I try to run the report from Sentinel Log Manager I get the
following error: "java.lang.String cannot be cast to
net.sf.jasperreports.engine.JRValueParameter".
After several detailed debug sessions I finally came into a conclusion
that this error is related to the use of parameter values (
$P!{mysortfield} and $P!{searchvalue} ).
I even tried using the following WHERE clause (which emulates the
queries as used in standart reports (especially at VendorProduct related
SQL queries ) with no success:
Code:
WHERE
($P{mysortfield} = 'evt_src_mgr_name' AND evt_src_mgr_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_collector_name' AND evt_src_collector_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_grp_name' AND evt_src_grp_name LIKE ($P{searchvalue} || '%')) OR
($P{mysortfield} = 'evt_src_name' AND evt_src_name LIKE ($P{searchvalue} || '%'))
Any suggestions?
hkalyoncu
hkalyoncu's Profile: http://forums.novell.com/member.php?userid=63527
View this thread: http://forums.novell.com/showthread.php?t=450687

Answer 1

bweiner12345;2167651 Wrote:
> I'm not 100% sure the $P! (instead of just $P) is needed in that WHERE
> portion of your SQL statement.
>
> What I would suggest doing is building the WHERE portion of your query
> up again step by step. That is, instead of using any parameters in your
> WHERE:
>
> $P!{mysortfield} LIKE '$P!{searchvalue}' || '%'
>
> ... take a step back and literally hard-code some values in there, such
> as:
>
> evt_src_mgr_name LIKE '%' || '%'
>
> ... and run it on your box to make sure it works fine.
>
> If it works fine, start substituting the parameters one by one:
>
> $P{mysortfield} LIKE '%' || '%'
>
> .... test on the box.
>
> $P{mysortfield} LIKE '$P{searchvalue}' || '%'
>
> .... test on the box.
>
> It may be a little tedious, but at least you'll find out where the
> problem is occurring... and may be quicker in the long run.
>
> (Note: In my above example steps I didn't use the ! in with the
> parameters, as I don't think they are needed in the WHERE clause... but
> I could be wrong... and by following the above step-by-step technique
> should answer that for sure.)
Thank you for the suggestions:
While trying to implement your suggestions I realized that there was a
error at the parameter name I used inside the where clause (it should be
$P{searchfield}).
Here are my results:
Code:
vt_src_mgr_name LIKE '%' || '%'
worked as expected.
Code:
$P{searchfield} LIKE '%' || '%'
produced PDF but wrong output.
Code:
$P!{searchfield} LIKE '%' || '%'
resulted with the error "java.lang.String cannot be cast to
net.sf.jasperreports.engine.JRValueParameter" and no PDF.
Then I tried the following where clause which resulted in exactly as
expected PDF:
Code:
WHERE
($P{searchfield} = 'evt_src_mgr_name' AND evt_src_mgr_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_collector_name' AND evt_src_collector_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_grp_name' AND evt_src_grp_name LIKE ($P{searchvalue} || '%')) OR
($P{searchfield} = 'evt_src_name' AND evt_src_name LIKE ($P{searchvalue} || '%'))
As a summary:
* The query which works in iRepord do not work in Sentinel Log
Manager.
* I found a workaround for my case.
* I did not checked, but the reports provided in Sentinel RD which use
the same technique for VendorProduct parameter (i.e. the reports with
query string containing
Code:
LIKE ($P{VendorProduct} || '%')
will most probably not work as expected IF Sentinel RD uses the same
code as Sentinel Log Manager.
hkalyoncu
hkalyoncu's Profile: http://forums.novell.com/member.php?userid=63527
View this thread: http://forums.novell.com/showthread.php?t=450687