Dynamic sql in classic report

Question

Hi everyone,
I have following question/task:
I have to generate an classic report. The problem is that the source of the report should be and dynamically generated sql query. The number and names of columns will always be the same. I already created the function which returns an varchar2 value, which in turn holds dynamically generated query. Lets say the function which generates the query is da_sql_flow_gen(v_authid number). As you can see the function takes v_authid as a parameter. v_authid it self will be a page item which will contain some random number.
I need something like this to be a source of the region
begin
return 'select da_sql_flow_gen(:P4_ID) from dual;';
end;but it does not work. Any suggestions ?
Or can I solve my task only with "pl/sql dynamic content" region ?
Thanks
Edited by: Boris Girsch on Feb 11, 2013 6:29 AM
Edited by: Boris Girsch on Feb 11, 2013 6:37 AM

Answer 1

fac586 wrote:
Boris Girsch wrote:
Hi everyone,
I have following question/task:
I have to generate an classic report. The problem is that the source of the report should be and dynamically generated sql query. The number and names of columns will always be the same. I already created the function which returns an varchar2 value, which in turn holds dynamically generated query. Lets say the function which generates the query is da_sql_flow_gen(v_authid number). As you can see the function takes v_authid as a parameter. v_authid it self will be a page item which will contain some random number.
I need something like this to be a source of the region
begin
return 'select da_sql_flow_gen(:P4_ID) from dual;';
end;but it does not work. Any suggestions ?It should be:
begin
return da_sql_flow_gen(:P4_ID);
end;
The approach you advocate forces you to use generic column names, whereas generating the same query in a functionaly identical anonymous block doesn't.
There is a workaround whereby if you wrap the call to the SQL-generating function within another SQL statement, you can use the named columns option:
   begin
      return 'SELECT * from ('||da_sql_flow_gen(:P4_ID)||')';
   end;I've not installed 4.2 yet so perhaps they've closed off this particular loophole (or indeed, fixed the "bug").