Databases
StackOverflow2013
Postsdbo
POOracle stored proc - dynamically generate select statement based on optional params
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOracle stored proc - dynamically generate select statement based on optional params
    primarykey
    data
    text
    <pre><code>create or replace PROCEDURE get_txn_by_account_id( p_ACCOUNT_ID IN txn.ACCOUNT_ID%TYPE DEFAULT NULL ) IS BEGIN FOR x IN (SELECT * FROM txn where account_id=p_ACCOUNT_ID) LOOP dbms_output.put_line(x.txn_ID || ', ' || x.txn_VER_NB); END LOOP; END get_txn_by_account_id; </code></pre> <p>my stored procedure issues a select based on one input as search criteria and outputs the search results. My input is ACCOUNT_ID. I'd like to add 4 additional input params (param_a, param_b, param_c, param_d) - at least two of which will be optional. </p> <p>So I'll probably change my stored proc declaration like</p> <pre><code>PROCEDURE get_txn_by_account_id( p_ACCOUNT_ID IN txn.ACCOUNT_ID%TYPE DEFAULT NULL, p_PARAM_A IN txn.PARAM_A%TYPE DEFAULT NULL, p_PARAM_B IN txn.PARAM_B%TYPE DEFAULT NULL, p_PARAM_C IN txn.PARAM_C%TYPE DEFAULT NULL, p_PARAM_D IN txn.PARAM_D%TYPE DEFAULT NULL ) </code></pre> <p>So my SELECT may have varying number of query params based on what optional params are passed to the stored proc.</p> <p>For instance,</p> <pre><code>FOR x IN (SELECT * FROM txn where account_id=p_ACCOUNT_ID, param_a=p_PARAM_A, param_b=p_PARAM_B, param_c=p_PARAM_C, param_d=p_PARAM_D) FOR x IN (SELECT * FROM txn where account_id=p_ACCOUNT_ID, param_a=p_PARAM_A, param_c=p_PARAM_C, param_d=p_PARAM_D) FOR x IN (SELECT * FROM txn where account_id=p_ACCOUNT_ID, param_a=p_PARAM_A, param_b=p_PARAM_B, param_d=p_PARAM_D) </code></pre> <p>or</p> <pre><code>FOR x IN (SELECT * FROM txn where account_id=p_ACCOUNT_ID, param_a=p_PARAM_A, param_b=p_PARAM_B) </code></pre> <p>etc.</p> <p>I'm having trouble with - how to code my stored proc so that the SELECT statement changes based on what optional params are passed to the stored proc - perhaps a string builder that builds a query statement based on optional params passed in to the proc, and then use the resulting string in the query? I'm not sure if this is even possible. Surely this is a common problem - anyone have any suggestions? Thanks!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFrustratedWithFormsDesigner
    1. USuser619804
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POOracle stored proc - dynamically generate select statement based on optional params
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POOracle stored proc - dynamically generate select statement based on optional params
      1. This table or related slice is empty.
      1. VTUpMod
    1. COwhy is `p_ACCOUNT_ID` optional? Or to put that another way, what do you want to return if `p_ACCOUNT_ID` isn't provided?
      singulars
      1. POOracle stored proc - dynamically generate select statement based on optional params
      1. This table or related slice is empty.
    2. COIn that case I'd return an empty set
      singulars
      1. POOracle stored proc - dynamically generate select statement based on optional params
      1. USuser619804
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload