Params

Question

Hi all
create or replace FUNCTION getResultID(  INPUT_ID NUMBER, IN_QUERY_ID NUMBER  ) 
RETURN VARCHAR2 
AS 
RESULT_ID VARCHAR2(256); 
query_str VARCHAR2(256); 
BEGIN 
  select CONSTRUCTOR INTO query_str from query_str_ref   where QUERY_ID=IN_QUERY_ID; 
  EXECUTE IMMEDIATE query_str INTO RESULT_ID  USING INPUT_ID; 
  ETURN Result_ID; 
END getResultID;
declare
  l_getResultID varchar2(20);
  l_INPUT_ID number:=100;
  l_IN_QUERY_ID number:=200;
begin
l_getResultID:=getResultID(l_INPUT_ID,l_IN_QUERY_ID);
end;
my req is pass the in param dynamically ,instead of passing the multiple in params can i club all the params and send it as a single param is it possible, is there any alternative please do me a favour.

Answer 1

f3665bb6-1b11-4d8f-ba83-befd00bfce5e wrote:
my req is pass the in param dynamically ,instead of passing the multiple in params can i club all the params and send it as a single param is it possible, is there any alternative please do me a favour.
The alternative is to stop storing queries in tables; to stop using dynamic queries, and to start properly designing your database and orchestrating your code instead.
There's very few reasons to ever store queries in tables and use dynamic queries in this way.  It is often done by people trying to write 'generic' code to handle multiple queries and multiple results... and the very fact they're trying to make things 'generic' is becuase they think it is clever and will save them writing more code, but the truth is that it makes code that is hard to maintain, is prone to bugs and sql injection, and in most cases doesn't provide a performant system.
So... step back... re-evaluate what you are actually trying to achieve and determine if doing this 'dynamic query' route is really the best way.  99.99% of the time it isn't.