Dynamic SQL and NULL

If testrh2 of the table has the following columns and data
col1-> NULL
col2-> 2

and table testrh has the columsn and the following data

col1-> NULL

How to write a dynamic SQL statement to join on null values? I wrote the following as a starting point block.

declare
cursor c1 is select col1 isis.testrh;
lval varchar2 (1000);
lval2 varchar2 (1000);
Start
to r1 c1 loop
lval: = 'select col2 from isis.testrh2 where col1 =' | R1.Col1;
run immediately lval in lval2;
dbms_output.put_line (lval2);
end loop;
end;

arizona9952 wrote:

How to write a dynamic SQL statement to join on null values? I wrote the following as a starting point block.

Identical to static SQL:

lval: = ' select col2 from isis.testrh2 where col1 =: 1 or (col1 is null and: 1 is nothing)';
run immediately in lval2 using r.col1 lval, r.col1;

SY.
PS I guess that's a simplified version of a logic more complex. Otherwise ther is not necessary for dynamic SQL statements.

Published by: Solomon Yakobson October 2, 2010 17:06

Tags: Database

Similar Questions

Works with dynamic sql and list of numbers as return value
Hello.

Problems:

1. How can I insert the USERNAME variable in the string so it will be replaced over time.
2. I intend to return a list of IDS as 1,4,6,7,2 I want to use later in an IN clause.

How to complete the return function with the dynamic sql output variable?
I have no preference to dynamic sql but it was just something that came into my mind
When I thought that the implementation of the obligation to choose a list of offices for specific user groups.
(select statements from the sample are cut short, they're actually really big and I want to reuse this function in my)
BI Publisher data model for multiple modells).

CREATE or REPLACE FUNCTION F_OFFICES (-input parameters)
USERNAME IN VARCHAR2
USERGROUP IN VARCHAR2,
)
-Output parameter
RETURN VARCHAR2 AS
dynSQL VARCHAR2 (1000);
BEGIN

IF USERGROUP = "local" THEN

dynSQL: = 'xxx SELECT FROM CO_B WHERE Userid = username';

ELSIF USERGROUP = "regional" THEN

dynSQL: = "SELECT...". » ;

ELSIF USERGROUP 'federal' = THEN
dynSQL: = "SELECT...". » ;

END IF;

EXECUTE IMMEDIATE dynSQL;

-RETURN?;

END F_OFFICES;

Thanks for any help.
As you have presented essentially pseudo-code we can only give you a Pseudo-solution :)

But the principle is:
```
...
--Output parameter
RETURN VARCHAR2 AS
    dynSQL VARCHAR2(1000);
    return_value varchar2(30):
BEGIN

  IF USERGROUP = 'local' THEN
    dynSQL:= 'SELECT xxx FROM CO_B WHERE userid = :1'; -- placeholder for parameter

   ...
  END IF;

  EXECUTE IMMEDIATE dynSQL
     using USERNAME -- pass parameters in placeholder order
     into return_value;   -- obviously this must match the projection of the dynamic query 

  RETURN return_value; 

END F_OFFICES ;
```
This approach is not good if you want to vary the dynamic query projection. In this case, you can use a REF CURSOR or maybe DBMS_SQL.

Cheers, APC

Using of the dynamic SQL and the cursor in a procedure

Here is the procedure:

create or replace
Procedure type_paiement_total
is

    cursor xbtable is select table_name from user_tables where table_name like 'XB%';
    n_table user_tables.table_name%type;
    req     varchar2(256);
    journal varchar2(2);
    mois varchar2(2);
    an varchar2(2);
  begin
    for n_table in xbtable
    loop
      execute immediate 'insert into xx_jk_xb (
      clie_code,journal, periode,origine, xb_ecri,xb_libe  ,dos_code,xb_debi,xb_cred,xb_term
)
select c.code,  
substr(:1,3,2),
substr(:1,7,2)||substr(:1,5,2)||,
:1,  
xb.ecri,  
xb.libe,  
d.code,
xb.debi,
xb.cred,
xb.terme
from                      
'||n_table.table_name ||' xb,
dossier d,                      
client c                    
where xb.cmpt=''4111''                    
and xb.doss  =d.code                    
and c.code   =d.clie
and c.role=''1''' using n_table.table_name;
      execute immediate 'insert into xx_jk_logxb (recnum,xb_ref,trsf) values (seq_logmreg.nextval,:1,''OK'')' using n_table.table_name;
      commit;
      fetch xbtable into n_table;
    end loop;
  end;

What he does (or what I intend to do)
take the datas of a whole bunch of pictures and put them in the "XX_JK_XB" table and make a log of the tables covered in xx_jk_logxb give just the source table and the status (OK).
Now when I run the procedure I get a "missing expression" th ' immediate «insert into xx_jk...»» »

I just can't tell what is the problem here.

clues?

Seems to me that you are wrong assuming that the binding can be done by name and no position when you use immediate enforcement.

Example:

SQL> create table foo_tab( c1 varchar2(10), n1 number );

Table created.

SQL>
SQL> begin
  2          for i in 1..10
  3          loop
  4                  execute immediate 'insert into foo_tab values( to_char(:1), :1 )' using i;
  5          end loop;
  6          commit;
  7  end;
  8  /
begin
*
ERROR at line 1:
ORA-01008: not all variables bound
ORA-06512: at line 4

SQL>
SQL>
SQL> begin
  2          for i in 1..10
  3          loop
  4                  execute immediate 'insert into foo_tab values( to_char(:1), :1 )' using i,i;
  5          end loop;
  6          commit;
  7  end;
  8  /

PL/SQL procedure successfully completed.

SQL>

As you can see, 1 PL/SQL block attempts to re - use bind variable: 1 new - and only link once.

Fact does not work like that - you must link it again. Binding is done by bind - 1 position = 1 to the help of var, 2nd = 2nd bind using var, etc.. Name of the connection variable used is irrelevant and not unique.

Is it possible to keep all static? (vs dynamic SQL)?
Hi all

I have existing MS who after db Exchange should work with newly partitioned table partition name = date of entry both inside AND date_param, something like:

sql_string: =' select * tt partition (P_'| date_param |') the problem of configuration required, I can't use any dynamic SQL and it really put me in the corner, do you think it is at all possible? I was thinking about a lot of things that may work, but date_param is just date < 12 - 7.-10. > and partition is preceded with PRT_?

I can to with str_part: = ('(P_'|| date_param ||'') ') "), but it is already dynamic...

Even after I create the temporary table and for sure, I know that the DDL inside the procedure should be ONLY dynamic?
What is the dead end? There is a way to CREATE static? or simply to use kind of temp table created outside MS and clean it before use? or...

I actually try to see why customer site cannot manage NDS or they just don't want it, but can't argue with that for now.
I've got enough new to Oracle and couldn't do bad things on the SQL dynamic (NDS)?

Thank you all
TR
Trento wrote:
Hi all

I have existing MS who after db Exchange should work with newly partitioned table partition name = date of entry both inside AND date_param, something like:

sql_string: =' select * tt partition (P_'| date_param |') the problem of configuration required, I can't use any dynamic SQL and it really put me in the corner, do you think it is at all possible? I was thinking about a lot of things that may work, but date_param is just <12-Sep-10>and partition is preceded with PRT_?

I can to with tmp_part: = ('(PRT_'|| date_param ||'') ') "), but it is already dynamic...

Even after I create the temporary table and for sure, I know that the DDL inside the procedure should be ONLY dynamic?
What is the dead end? There is a way to CREATE static?

I actually try to see why customer site cannot manage NDS or they do not want, cannot buy with that for now. I'm pretty new to Oracle and could not do bad things on dynamic SQL?

Thank you all
TR

Why the hell wouldn't you just query the table and apply the predicate? Oracle would then partition elimination for you.

No need for anything either dynamics based on what you posted.

Dynamic SQL in APEX
Hey everyone, I'm trying to understand how to use dynamic sql statements in Application Express. Specifically, I'm trying to write a query using substitution/bind variables. I don't know if you need a description of the application or not, but here's the query that will run in sqlplus:
```
ACCEPT     file_id     PROMPT     "Enter the file_id (a number, e.g. 3): "
 
-- Preliminary Query, to set table_name
 
COLUMN     reference_id_col     NEW_VALUE     reference_id
COLUMN     table_name_col     NEW_VALUE     table_name
 
SELECT  f.reference_id          AS reference_id_col
,           t.reference_table       AS table_name_col
FROM      aa_files     f
JOIN     aa_type     t     ON     f.file_type     = t.type_id
WHERE     f.file_id     = &file_id
;
 
--     Main Query
 
SELECT  * 
FROM     &table_name
WHERE      reference_id     = &reference_id
;
```
There are three substitution variables, reference_id & file_id and & table_name. My basic setup is that I have a table full of table names, so I ask her to get a table name in a variable, then query this table for my data.

I work inside the window of SQL commands to try to find the proper syntax to make this work in the APEX. I'm pretty sure that APEX does not allow the use of substitution variables, because they are one thing on the side of client SQL more right?

I'm still a student, so I'm not known and Oracle Application Express, but reading the documentation of the APEX and the Googling, I tell myself that bind variable should be able to do this for me, but I don't know how. I searched for some examples or documentation on the use of dynamic SQL statements in the APEX, but I could not find anything. I'm sure I could do this using a PL/SQL block, but I'd rather do it in pure SQL if possible.

So if someone could help me or giving me an example of syntax I would have to use to write a query that is running in Application Express, or could direct me to the literature on the use of dynamic sql statements in Application Express, it would be greatly appreciated!

If you need more information on my application, I can post my create table statements and some inserts sample data, if that would be helpful.

Thank you!

Published by: username, June 21, 2010 07:34
OK, so one of the great things about SQL is your ability to choose what columns you want to include in your result set. You don't have to use all of them. You can do this in two ways: with dynamic SQL or individual areas for each type of file. This will depend on your use as to how many types different files will be added each day on which you want to go with.

If you go with dynamic SQL (and because you don't know until run time what columns you want to use, it is an appropriate use), you will need to build your query based on the file type. Something like this:
```
declare
  qry_type  VARCHAR2(10);
  sql_qry    VARCHAR2(4000);
  qry_select  VARCHAR2(500);
  qry_from   VARCHAR2(100);
  qry_where  VARCHAR2(400);
  qry_order   VARCHAR2(100);
begin
  qry_type  :=  :PX_QRY_TYPE;
  --Build the SELECT clause
  qry_select   := 'select a.FILE_NAME, a.FILE_NAME, a.FILE_TYPE, a.LOCATION';
  CASE qry_type
     WHEN 'PDF' THEN qry_select   := qry_select || ', pdf.DATE_MODIFIED, pdf.SUMMARY, pdf.AUTHOR';
     WHEN 'XLS' THEN qry_select   := qry_select || ', xls.DATE_MODIFIED, xls.SUMMARY, xls.TOTAL_VALUE';
     ...
  END CASE;
  --Build the FROM clause
  qry_from    := ' from AA_FILE a, AA_FILETYPE_PDF pdf, AA_FILETYPE_XLS xls, AA_FILETYPE_PHOTO p';
  --Build the WHERE clause
  qry_where  := ' where a.FILE_ID = pdf.FILE_ID (+)';
  qry_where  := qry_where || ' and a.FILE_ID = xls.FILE_ID (+)';
  qry_where  := qry_where || ' and a.FILE_ID = p.FILE_ID (+)';
  --Build the ORDER BY clause
  qry_order  := '';
  --Put it all together
  sql_qry   := qry_select || qry_from || qry_where || qry_order;
  EXECUTE IMMEDIATE sql_qry;
  ...
end;
```
Now this does not cover the addition of new file types. I still think you're going to be better off planning for as much as you can and handle manually creating additional tables, but this is going to be to you. I know you are trying to generate code to do everything for you, but when it comes to databases, I found that the creation of objects can quickly become uncontrolled if you're not very careful. These are going to be permanent, not temporary memory built database objects. Just a word of warning.

If you decide to go with a region and by file type, it does not require nearly as much work. Simply create a report region based on the view and set the conditional display based on your file type.
```
  select * from V_FILES_PHOTO
   where FILE_ID = :PX_FILE_ID;

condition:  FILE_TYPE = 'PDF'
```
While you will need to add a region again every time that you add a new file type, once again, the question that arises is: file types how are you really going to have to worry? If you're talking about a dozen, I would like to do things manually. If you're talking about a hundred, it's maybe worth trying to find a method of programming. It is your call to make.

Dynamic SQL is a valid option?
Hello

I have question on insertion I have a large amount of lines that I want to insert into a table. Insert rows are like;

001 09 00 FF
001 09 FF 11
FF 00 11 001
001 00 01 00

There are four types of conditions. Only the last condition can be inserted, while the rest cannot be inserted (in other words, on four columns to all who have the value 'FF' must not be inserted).

I wanted to use a simple constraint checking, but our DBA is not agree on this. The reason is that overall with many conditions will create a problem with the database-level locking.

Now, I think to use dynamic SQL and the place of the condition in the WHERE clause. I think right and make any sense?

I think I have to be aware of performance because there will be a mass insertion.

Published by: uk113 on July 28, 2009 06:03
In fact, I agree with kind of your DBA, but not his reasons. A check against the content of a column constraint will not cause a locking more in the database column without constraint. If you update a row in the table, Oracle will have a lock on the rows updated if they are limited or not. A newly inserted row never "locked" because it is no longer visible in the session that he introduced to the validation of this session.

You say "I have a lot of lines that I want to insert into a table" which implies to me that you have the source data in an accessible form electronically, which means you can do single insertion as a SQL statement. As many others have suggested, I would use a predicate on each of the columns that cannot contain FF to remove these rows from the result set that you will use to make the insertion.

Given the constraints on the table for a loading block, particulalry if you know you will have a fairly large number of rows in your data source, which will infringe the constraint actually will force you in a row by row (or bulk collect bulk collect) scenario so that you can catch constraint violations and throw these lines. Although you can still use a predicate to filter the lines that would not allow the validation.

If you need constraints after loading mass will depend on whether or not you expect to get new data in the table, and how it will be inserted or updated. If new data come mainly from single row inserts and updates (for example from the application screen), then I would certainly limit the columns to allow not FF. If you do only loads in bulk, I would add probably not these constraints. If you are likely to have a mix of bulk and individual tips, I add the constraints, but still have a predicate in loads in bulk to filter incorrect records.

John

Tables created in a stored procedure cannot be used with dynamic SQL? The impact?
There is a thread on the forum which explains how to create tables within a stored procedure (How to create a table in a stored procedure , however, it does create a table as such, but not how to use it (insert, select, update, etc.) the table in the stored procedure.) Looking around and in the light of the tests, it seems that you need to use dynamic SQL statements to execute ddl in a stored procedure in Oracle DB. In addition, it also seems that you cannot use dynamic SQL statements for reuse (insert, select, update, etc.) the table that was created in the stored procedure? Is this really the case?

If this is the case, I am afraid that if tables cannot be 'created and used"in a stored procedure using the dynamic SQL, as is the case with most of the servers of DB dynamic SQL is not a part of the implementation plan and, therefore, is quite expensive (slow). This is the case with Oracle, and if yes what is the performance impact? (Apparently, with Informix, yield loss is about 3 - 4 times, MS SQL - 4 - 5 times and so on).

In summary, tables created within a stored procedure cannot be 'used' with dynamic SQL, and if so, what is the impact of performance as such?

Thank you and best regards,
Amedeo.

Published by: AGF on March 17, 2009 10:51
AGF says:
Hi, Frank.

Thank you for your response. I understand that the dynamic SQL is required in this context.

Unfortunately, I am yet to discover "that seeks to" using temporary tables inside stored procedures. I'm helping a migration from MySQL to Oracle DB, and this was one of the dilemmas encountered. I'll post what is the attempt, when more.

In Oracle, we use [global temporary Tables | http://www.psoug.org/reference/OLD/gtt.html?PHPSESSID=67b3adaeaf970906c5e037b23ed380c2] aka TWG these tables need only be created once everything like a normal table, but they act differently when they are used. The data inserted in TWG will be visible at the session that inserted data, allowing you to use the table for their own temporary needs while not collide with them of all sessions. The data of the TWG will be automatically deleted (if not deleted programmatically) when a) a commit is issued or b) the session ends according to the parameter that is used during the creation of the TWG. There is no real need in Oracle to create tables dynamically in code.

I noticed that many people say that the "Creation of the tables within a stored procedure" is not a good idea, but nobody seems necessarily explain why? Think you could elaborate a little bit? Would be appreciated.

The main reason is that when you come to compile PL/SQL code on the database, all explicit references to tables in the code must correspond to an existing table, otherwise a djab error will occur. This is necessary so that Oracle can validate the columns that are referenced, the data types of those columns etc.. These compilation controls are an important element to ensure that the compiled code is as error free as possible (there is no accounting for the logic of programmers though ;)).

If you start to create tables dynamically in your PL/SQL code, so any time you want to reference this table you must ensure that you write your SQL queries dynamically too. Once you start doing this, then Oracle will not be able to validate your SQL syntax, check the types of data or SQL logic. This makes your code more difficult to write and harder to debug, because inevitably it contains errors. It also means that for example if you want to write a simple query to get that one out in a variable value (which would take a single line of SQL with static tables), you end up writing a dynamic slider all for her. Very heavy and very messy. You also get the situation in which, if you create tables dynamically in the code, you are also likely to drop tables dynamically in code. If it is a fixed table name, then in an environment multi-user, you get in a mess well when different user sessions are trying to determine if the table exists already or is the last one to use so they can drop etc. What headache! If you create tables with table names, then variable Dynamics not only make you a lot end up creating (and falling) of objects on the database, which can cause an overload on the update of the data dictionary, but how can ensure you that you clean the tables, if your code has an exception any. Indeed, you'll find yourself with redundant tables lying around on your database, may contain sensitive data that should be removed.

With the TWG, you have none of these issues.

Also, what is the impact on the performance of the dynamic SQL statements in Oracle? I read some contrasting opinions, some indicating that it is not a lot of difference between static SQL and SQL dynamic in more recent versions of Oracle DB (Re: why dynamic sql is slower than static sql is this true?)

When the query runs on the database, there will be no difference in performance because it is just a request for enforcement in the SQL engine. Performance problems may occur if your dynamic query is not binding variable in the query correctly (because this would cause difficult analysis of the query rather than sweet), and also the extra time, to dynamically write the query running.

Another risk of dynamic query is SQL injection which may result in a security risk on the database.

Good programming will have little need for the tables of dynamically created dynamically or SQL.

Examination of dynamic cursor and SQL performance
Hello world

I'm a researcher on internet forums and oracle for what is best for my case.

I tried to rebuild indexes. I had two methods, both works very well, but I'm looking for which is preferable from the point of view of performance

1 - the use of cursor as in the link below.

http://www.think-forward.com/SQL/rebuildunusable.htm

2 - using dynamic SQL, that generated the script file, then run it.

coil rebuildall.sql
Select "change the index ' |" owner: '. ' || index_name |' rebuild online; '
from dba_indexes where status = "UNUSABLE."
spool off;

@rebuildall.sql

Thanks in advance. Your help is appreciated.
In both cases, that you use dynamic SQL statements, I think that there is no difference in terms of performance, use the method you feel most comfortable

In all cases, you can follow the timestamps (time is set on & set timing on) and connect the outputs

Best regards
Alfonso Vicente
www.logos.com.uy

Difference between the static SQL query and dynamic SQL query.
Hello

Please explain the fundamental difference between static and dynamic sql queries. Please explain for example.
Static: http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10472/static.htm
Dynamics: http://download.oracle.com/docs/cd/E11882_01/appdev.112/e10472/dynamic.htm

Of FUNDING and dynamic SQL CREATE ANY TABLE
Hi gurus,

I have a dynamic SQL code in a procedure where a table to an existing table without data will be created.

strSQL: = "create table ' | strTemp | ' in select * from '. strArc. "where 1 = 2"; "
Execute immediate strSQL;

without GRANT CREATE ANY TABLE to user, * "ORA-01031: insufficient privileges" * error executing. "."

Is there a way to tackle this problem without providing a GRANT CREATE ANY TABLE privileged?

Thank you very much
Charles
(1) why you are creating a table to run? Which seems to me very concerning. If you create a temporary table and you're accustomed to work how temporary tables in other databases, I would strongly suggest you look at how Oracle manages global temporary tables. If temporary storage is really necessary (99% of the time is not because of the consistent reading multi-version), you should be able to create global temporary tables a few during execution.

(2) the owner of the procedure should just need the CREATE TABLE privilege granted directly to the user (not granted through a role), assuming that it is in stored procedure a standard DEFINER rights.

Justin

Retrieve and display a result set using the dynamic sql?
Hi all

How would display a result set in Oracle using the dynamic SQL? Reason being, the table where I'd retrieve and display the result set is a GLOBAL TEMP TABLE created in a stored procedure. If I try to use the loop as usual, the compiler complains that the table does not exist. This makes sense because the compiler does not recognize the table because it is created dynamically. Here is an example:

create or replace PROCEDURE maketemptab IS
sql_stmt VARCHAR2 (500);
OutputString VARCHAR2 (50);

BEGIN
-create temporary table
sql_stmt: = ' CREATE of TABLE TEMPORARY GLOBAL globtemptab (id NUMBER, col1 VARCHAR2 (50))';
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... created table ');

-Insert a row into the temporary table
sql_stmt: = "INSERT INTO globtemptab values (1, 'some data of a test')';"
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... inserted row ');

-Insert a row into the temporary table
sql_stmt: = ' INSERT INTO globtemptab values (2, "some more test data");
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... inserted row ');

-Select the row on temporary table
sql_stmt: = 'SELECT col1 FROM globtemptab WHERE id = 1';
EXECUTE IMMEDIATE sql_stmt INTO outputstring;
dbms_output.put_line ('... selected line: ' | outputstring);

-drop temporary table
sql_stmt: = 'DROP TABLE globtemptab;
EXECUTE IMMEDIATE sql_stmt;
dbms_output.put_line ('... moved table ');

-display the result set
for tabdata loop (select col1 from globtemptab)
dbms_output.put_line ('... test of recovered data are' | tabdata.col1)
end loop;
end;

In short, how to rewrite the SQL below the comment "to display the result set" using the dynamic sql?

Thank you
Amedeo.
Hello

Try this:
```
CREATE OR REPLACE PROCEDURE maketemptab IS
   sql_stmt     VARCHAR2(500);
   outputstring VARCHAR2(50);
   v_cursor     SYS_REFCURSOR;
   v_col1       VARCHAR2(30);
BEGIN
   -- create temp table
   sql_stmt := 'CREATE GLOBAL TEMPORARY TABLE globtemptab(id NUMBER, col1 VARCHAR2(50))';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...table created');

   -- insert row into temp table
   sql_stmt := 'INSERT INTO globtemptab values (1, ''some test data'')';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...row inserted');

   -- insert row into temp table
   sql_stmt := 'INSERT INTO globtemptab values (2, ''some more test data'')';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...row inserted');

   -- select row from temp table
   sql_stmt := 'SELECT col1 FROM globtemptab WHERE id=1';
   EXECUTE IMMEDIATE sql_stmt
      INTO outputstring;
   dbms_output.put_line('...row selected: ' || outputstring);

   OPEN v_cursor FOR 'SELECT col1 FROM globtemptab';

   LOOP
      FETCH v_cursor
         INTO v_col1;
      EXIT WHEN v_cursor%NOTFOUND;
      dbms_output.put_line('...test data retrieved is' || v_col1);
   END LOOP;
   CLOSE v_cursor;

   -- drop temp table
   sql_stmt := 'DROP TABLE globtemptab';
   EXECUTE IMMEDIATE sql_stmt;
   dbms_output.put_line('...table dropped');
END;
/
```
Kind regards

How to get sql % number of dynamic sql code lines

Hello

In this procedure I'm inserting and updating using dynamic sql. Now I want to go back two more PARAMETERS, the parameter should be back the number of lines inserted and how updated by stmtas of UPDATE as well as an INSERT. I'm not able to do can help you on that?

CREATE OR REPLACE PROCEDURE Sp_Array_Test( PV_TGT_NAME   IN  VARCHAR2,
                                           PV_SRC_NAME   IN  VARCHAR2,
                                           PV_PK_COLS    IN  VARCHAR2,
                                           PN_ERR_CD     OUT NUMBER,
                                           PN_ERR_MSG    OUT VARCHAR2)
AS


TYPE ARR_TAB IS TABLE OF VARCHAR2(4000) INDEX BY BINARY_INTEGER;


--UTL_FP        UTL_FILE.FILE_TYPE;
LV_AN_



BLOCK   VARCHAR2(32767);
LN_CUR        BINARY_INTEGER := DBMS_SQL.OPEN_CURSOR;
LN_DESC       DBMS_SQL.DESC_TAB;
LN_COL_CNT    PLS_INTEGER := 0;
LV_SEL_UPD_STMT   VARCHAR2(4000);
LV_SEL_INS_STMT   VARCHAR2(4000);
ARR_INDX      NUMBER := 1;
LV_DATA_TYPE  VARCHAR2(8);
LN_FIND_FLAG  NUMBER := 0;
LN_TAB        ARR_TAB;
LV_COLS_ARR   ARR_TAB;
LV_ERR_MSG    VARCHAR2(500);




--PROCEDURE FILE_WRITE ( FH_IN     IN UTL_FILE.FILE_TYPE,
--                STRING_IN IN VARCHAR2 ) IS
--BEGIN
--   UTL_FILE.PUT_LINE(FH_IN,STRING_IN);
--   LV_AN_BLOCK := LV_AN_BLOCK||STRING_IN;
--EXCEPTION
--   WHEN OTHERS THEN
--      RAISE;
--END FILE_WRITE;




BEGIN


--   UTL_FP := UTL_FILE.FOPEN('TEST_DIR', 'TEST.sql', 'W');


    LV_SEL_UPD_STMT := 'SELECT A.'||REPLACE(PV_PK_COLS,',','||A.')||' PK_COLS , A.* , B.ROWID FROM '||PV_SRC_NAME||' A, '||PV_TGT_NAME||' B WHERE ';


    LV_SEL_INS_STMT := 'SELECT A.* FROM '||PV_SRC_NAME||' A WHERE NOT EXISTS (SELECT ''1'' FROM '||PV_TGT_NAME||' B WHERE ';


    LN_TAB(ARR_INDX) := 'DECLARE ';
    ARR_INDX := ARR_INDX + 1;


    LN_TAB(ARR_INDX) := 'CURSOR CUR_VIEW_UPD IS '||LV_SEL_UPD_STMT ;
    ARR_INDX := ARR_INDX + 1;




    SELECT SUBSTR(COLS,DECODE(RN,1,1,INSTR(COLS,',',1,RN-1)+1),DECODE(RN,1,INSTR(COLS,',',1,RN)-1,INSTR(COLS,',',1,RN)-INSTR(COLS,',',1,RN-1)-1))
BULK COLLECT INTO LV_COLS_ARR
      FROM ( SELECT RN, PV_PK_COLS||',' COLS
               FROM (SELECT ROWNUM RN
                       FROM ALL_OBJECTS
                      WHERE ROWNUM <= LENGTH(PV_PK_COLS)- LENGTH(REPLACE(PV_PK_COLS,','))+1)) ;
    FOR K IN 1 .. LV_COLS_ARR.COUNT LOOP
        LV_SEL_UPD_STMT     := LV_SEL_UPD_STMT||' A.'||LV_COLS_ARR(K)||' = ';
        LN_TAB(ARR_INDX) := ' A.'||LV_COLS_ARR(K)||' = ';
        LV_SEL_UPD_STMT     := LV_SEL_UPD_STMT||' B.'||LV_COLS_ARR(K) ||CASE WHEN K = LV_COLS_ARR.COUNT THEN NULL ELSE ' AND ' END;
        LN_TAB(ARR_INDX) := LN_TAB(ARR_INDX)||' B.'||LV_COLS_ARR(K) ||CASE WHEN K = LV_COLS_ARR.COUNT THEN ' ;' ELSE ' AND ' END;
        ARR_INDX := ARR_INDX + 1;
    END LOOP;


    LN_TAB(ARR_INDX) := 'CURSOR CUR_VIEW_INS IS '||LV_SEL_INS_STMT ;
    ARR_INDX := ARR_INDX + 1;


    FOR K IN 1 .. LV_COLS_ARR.COUNT LOOP
        LV_SEL_INS_STMT     := LV_SEL_INS_STMT||' A.'||LV_COLS_ARR(K)||' = ';
        LN_TAB(ARR_INDX) := ' A.'||LV_COLS_ARR(K)||' = ';
        LV_SEL_INS_STMT     := LV_SEL_INS_STMT||' B.'||LV_COLS_ARR(K) ||CASE WHEN K = LV_COLS_ARR.COUNT THEN NULL ELSE ' AND ' END;
        LN_TAB(ARR_INDX) := LN_TAB(ARR_INDX)||' B.'||LV_COLS_ARR(K) ||CASE WHEN K = LV_COLS_ARR.COUNT THEN ' );' ELSE ' AND ' END;
        ARR_INDX := ARR_INDX + 1;
    END LOOP;




    LV_ERR_MSG := 'WHILE PARSING SELECT STATEMENT -- '||LV_SEL_UPD_STMT;
    DBMS_SQL.PARSE(LN_CUR, LV_SEL_UPD_STMT, DBMS_SQL.NATIVE);


    LV_ERR_MSG := 'WHILE DESCRIBING SELECT STATEMENT -- '||LV_SEL_UPD_STMT;
    DBMS_SQL.DESCRIBE_COLUMNS(LN_CUR, LN_COL_CNT, LN_DESC);






   FOR i IN LN_DESC.FIRST .. LN_DESC.LAST LOOP
      IF LN_DESC(i).col_type = 2 THEN
         LV_DATA_TYPE := 'NUMBER';
      ELSIF LN_DESC(i).col_type = 12 THEN
         LV_DATA_TYPE := 'DATE';
      ELSE
         LV_DATA_TYPE := 'VARCHAR2';
      END IF;
       LN_TAB(ARR_INDX) := '   T_'||LN_DESC(i).col_name||' DBMS_SQL.'||LV_DATA_TYPE||'_TABLE;';
       ARR_INDX := ARR_INDX + 1;
   END LOOP;






    LN_TAB(ARR_INDX) := 'BEGIN ';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '   EXECUTE IMMEDIATE ''ALTER SESSION SET NLS_DATE_FORMAT = ''''DD-MON-YYYY HH24:MI:SS'''''';';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '   OPEN CUR_VIEW_UPD;';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '   LOOP';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '      FETCH CUR_VIEW_UPD BULK COLLECT INTO T_'||LN_DESC(LN_DESC.FIRST).col_name||',';
    ARR_INDX := ARR_INDX + 1;
    FOR i IN LN_DESC.FIRST + 1 .. LN_DESC.LAST - 1 LOOP
      LN_TAB(ARR_INDX) := '                        T_'||LN_DESC(i).col_name||',';
      ARR_INDX := ARR_INDX + 1;
    END LOOP;
   LN_TAB(ARR_INDX) := '                        T_'||LN_DESC(LN_DESC.LAST).col_name||' LIMIT 500 ;';
   ARR_INDX := ARR_INDX + 1;
   LN_TAB(ARR_INDX) := '     FORALL I IN 1 .. '||'T_'||LN_DESC(LN_DESC.LAST).col_name||'.COUNT ';
   ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '      UPDATE '||PV_TGT_NAME||' SET  ';
    ARR_INDX := ARR_INDX + 1;
    LN_FIND_FLAG := 0;
    FOR I IN LN_DESC.FIRST + 1 .. LN_DESC.LAST-1 LOOP
      FOR K IN 1 .. LV_COLS_ARR.COUNT LOOP
         LN_FIND_FLAG := 0;
         IF LN_DESC(I).COL_NAME = LV_COLS_ARR(K) THEN
            LN_FIND_FLAG := 1;
            EXIT;
         END IF;
      END LOOP;
      IF LN_FIND_FLAG = 0 THEN
        LN_TAB(ARR_INDX) := '                        '||LN_DESC(i).col_name||' = '||'T_'||LN_DESC(i).col_name||'(I)'||CASE WHEN I = LN_DESC.LAST-1 THEN ' WHERE ' ELSE ',' END;
        ARR_INDX := ARR_INDX + 1;
      END IF ;
    END LOOP;


   LN_TAB(ARR_INDX) := '                        ROWID = '||'T_'||LN_DESC(LN_DESC.LAST).col_name||'(I) ;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '      COMMIT;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '      EXIT WHEN CUR_VIEW_UPD%NOTFOUND;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '   END LOOP;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '   CLOSE CUR_VIEW_UPD;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '      COMMIT;';
   ARR_INDX := ARR_INDX + 1;




    LN_TAB(ARR_INDX) := '   OPEN CUR_VIEW_INS;';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '   LOOP';
    ARR_INDX := ARR_INDX + 1;
    LN_TAB(ARR_INDX) := '      FETCH CUR_VIEW_INS BULK COLLECT INTO T_'||LN_DESC(LN_DESC.FIRST+1).col_name||',';
    ARR_INDX := ARR_INDX + 1;
    FOR i IN LN_DESC.FIRST + 2 .. LN_DESC.LAST - 2 LOOP
      LN_TAB(ARR_INDX) := '                        T_'||LN_DESC(i).col_name||',';
      ARR_INDX := ARR_INDX + 1;
    END LOOP;
   LN_TAB(ARR_INDX) := '                        T_'||LN_DESC(LN_DESC.LAST-1).col_name||' LIMIT 500 ;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '     FORALL J IN 1 .. '||'T_'||LN_DESC(LN_DESC.FIRST + 1).col_name||'.COUNT ';
   ARR_INDX := ARR_INDX + 1;
   LN_TAB(ARR_INDX) := '     INSERT INTO '||PV_TGT_NAME||' (';
   ARR_INDX := ARR_INDX + 1;
    FOR i IN LN_DESC.FIRST + 1 .. LN_DESC.LAST - 1 LOOP
      LN_TAB(ARR_INDX) := '                        '||LN_DESC(i).col_name||CASE WHEN I = LN_DESC.LAST - 1  THEN ' )' ELSE ',' END ;
      ARR_INDX := ARR_INDX + 1;
    END LOOP;
    FOR i IN LN_DESC.FIRST + 1 .. LN_DESC.LAST - 1 LOOP
      LN_TAB(ARR_INDX) := CASE WHEN I = LN_DESC.FIRST + 1 THEN 'VALUES (' ELSE NULL END ||'                        T_'||LN_DESC(i).col_name||'(J)'||CASE WHEN I = LN_DESC.LAST - 1  THEN ' ) ;' ELSE ',' END ;
      ARR_INDX := ARR_INDX + 1;
    END LOOP;


   LN_TAB(ARR_INDX) := '      COMMIT;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '      EXIT WHEN CUR_VIEW_INS%NOTFOUND;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '   END LOOP;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '   CLOSE CUR_VIEW_INS;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := '      COMMIT;';
   ARR_INDX := ARR_INDX + 1;


   LN_TAB(ARR_INDX) := 'END ;';
   ARR_INDX := ARR_INDX + 1;




   FOR J IN 1 .. LN_TAB.COUNT LOOP
--     DBMS_OUTPUT.PUT_LINE( LN_TAB(J));
--     FILE_WRITE(UTL_FP,LN_TAB(J));
     LV_AN_BLOCK := LV_AN_BLOCK||LN_TAB(J);
   END LOOP;


--   UTL_FILE.FCLOSE(UTL_FP);


   EXECUTE IMMEDIATE LV_AN_BLOCK;


PN_ERR_CD    := 0;
PN_ERR_MSG   := 'Successful Completion';


EXCEPTION
WHEN OTHERS THEN
PN_ERR_CD    := SQLCODE;
PN_ERR_MSG   := LV_ERR_MSG||' -- '||SQLERRM ;
END;
/

Thank you all for your answers. I agree with you all. I have manged this time by adding variable bind, then run it immediately ON aid. I don't know how it's going to be training.

From now on my side no problem I don't thank you.

How to write the SQL without using dynamic SQL?

How can you write this under SQL without using execute immediately?
You can use static SQL (using something like a CASE statement)?
test procedure (one in varchar2, b number, each number) is
v_num_recs pls_integer;
Start
Select count (*)
in v_num
FROM table1
where
col1 = one and
If b is not null then col2 = b
If c is not null then col3 = c;
/ * i.e. If b is not null, where condition to add this line only. If c is not null, where condition should add only this line. OR condition No. it * /.
dbms_output.put_line (v_num);
end;
Or should I use dynamic SQL statements for this?

I was wondering if the two are NOT NULL? Well check this.

Select count (*) in v_num

table

where col1 = one

and col2 = (CASE WHEN (b is not null) THEN b ELSE END col2)

and col3 = (CASE WHEN (c is not null) THEN ELSE END col3 c)

Dynamic SQL with dynamic identifiers
Oracle 10gXE

I have a table that is used to track student attendance. If the student is present on a given day, a record is inserted with the student ID and the date they frequented.

presence of DESC
Name of Type Null
--------------- -------- ------
ID NOT NULL NUMBER
NUMBER OF STUDENT_ID
SITE_ID NUMBER
DATE OF ATTENDANCE_DATE

I want to view a report (in TOP) which shows all students for a given site, the days when school was in session for this month (not Saturday, Sunday) and a X for the student who participated in that day or a null value if they do not have.

ID # FNAME LNAME 3 4 5 6 7 10
38754636 POE JANE X X X
81248754 DOE KAYLA X X X X X
43127409 RAO JOHN X X X X X

In this example, days 3 and 7 of the month are from Monday to Friday and 8-9 have been excluded because they are on Saturday and Sunday.

I am trying to find a way to dynamically generate a query for any month/year and returning to a report. The obstacle is that given that I don't know in advance which days in a month will be excluded, the identifiers in my select statement are not fixed.

I found a query that returns a list of day numbers and dates for a given month. It looks like this:

SELECT LEVEL lv, TO_DATE (TO_CHAR (LEVEL, '09')
|| TO_CHAR (EXTRACT (TO_DATE('01-SEP-11') MONTHS), '09')
|| To_char (EXTRACT (TO_DATE('01-SEP-11') YEAR), ' 9999'), 'dd.mm.yyyy') mon_day
OF double WHERE ROWNUM < = EXTRACT (DAY OF LAST_DAY (TO_DATE('01-SEP-11')))
CONNECT BY LEVEL = ROWNUM

I combined this request with another brings my student attendance data and results that pivots in what I need. Then, I created a function that accepts the month and year as parameters and creates the combined request.

SELECT c.ID student_id, c.last_name, c.first_name,.
MAX (decode (mon_day, ' 01 - SEPT.-11', 'X', NULL)) '1', MAX (decode (mon_day, ' 02 - SEVEN.-11', 'X', NULL)) '2 ',.
MAX (decode (mon_day, ' 05 - SEPT.-11', 'X', NULL)) '5', MAX (decode (mon_day, ' 06 - SEPT.-11', 'X', NULL)) "6."
MAX (decode (mon_day, ' 07-SEP-11', 'X', NULL)) '7', MAX (decode (mon_day, ' 08 - SEPT.-11', 'X', NULL)) "8."
MAX (decode (mon_day, ' 09 - SEPT.-11', 'X', NULL)) '9', MAX (decode (mon_day, 12-SEP-11', 'X', NULL)) "12."
MAX (decode (mon_day, 13-SEP-11', 'X', NULL)) '13', MAX (decode (mon_day, 14-SEPT-11', 'X', NULL)) "14."
MAX (decode (mon_day, 15-SEP-11', 'X', NULL)) '15', MAX (decode (mon_day, 16-SEP-11', 'X', NULL)) "16."
MAX (decode (mon_day, 19-SEP-11', 'X', NULL)) '19', MAX (decode (mon_day, 20-7.-11', 'X', NULL)) "20."
MAX (decode (mon_day, 21-SEP-11', 'X', NULL)) "21", MAX (decode (mon_day, 22-SEP-11', 'X', NULL)) '22 ',.
MAX (decode (mon_day, 23-SEP-11', 'X', NULL)) '23', MAX (decode (mon_day, 26-SEP-11', 'X', NULL)) "26."
MAX (decode (mon_day, 27-SEP-11', 'X', NULL)) '27', MAX (decode (mon_day, 28-SEP-11', 'X', NULL)) "28."
MAX (decode (mon_day, 29-SEP-11', 'X', NULL)) '29', MAX (decode (mon_day, 30-SEP-11', 'X', NULL)) '30 '.
(SELECT level lv, TO_DATE (TO_CHAR (LEVEL, '09')
|| TO_CHAR (EXTRACT (TO_DATE('01-SEP-11') MONTHS), '09')
|| To_char (EXTRACT (TO_DATE('01-SEP-11') YEAR), ' 9999'), 'dd.mm.yyyy') mon_day
OF double WHERE ROWNUM < = EXTRACT (DAY OF LAST_DAY (TO_DATE('01-SEP-11')))
CONNECTION LEVEL = ROWNUM) a, b of attendance, student c
WHERE to_char(MON_DAY,'D') NOT IN (1.7)
AND A.mon_day = b.attendance_date
AND b.student_id = c.ID
Group of c.ID, student_id, c.last_name, c.first_name

Now I'm stuck on what I can pass this request in to get my result. What I've read, dynamic SQL method 4 would work if I incorporate Pro/C. I hope this isn't my only option. I have considered to try to do this in a function table in pipeline, but since the columns returned are not known in advance, I can't create a corresponding data type.

I'm starting to wonder if I forgot a simpler method to achieve this.

Published by: David Sumner on April 12, 2012 18:52
Ignoring the actual query and looking at the dynamic SQL part of the question.

There are 3 ways to run a dynamic select SQL in PL/SQL code.

immediate execution requires a fixed number of bind variables, linking him in position and translates a single implicit output cursor extraction - requiring the projection of cursor to be known at the time of coding.

REF CURSOR are essentially the same - the only exception being that it requires an extraction explicit coding process output cursor.

DBMS_SQL differs in all of these respects. The connection is by name and not position. The connection is dynamic. Projection of the cursor must not be known at the time of coding. It is dynamically determined at runtime and fetch offers of release of the cursor with the projection of unknown SQL - coding time.

Apex uses DBMS_SQL internally (in fact he uses DBMS_SYS_SQL properly run dynamic and specific patterns of Oracle SQL, as if a session connected as a scheme runs the SQL code). This allows the Apex to take a dynamic SQL that you enter a region (which can contain a variable number of bind variable), run it and make the projection of the cursor as an HTML report.

Apex supports in turn also dynamic SQL - what you (Apex developer) to provide a dynamic SQL code for a region, instead of you having to provide SQL fixed (with bind variable) for the region in question.

As Apex creates DBMS_SQL sliders, it doesn't have your SQL as a ref cursor or cursor DBMS_SQL. All they need is the source of the SQL statement. And that's what you create dynamically.

So in the Apex, dynamic SQL means using a function from PL/SQL to return the source for Apex SQL analyze like a slider DBMS_SQL - instead of coding the source SQL statement in a fixed statement.

So, using the option of function for an area considered in the Apex, allows you to provide the following in the code that must run to get the SQL statement for the report Apex (Apex running this as a dynamic function that returns a string):
```
--// return the dynamic SQL for the report region
return(
  case
    when :P1_OPTION = 1 then
      'select * from emp'

    when :P1_OPTION = 2 then
      'select * from dept where dept_id = :P1_DEPT_ID'
  end
);
```
You can also write a PL/SQL function that is stored in the database and call this function so that it can determine what is the dynamic SQL source code statement. For example
```
--// calling database function to return the dynamic SQL for the report region
return(
  GetDynamicReportSQL( page => 1, option => :P1_OPTION )
);
```
Dynamic SQL is fully supported by Apex - but does not require that you, the developer, to create the dynamic cursor and treat the dynamic linking and dynamic recovery of this slider.

All you have to do is to provide the source code of this dynamic SQL (including the bind variable) to the Apex and it will do the whole thing from cursor for you.

Using CASE in a dynamic sql query
Hello
I want to create a dynamic query using the CASE statement to replace the below 2 SQL statements:

+++++
Select "create or replace the synonym ' |" SYNONYM_NAME | 'for'. TABLE_OWNER |'. ' || TABLE_NAME | » @'|| SUBSTR (Db_link, 1, 30) |';' OF USER_SYNONYMS where db_link is not null;
Select "create or replace the synonym ' |" SYNONYM_NAME | 'for'. TABLE_OWNER |'. ' || TABLE_NAME |';' OF USER_SYNONYMS where the db_link is null;
+++++

While I have a unique select query which will give her create synonym statements for all with or without links db

Using the example of CASE statement as below:
SELECT
FirstName, LastName,
Salary, date of birth,
ABOUT sex
WHEN'm ' THEN 'male '.
WHEN 'F' THEN 'woman '.
END
Employees

I don't get how to write this CASE statement. Can someone guide me here?

Thank you
Malika
"" The thread has been moved to Forum Home "database" SQL and PL/SQL+.

Nicolas.

Dynamic SQL and NULL

Similar Questions

Maybe you are looking for