Using associative arrays in query

Similar Questions

• Error in the pl/sql block using associative arrays

  Hello
  I tried the following block of code using associative arrays.
  

  DECLARE
     TYPE NumTab IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
     CURSOR c1 IS SELECT empno FROM emp;
     empnos NumTab;
     rows   NATURAL := 10;
  BEGIN
     OPEN c1;
     FOR i in empnos.first..empnos.last LOOP
        /* The following statement fetches 10 rows (or less). */
        FETCH c1 BULK COLLECT INTO empnos LIMIT rows;
        EXIT WHEN c1%NOTFOUND;
        DBMS_OUTPUT.PUT_LINE ( empnos.next(i)); 
     END LOOP;
     CLOSE c1;
  END;

  and the error is

  DECLARE
  *
  ERROR at line 1:
  ORA-06502: PL/SQL: numeric or value error
  ORA-06512: at line 8

  could you please let me know where I am going wrong
  and please guide me where we use these associative arrays.
  
  Thank you

  Try this

  DECLARE
     TYPE NumTab IS TABLE OF emp%rowtype INDEX BY PLS_INTEGER;
     CURSOR c1 IS SELECT * FROM emp;
     empnos NumTab;
     rows   INTEGER := 10;
  BEGIN
    OPEN C1;
    LOOP
      FETCH c1 BULK COLLECT INTO empnos LIMIT rows;
      EXIT WHEN c1%NOTFOUND;
  
      FOR i IN 1..empnos.count
      LOOP
        DBMS_OUTPUT.PUT_LINE(empnos(i).empno || '/' || empnos(i).ename);
      END LOOP;
    END LOOP;
  END;
  

• Table of multiplication using associative arrays

  DB version: 10.2.0.1.0
  
  Here is a code for the multiplication of 14 up to 100 table. How can I store these values in an associative array and each element of the Bulletin Board so that it produces the same output as the code below.

  Declare
  --TYPE v_number_type IS TABLE OF number INDEX BY PLS_INTEGER;
  
  v_number     number:= 14;
  v_multiplied_by     number:= 1;
  v_result     number;
  begin
  
       for i in 1..100
       loop
            v_result:=     v_number * v_multiplied_by;
            dbms_output.put_line(v_number||' multiplied by '||v_multiplied_by||' = '||v_result);
            v_multiplied_by:=v_multiplied_by + 1;
       end loop;
   
   end;
   /

  Result would be

   14 multiplied by 1 = 14
   14 multiplied by 2 = 28
   14 multiplied by 3 = 42
   14 multiplied by 4 = 56
   14 multiplied by 5 = 70
   .
   .
   .
   

  Published by: user609308 on March 12, 2009 03:09
  Including the

   tags                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    

  It's a bad habit to "select into... of double" where you could just assign a value.
  It's your code, that boiled down to this:

  DECLARE
     TYPE v_number_type IS TABLE OF VARCHAR2(40)
        INDEX BY PLS_INTEGER;
  
     v_number     PLS_INTEGER   := 14;
     v_res_type   v_number_type;
  BEGIN
     FOR i IN 1 .. 100 LOOP
        v_res_type(i) := TO_CHAR(v_number) || ' multiplied by ' || TO_CHAR(i) || ' = ' || TO_CHAR(v_number * i);
     END LOOP;
  
     FOR j IN v_res_type.FIRST .. v_res_type.LAST LOOP
        DBMS_OUTPUT.put_line(v_res_type(j));
     END LOOP;
  END;
  /
  

• join an associative array with table

  I'm new to associative arrays.
  
  Here, I'm doing the equivalent of as follows:
  

   create table mytable as select n1,padding from T1 where rownum <=5;
  Table created.

  And join this table with T1 and the corresponding records to get top 10

    1   SELECT * FROM
    2   (
    3     SELECT
    4              T1.n1
    5            , T1.small_vc
    6            , mytable.padding
    7      FROM
    8             mytable
    9            , T1
   10      WHERE
   11            mytable.n1 = T1.n1
   12   )
   13* WHERE ROWNUM <= 10;

  Now with the assicative bays

    1  DECLARE
    2          type array is table of T1%rowtype index by binary_integer;
    3          l_data array;
    4          l_rec T1%rowtype;
    5  BEGIN
    6          SELECT
    7                    *
    8          BULK COLLECT INTO
    9          l_data
   10          FROM T1
   11          WHERE ROWNUM <=5;   -- the top 5 records
   12          FOR i IN 1..l_data.count
   13          LOOP
   14                BEGIN
   15  --
   16               SELECT
   17                     *
   18               INTO
   19                     l_rec
   20               FROM
   21                     T1
   22               WHERE
   23                     T1.n1 = l_data(i).n1;
   24             EXCEPTION
   25               WHEN OTHERS THEN
   26                       DBMS_OUTPUT.PUT_LINE(to_char(SQLCODE) || ' - ' || substr(SQLERRM,1,200));
   27        END;
   28     END LOOP;
   29* END;
  [email protected]> /
  -1422 - ORA-01422: exact fetch returns more than requested number of rows
  -1422 - ORA-01422: exact fetch returns more than requested number of rows
  -1422 - ORA-01422: exact fetch returns more than requested number of rows
  -1422 - ORA-01422: exact fetch returns more than requested number of rows
  -1422 - ORA-01422: exact fetch returns more than requested number of rows

  Of course the encoding isn't fair. Also, I want to display the first 10 results set.
  
  Thank you
  
  Mich

  Talebzadeh mich wrote:

  Does it fast enough and I think it is necessary for using the pipeline to multiple joins functions to update the tables of FACTS so to speak.

  A pipeline returns data that are not indexed. So by default, using data from a pipeline function involves a full production table scan. That's why native SQL tables are better than a pipeline - as these are accessible and used optimally (via the index partitions, bitmaps, clusters, etc.).

  Since PTFS uses memory structures as associative arrays do, what are the main benefits of using TFP compared to the associative arrays in addition to the fact that in MFP memory structures are presented in the SQL format?

  Not the same structure. An associative array is typically a list linked and "indexed" differently.

  A normal array is accessible by compensation. Let's say it's an array of bytes 4 IEEE floats. 1st entry is at position 0 in the structure of memory. The 2nd entry at position 4. Etc.

  Index number of the table is used to determine the offset of this table cell in the structure of memory.

  An associative array is "indexed" using strings or dates or numbers (not sequential). Thus a structure like a linked list must be used. Access to the range means a search in this linked to the match index list and then read the value of this cell in the table.

  The associative arrays do exist in the SQL engine. It is a unique data structure of PL/SQL engine.

  As to the benefits of a pipeline - this is when the data must be processed and plain vanilla SQL is not able to do this and PL/SQL is required.

  Simple example. A flat web service XML data structure. A table of pipeline can use UTL_HTTP to make the service web call, retrieve the XML code and that the output data as rows and columns - in effect turning a web service interface into something that looks like a SQL table and can be used as if it were a table SQL.

  Reading Tom on the use of pipelines comments:
  http://asktom.Oracle.com/pls/asktom/f?p=100:11:2814739467100916:P11_QUESTION_ID:19481671347143

  Also when can I use associative arrays functions insteard table in pipeline?

  Associative arrays are useful for the only PL/SQL data. For example, which deals with the pair name / value that are placed by a customer and that are used to determine which query or process data. For the majority of the PL/SQL code and the treatment, associative arrays are not necessary. And often wrongly used that developers do not seem to understand what an associative array is and how it differs from a normal table structure.

• Associative arrays... items in the index

  I can control the index of an associative array like that...
  

   TYPE aat_id IS TABLE OF PLS_INTEGER INDEX BY PLS_INTEGER;
    aa_ids aat_id;
  
  BEGIN
  
       aa_ids(1) := 3;
       aa_ids(2) := 8;
       aa_ids(2) := 10;
       
  aa_ids.delete(2);
  
  dbms_output.put_line(aa_ids.count);
  
  END;

  How can I control the index in the statement of collection in bulk as follows... so that I can delete records using this index
  

   SELECT decode(mod(rownum,2),1,1,2), object_name BULK COLLECT INTO aa_recs
       FROM   all_objects WHERE  ROWNUM <= 6;

  Thank you
  HESH.

  HESH wrote:

  but I have to play with the collected values, I want to delete the values in bulk without a loop through the list there at - it a trick possible to do this?

  Using not PL/SQL and bays of PL/SQL at all - just using simple native SQL.

  Before bulk collection and construction of an associative array, for the use of the values in table for future SQL operations, I rather to store the collection of values in a TWG (global temporary table) instead. A TWG can be indexed - and can thus provide much better access to the data as an associative array. He played better. It can be used via SQL, native mode.

  The best place for the data is in the database. Not in the PL/SQL layer. This means that in SQL tables and not in PL/SQL tables or collections.

  There are very few situations in PL/SQL, which require the use of associative arrays. If few, the majority of the PL/SQL code using associative arrays, IMO do badly. And what you've posted so far, I do not see a specific requirement for associative arrays.

  So be sure you use the correct feature - and make sure that it is also well put to use in your code.

  PS. HESH is a strange name. I'm used to HESH meaning High Explosive Squash Head (used for the filming of shielding). :-)

• CURSOR for loops or an associative array

  I just want to know the advantages and disadvantages of the CURSOR for loops. As a general rule, what guys do you prefer: associative array with CURSOR for loops?
  
  
  If you use the CURSOR for loop, is it not difficult to debug?
  
  PL/SQL Developer, I do not see what values are stored in the CURSOR for loop (in SP master_proc below) as
  There are no variables to watch. Not sure if the TOAD can show these values
  
  If I had used an associative array (master_proc2 below), I can see the values stored in the table by clicking on "show Collection"variable in PL/SQL developer.
  
  
  
  
  

  create table emp2 as select * from emp;
  
  
  create or replace procedure my_proc(p_empno in number)
  as
  begin
  update emp2 set sal=sal+100 where empno=p_empno;
  end;
  /
  
  --Using CURSOR FOR loop
  
  create or replace procedure master_proc
  as
  begin
       for rec in (select empno from emp2 where empno>7700)
       loop
            my_proc (rec.empno);
       end loop;
  end;
  /
  
  -- Using Associative arrays
  create or replace procedure master_proc2
  as
  type v_empno_type is table of number index by pls_integer;
  v_empno v_empno_type;
  
  begin
  select empno bulk collect into v_empno from emp2 where empno>7700;
  
  for i in 1..v_empno.count
   loop
      my_proc (v_empno(i));
   end loop;
  end;
  /

  VitaminD wrote:
  Thank you Tubby. If you are faced with a situation where you MUST use a loop. Then you would go to associative arrays rather than CURSOR FOR loops. Right?

  Doesn't happen too often, but if/when then I would do as I said in my first post. Use the transformation, the collection table in BULK and FORALLs.

  If we use your example posted, I would NOT spend a single table (in a loop mode) value I would be transmitted in the OVERALL picture and treat it with FORALL.

  So, I would still use neither of the approaches that you mentioned.

• An associative array, how the records using the loop counter?

  In the associative array, how the records using the loop counter? for example
  

  declare
      type population is table of number index by varchar2(64);
      city_population population;   
  begin
      city_population('Samillve') := 200;
      city_population('Lindenhurst') := 300;    
      
      for i in 1 .. city_population.count
      loop
          dbms_output.put_line(city_population(i)); -- compiler error
      end loop;
  end;
  /

  That would look like

  SQL> ed
  Wrote file afiedt.buf
  
    1  declare
    2      type population is table of number index by varchar2(64);
    3      city_population population;
    4      l_index varchar2(64);
    5  begin
    6      city_population('Samillve') := 200;
    7      city_population('Lindenhurst') := 300;
    8      l_index := city_population.first;
    9      while( l_index IS NOT NULL )
   10      loop
   11          dbms_output.put_line(city_population(l_index ));
   12          l_index := city_population.next(l_index);
   13      end loop;
   14* end;
  SQL> /
  300
  200
  
  PL/SQL procedure successfully completed.
  

  Justin

• the associative arrays containing the record type, cannot be used first

  I am having trouble with the declaration of an associative array containing the Types of records and iteration using FIRST and NEXT functions.
  This problem of mine is only appear when I use that types of records, the FIRST and FOLLOWING operators work very well when you use the regular NUMBER.
  
  Trying to get the first element of the array, I get: ORA-06550: line 22, column 40: PLS 00382: expression is of the wrong type
  
  See the code snippet below. Anyone know if this can be done in PL/SQL?
  
  -----------------------------------------------------------------------------------------
  DECLARE
  
  
  -Set the record structure that will contain information on a post
  TYPE PostRec IS (RECORD
  post_type VARCHAR2 (4) - maybe DEB/CRED
  );
  
  lr_charge_back_post PostRec;
  
  TYPE post_table IS TABLE OF PostRec NOT NULL
  INDEX BY VARCHAR2 (4);
  
  assoc_posts post_table;
  
  BEGIN
  
  
  -lr_charge_back_post.post_type: = "asd";
  assoc_posts('1').post_type: = '1';
  
  lr_charge_back_post: = assoc_posts.first;
  
  END;
  /

  Returns the index, not the file FIRST:

  SQL> declare
    2  TYPE PostRec IS RECORD (
    3  post_type VARCHAR2(4) -- Can be DEB/CRED
    4  );
    5
    6  lr_charge_back_post  varchar2(20);
    7  TYPE post_table IS TABLE OF PostRec NOT NULL
    8  INDEX BY VARCHAR2(4);
    9
   10
   11  assoc_posts post_table;
   12
   13  BEGIN
   14
   15
   16  --lr_charge_back_post.post_type := 'asd';
   17  assoc_posts('1').post_type := '1';
   18
   19  lr_charge_back_post := assoc_posts.first;
   20  dbms_output.put_line('idx='||lr_charge_back_post);
   21  END;
   22  /
  idx=1
  
  PL/SQL procedure successfully completed.
  
  SQL> declare
    2  TYPE PostRec IS RECORD (
    3  post_type VARCHAR2(4) -- Can be DEB/CRED
    4  );
    5
    6  lr_charge_back_post  varchar2(20);
    7  TYPE post_table IS TABLE OF PostRec NOT NULL
    8  INDEX BY VARCHAR2(4);
    9
   10
   11  assoc_posts post_table;
   12
   13  BEGIN
   14
   15
   16  --lr_charge_back_post.post_type := 'asd';
   17  assoc_posts('idx').post_type := '1';
   18  lr_charge_back_post := assoc_posts.first;
   19  dbms_output.put_line('idx='||lr_charge_back_post);
   20  END;
   21  /
  idx=idx
  
  PL/SQL procedure successfully completed.
  

  Max
  http://oracleitalia.WordPress.com

• Associative arrays

  Quoting docs.oracle.com lines
  
  
  Associative arrays are used to represent sets of data of arbitrary size, with quick search of an individual element without its position in the table and without
  having to loop through all the elements in the array. Here is a small example
  
  DECLARE
  TYPE population_type IS TABLE OF NUMBER INDEX OF VARCHAR2 (64);
  country_population population_type;
  continent_population population_type;
  howmany NUMBER;
  that VARCHAR2 (64);
  BEGIN
  country_population ('Greenland'): = 100000; -Creates the entry
  country_population ('Iceland'): = 750000; -Creates the entry
  -Research associated with a value chain
  howmany: = country_population ('Greenland');
  continent_population ('Australia'): = 30000000;
  continent_population ('Antarctica'): = 1000; -Creates the entry
  continent_population ('Antarctica'): = 1001; -Replaces the previous value
  -Returns "Antarctic" which comes first in alphabetical order.
  who: = continent_population. FIRST;
  -Returns "Australia", which comes last in the alphabetical order.
  who: = continent_population. LAST;
  -Returns the value corresponding to the last key, in this
  -case of the Australia population.
  howmany: = continent_population (continent_population. LAST);
  END;
  /
  
  
  
  my doubt is in what regards the statement "with a quick search of an individual element without its position in the table".can someone give a small relevant example. Therefore the associative arrays is also appropriate for relatively small lookup tables where the collection can be constructed in memory eachtime, a procedure is called? Thanks in advance...

  >
  my doubt is in what regards the statement "with a quick search of an individual element without its position in the table".can someone give a small relevant example.
  >
  Think of it as gradually close equivalent to a hash of key/value pairs. When you want to insert an item provide you the key, Oracle axe key to find the entry in the hash table. It doesn't matter if the entry is the first, last, or any other arbitrary position in the table.
  >
  Therefore the associative arrays is also appropriate for relatively small lookup tables where the collection can be constructed in memory eachtime, a procedure is called?
  >
  The scope of the variables of the procedure is only the duration of the procedure. They are built when the procedure is called and destroyed when the procedure ends.

  If any associative array created in the procedure must be small to minimize the impact on the performance of the table fill. If the procedure performs complex calculations or ETL one record at a time, it is more efficient to get a value from the array instead of having to re - query a database table for him.

  For example, for the United States, a list of 50 State and their full name abbreviations that can be stored in an associative array and procedure could extract the code of the State of a data element, and quickly find the name of the State of the table. It would be faster than executing a query on the database on a lookup table.

• How to: compare 2 associative arrays element-by-element

  After playing, I decided to go with the approach of the two sets of data of their own associative array.  The code and the results of this are below.  My question is the comparison.  For each element within the matrix of order, check all the items in the details table to see if there's a football game.  If there is a match > > > move to the next item in the control panel and check all the items in the details table to see if there is a football game.  Go until the whole is considered to be a match (in number of rows and values).  If no match, take the exit.

  Below, you'll see my logic to get both sets of data into their respective tables.  The results with a note attached to one of the elements is also pasted here (hereinafter the code).

  DECLARE

  TYPE details_t () IS RENDERING

  SIDE AUTO_RECIPE_DETAILS. SIDE % TYPE.

  REF_DES AUTO_RECIPE_DETAILS. REF_DES % TYPE,

  PART_NUM AUTO_RECIPE_DETAILS. PART_NUM % TYPE

  );

  TYPE details_type IS TABLE OF details_t INDEX OF AUTO_RECIPE_DETAILS. PART_NUM % TYPE;

  details_recipe details_type;

  pid_recipe details_type;

  compare_result details_type;

  CURSOR details_cur

  IS

  SELECT A FACE, REF_DES, PART_NUM

  OF AUTO_RECIPE_DETAILS

  WHERE RECIPE_NAME =' 40617-000001;

  CURSOR pid_cur

  IS

  SELECT cl. SIDE, lacpa. REF_DES, NVL(oecl.COMPONENT_ID, 'NOT APPLIED') AS PART_NUM

  OF ORDER_ERP_COMPS_LIST lacpa

  RIGHT OUTER JOIN CAD_LOCS cl

  ON cl. REF_DES = LACPA. REF_DES

  WHERE lacpa. ORDER_NUM = "PSY142420."

  AND CL. FAB = '38112';

  counter_d number (10): = 0;

  counter_p number (10): = 0;

  comp_counter number (10): = 0;

  BEGIN

  FOR rec IN details_cur

  LOOP

  counter_d: = counter_d + 1;

  details_recipe (counter_d). SIDE: = rec. SIDE;

  details_recipe (counter_d). REF_DES: = rec. REF_DES;

  details_recipe (counter_d). PART_NUM: = rec. PART_NUM;

  END LOOP;

  FOR rec IN pid_cur

  LOOP

  counter_p: = counter_p + 1;

  pid_recipe (counter_p). SIDE: = rec. SIDE;

  pid_recipe (counter_p). REF_DES: = rec. REF_DES;

  pid_recipe (counter_p). PART_NUM: = rec. PART_NUM;

  END LOOP;

  -for each pid_recipe element, double-check each record in details_recipe to see if there is an item matching (record)...

  FOR indx_d IN details_recipe. FIRST... details_recipe. LAST

  LOOP

  DBMS_OUTPUT. Put_line (details_recipe (indx_d). SIDE | ', ' || details_recipe (indx_d). REF_DES | ', ' || details_recipe (indx_d). PART_NUM);

  END LOOP;

  DBMS_OUTPUT. PUT_LINE ('IN THE SECOND PART OF IT!');

  FOR indx_p IN pid_recipe. FIRST... pid_recipe. LAST

  LOOP

  DBMS_OUTPUT. Put_line (pid_recipe (indx_p). SIDE | ', ' || pid_recipe (indx_p). REF_DES | ', ' || pid_recipe (indx_p). PART_NUM);

  END LOOP;

  END;

  /

  
  

  
  

  RESULT:

  
  

  DETAILS TABLE
  

  RECIPE FOR THE DETAILS TABLE:
  

  B, R28, 34315-26R7

  B, R38, 34315-4990

  B, R40, 34152-1R60

  B, R45, 34315-1002

  B, R46, 34315-3011

  B, R48, 34152-1004

  B, R55, 34315-5901

  B, R64, NOT APPLIED

  B, R77, 34315-4992

  
  

  
  

  CONTROL PANEL
  

  THE RECIPE IS CALCULATED IN THE ORDER ITSELF:
  

  B, C01, 39412-334 / / for that one single item-> check all the items from the table (above) details Table and see if an element matches.  Move to the next item if there is a match...

  B, C02, 39412-334

  B, C03, NOT APPLIED

  T, C11, 27249-105

  T, C13, 35404-104

  T, C14, 27531-224

  T, C15, 35404-104

  T, C18, 27249-105

  T, C19, 27531-224

  CHANGED:

  THIS... is the solution to my original question.  I had a little mistake that I set between this and my last post with this code.  Just in case a person who could use an example like that falls on this thread.

  FOR index_p IN pid_recipe. FIRST... pid_recipe. LAST

  LOOP

  Result WHEN the OUTPUT = 1;

  FOR index_d IN details_recipe. FIRST... details_recipe. LAST

  LOOP

  IF (pid_recipe (index_p). SIDE = details_recipe (index_d). SIDE)

  AND (pid_recipe (index_p). REF_DES = details_recipe (index_d). REF_DES)

  AND (pid_recipe (index_p). PART_NUM = details_recipe (index_d). PART_NUM)

  THEN

  EXIT;

  ON THE OTHER

  DBMS_OUTPUT. Put_line("IT WAS NOT a MATCH");

  result: = 1;

  EXIT;

  END IF;

  END LOOP;

  END LOOP;

  DBMS_OUTPUT. Put_line('LOOP OUT');

• What is the preferred means of data transmission as a type of record between the nested table of pl/sql program or an associative array

  What is the preferred means of data transmission in the associative array of the nested table record vs

  Choose between Nested Tables and associative arrays

  The two nested tables and associative arrays (formerly index - by tables) use similar index notation, but they have different characteristics when it comes to persistence and ease of passing parameters.

  Nested tables can be stored in a column of data, but can of associative arrays. Nested tables can simplify the SQL operations where you would normally join a single-column table with a larger table.

  Associative arrays are appropriate for relatively small lookup tables where the collection can be constructed in memory whenever a procedure is called or a package is initialized. They are good for the collection of the information volume is unknown beforehand, because there is no fixed limit on their size. Their index values are more flexible, as associative array indices can be negative, can be no sequential and can use values of string instead of numbers.

  PL/SQL automatically converts between the bays of the host and the associative arrays that use values of digital keys. The most effective way to move the collections to and from the database server is to implement data values in associative arrays, and then use these associative arrays with erections in bulk (the FORALL statement or BULK COLLECT clause).

  With the help of documents and Collections of PL/SQL

  Read this:

  How to pass the record set as a parameter of the procedure.

  https://community.Oracle.com/thread/2375173?TSTART=0

• Associative array

  I have a table proj_test .i want to recover the data in the associative array.

  How to do?

  create table proj_test as  
    select 1 as id, 1 as rn, 'Fred' as nm from dual union all  
    select 1,2,'Bloggs' from dual union all  
    select 2,1,'Scott' from dual union all  
    select 2,2,'Smith' from dual union all  
    select 3,1,'Jim' from dual union all  
    select 3,2,'Jones' from dual  
  
  

  You need not Associative array if you do a bulk of collect. You can use the nested PL/SQL table type.

  11g and more

  declare

  is of type tbl table of the proj_test % rowtype;

  tbl l_tbl;

  Start

  SELECT id, rn, nm bulk collect into l_tbl

  of proj_test;

  because me in 1.l_tbl.count

  loop

  dbms_output.put_line

  (

  RPAD (to_char (l_tbl (i) USER.USER), 10, ' ')

  || RPAD (to_char (l_tbl (i). (RN), 10, ' ')

  || l_tbl (i) .nm

  );

  end loop;

  end;

  Before 11 g

  declare

  type id_tbl is table of the proj_test.id%type;

  type rn_tbl is table of the proj_test.rn%type;

  type nm_tbl is table of the proj_test.nm%type;

  id_tbl l_id;

  l_rn rn_tbl;

  l_nm nm_tbl;

  Start

  SELECT id, rn, nm bulk collect into l_id, l_rn, l_nm

  of proj_test;

  because me in 1.l_id.count

  loop

  dbms_output.put_line

  (

  RPAD (to_char (l_id (i)), 10, ' ')

  || RPAD (to_char (l_rn (i)), 10, ' ')

  || l_nm (i)

  );

  end loop;

  end;

• Error renaming dates to an associative array of type date

  Hi all

  I am facing issue while assigning dates in an associative array of type date:

  Oracle version:

  SQL > select * from v version $;

  BANNER
  ----------------------------------------------------------------
  Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
  PL/SQL Release 10.2.0.1.0 - Production
  CORE 10.2.0.1.0 Production
  AMT for Linux: Version 10.2.0.1.0 - Production
  NLSRTL Version 10.2.0.1.0 - Production

  Stored procedure, I try to write is as follows

  1. create or replace procedure (jp1)
  2. p_start_date default date trunc(sysdate,'MM')
  3. p_end_date date default trunc (sysdate)
  4. )
  5. is
  6. number of l_no_of_days;
  7. type t_date_id is table of date
  8. index by pls_integer;
  9. l_date_id_arr t_date_id;
  10. Start
  11. l_no_of_days: = p_end_date - p_start_date;
  12. for i from 0
  14. .. l_no_of_days - 1
  15. loop
  16. l_date_id_arr: = p_start_date + i;
  17. dbms_output.put_line (p_start_date + i);
  18. end loop;
  19. end;
  20. /

  I get error on line 14 when compiling it. and the error message is as follows:

  JP1 PROCEDURAL errors:

  LINE/COL ERROR
  -------- -----------------------------------------------------------------
  14/5 PL/SQL: statement ignored
  14/22 PLS-00382: expression is of the wrong type

  While studying this, I tried the value of (p_start_date + i) using dbms_output.put_line and the output is so date itself.

  1. create or replace procedure (jp1)
  2. p_start_date default date trunc(sysdate,'MM')
  3. p_end_date date default trunc (sysdate)
  4. )
  5. is
  6. number of l_no_of_days;
  7. type t_date_id is table of date
  8. index by pls_integer;
  9. l_date_id_arr t_date_id;
  10. Start
  11. l_no_of_days: = p_end_date - p_start_date;

  12. for i from 0... l_no_of_days-1

  13. loop
  14. -l_date_id_arr: = p_start_date + i;
  15. dbms_output.put_line (p_start_date + i);
  16. end loop;
  17. end;
  18. /

  output of the

  1. exec jp1

  is as follows:

  1ST DECEMBER 13

  2 DECEMBER 13

  3 DECEMBER 13

  DECEMBER 4, 13

  5 DECEMBER 13

  DECEMBER 6, 13

  7 DECEMBER 13

  DECEMBER 8, 13

  9 DECEMBER 13

  DECEMBER 10, 13

  DECEMBER 11, 13

  DECEMBER 12, 13

  13 DECEMBER 13

  14 DECEMBER 13

  15 DECEMBER 13

  16 DECEMBER 13

  17 DECEMBER 13

  18 DECEMBER 13

  I see the release date itself. so why he throws error while the same assignment to an associative array of type date.

  I tried Google too for the same but without success.

  Any help is appreciated in this regard not or any pointer another thread on the internet or in this forum.

  Thanks in advance

  Jagdeep Seven

  Read associative arrays:

  1. create or replace procedure (jp1)
  2. p_start_date default date trunc(sysdate,'MM')
  3. p_end_date date default trunc (sysdate)
  4. ) is
  5. number of l_no_of_days;
  6. type t_date_id is table of date
  7. index by pls_integer;
  8. l_date_id_arr t_date_id;
  9. Start
  10. l_no_of_days: = p_end_date - p_start_date;
  11. because me in 0.l_no_of_days - 1
  12. loop
  13. l_date_id_arr (I): = p_start_date + i;
  14. dbms_output.put_line (p_start_date + i);
  15. end loop;
  16. end;

  ----

  Ramin Hashimzade

• Associative array as a type of database

  As it is very well create an associative array inside a stored procedure:

    type urltype  is table of varchar2(32767) index by varchar2(30);
  
  

  Can it be created as a type of database at the level of the schema?

  Brian.McGinity wrote:

  As it is very well create an associative array inside a stored procedure:

  1. type urltype is the table of index varchar2 (32767) by varchar2 (30);

  Can it be created as a type of database at the level of the schema?

  Non - associative arrays are a function of PL/SQL.

  See table 5-1 in the doc of the PL/SQL language for a description of each type of collection and where (pl/sql, sql, etc.) they can be used.

  http://docs.Oracle.com/CD/E11882_01/AppDev.112/e25519/composites.htm#CHDBHJEI

• Associative array of index files by varchar2 - PLS 00382

  I have a SQL anonymous block that creates a report. At the end of each section, I need to summarize the data by "renting". The list of locations is finished (approx. 15 in a table) and not all sections will have data for each location, but I want the locations to order the same so I thought I'd use an associative array to store summary data. But when I try to initialize the associative array (I simply put the slots in the array in the "correct" order) I receive PLS-00382 expression is of the wrong type.
  
  Here is the code (the lines where the error occurs are in bold):
  
  TYPE summary_data () IS RENDERING
  Summary1 NUMBER,
  NUMBER of summary2
  NUMBER of summary3
  );
  
  Summ_arr TYPE IS TABLE of summary_data INDEX OF VARCHAR2 (5);
  
  location_summary summ_arr;
  
  aLoc VARCHAR2 (5);
  
  PROCEDURE init_summ (aSummArr IN OUT summ_arr) IS
  BEGIN
  aSummArr.Delete;
  
  BEGIN
  FOR in aLoc (select name - name is VARCHAR2 (5))
  table
  control key)
  LOOP
  aSummArr (aLoc) .summary_1: = 0;
  aSummArr (aLoc) .summary_2: = 0;
  aSummArr (aLoc) .summary_3: = 0;
  END LOOP;
  EXCEPTION
  -exception handling
  END;
  
  END;
  
  If this is not allowed, or I do something wrong? I tried substituting:
  
  Summ_arr TYPE IS TABLE of summary_data INDEX OF VARCHAR2 (5);
  
  with
  
  Summ_arr TYPE IS TABLE of summary_data INDEX table.key%TYPE;
  
  Nothing helps.
  
  Thanks in advance for your help with this.
  
  ANNUAL GENERAL MEETING

  ALOC is a record variable. You need to refrence the column in the file said. So, something like this:

  aSummArr(aLoc.name).summary_1 := 0;
  

  Cheers, APC