Skip to main content

PL/SQL Brain Teaser: How can BULK COLLECT be used?

No sonnets, no songs, just a simple question that has mostly obvious answers, but maybe not completely:

What are the different ways (essentially different kinds of statements) that BULK COLLECT can appear in PL/SQL code?

Comments

  1. Well, out of my head without consulting any manual (but testing in sqlplus first) here they are:

    CLEAR SCREEN
    SET SERVEROUTPUT ON
    CREATE OR REPLACE TYPE plch_integer_ntt IS TABLE OF INTEGER;
    /
    -- implicit cursor bulk collect into collection
    DECLARE
    l_coll plch_integer_ntt := plch_integer_ntt ();
    BEGIN
    SELECT LEVEL
    BULK COLLECT INTO l_coll
    FROM DUAL
    CONNECT BY LEVEL <= 10;

    FOR f_idx IN 1 .. l_coll.COUNT
    LOOP
    DBMS_OUTPUT.put_line (f_idx || '-' || l_coll (f_idx));
    END LOOP;
    END;
    /
    -- explicit cursor bulk collect into collection
    DECLARE
    l_coll plch_integer_ntt := plch_integer_ntt ();

    CURSOR ten_values_cur
    IS
    SELECT LEVEL val
    FROM DUAL
    CONNECT BY LEVEL <= 10;
    BEGIN
    OPEN ten_values_cur;

    FETCH ten_values_cur
    BULK COLLECT INTO l_coll;

    CLOSE ten_values_cur;

    FOR f_idx IN 1 .. l_coll.COUNT
    LOOP
    DBMS_OUTPUT.put_line (f_idx || '-' || l_coll (f_idx));
    END LOOP;
    END;
    /
    -- explicit cursor bulk collect into collection with limits
    DECLARE
    l_coll plch_integer_ntt := plch_integer_ntt ();

    CURSOR ten_values_cur
    IS
    SELECT LEVEL val
    FROM DUAL
    CONNECT BY LEVEL <= 1000;
    BEGIN
    OPEN ten_values_cur;

    LOOP
    FETCH ten_values_cur
    BULK COLLECT INTO l_coll
    LIMIT 100;

    EXIT WHEN l_coll.COUNT = 0;

    FOR f_idx IN 1 .. 10
    LOOP
    DBMS_OUTPUT.put_line (f_idx || '-' || l_coll (f_idx));
    END LOOP;

    exit ; -- exit now for sample purposes
    END LOOP;

    CLOSE ten_values_cur;
    END;
    /

    ReplyDelete
  2. Joao's first example could also be rewritten with:

    EXECUTE IMMEDIATE 'select level from dual connect by level<=10'
    BULK COLLECT INTO l_coll;

    ReplyDelete
  3. Excellent, Julius. That's another one!

    ReplyDelete
  4. Alos DML returning bulk collect into, like this
    DECLARE
    TYPE number$table IS TABLE OF NUMBER;
    t_ids number$table;
    BEGIN
    DELETE FROM emp WHERE salary > 100 RETURNIG id BULK COLLECT INTO t_ids;
    END;

    ReplyDelete
  5. There you go, Ilya - that was the one I thought would be hardest to recall or be aware of. When you use RETURNING for a DML statement that modifies more than one row, you will need to BULK COLLECT the values returned.

    ReplyDelete
    Replies
    1. Hi Steven.
      You wrote: "When you use RETURNING for a DML statement that modifies more than one row, you will need to BULK COLLECT the values returned".
      Another option is to use an aggregate function, like:
      UPDATE T SET... RETURNING SUM(COL1) INTO VAR1;
      Thanks,
      Oren.

      Delete
    2. Thanks for pointing that out, Oren.

      Delete
  6. Hello Steven,

    When I started to write my post, there were still no comments on this thread ...
    now, before I post it, there are already 6 of them, you can really be proud :):)

    So, I will post my comment **before** reading the other ones :)

    In a first quick attempt to cover all the cases, the list seems to be as follows:

    SELECT ... BULK COLLECT INTO ...

    FETCH ... BULK COLLECT INTO ...

    UPDATE ...
    RETURNING ... BULK COLLECT INTO ...

    DELETE ...
    RETURNING ... BULK COLLECT INTO ...

    FORALL ...
    UPDATE ...
    RETURNING ... BULK COLLECT INTO ...

    FORALL ...
    DELETE ...
    RETURNING ... BULK COLLECT INTO ...

    FORALL ...
    INSERT ... VALUES ...
    RETURNING ... BULK COLLECT INTO ...

    as well as their dynamic counter-parts, like

    EXECUTE IMMEDIATE
    'SELECT ... '
    BULK COLLECT INTO ...

    EXECUTE IMMEDIATE
    'UPDATE ... RETURNING ... INTO ...'
    RETURNING BULK COLLECT INTO ...

    EXECUTE IMMEDIATE
    'DELETE ... RETURNING ... INTO ...'
    RETURNING BULK COLLECT INTO ...

    and so on.

    I would just add that, since INSERT SELECT ... RETURNING ... is not supported,
    we should use a properly designed FORALL with a single row insert, like:

    FORALL ...
    INSERT ... VALUES ...
    RETURNING ... BULK COLLECT INTO ...

    as a work-around.

    All the FORALL cases can also use a dynamic statement, like in

    FORALL ...
    EXECUTE IMMEDIATE
    'UPDATE ... RETURNING ... INTO ...'
    USING ...
    RETURNING BULK COLLECT INTO ...


    I hope that I covered all the possible cases but, if not, I am very curious what is it that I forgot.

    Thanks a lot & Best Regards,
    Iudith

    ReplyDelete
  7. Hi Steven
    Nice explanation, but I have a question regarding 1 piece of code.
    You mentioned the following code in your 2nd program:

    -- explicit cursor bulk collect into collection
    DECLARE
    l_coll plch_integer_ntt := plch_integer_ntt ();

    but I think calling a constructor is not necessary,if you are using bulk collect.
    we can change this something like below:
    l_coll plch_integer_ntt ;--:= plch_integer_ntt ();

    Please correct me if you find me wrong. Thanks

    Regards
    Shu

    ReplyDelete
  8. You are correct, Shu. When populating a collection with BULK COLLECT it is not necessary to initialize or extend first.

    ReplyDelete
  9. Kool but any practical use of using bulk collect with returning clause?

    ReplyDelete
  10. I confess that I have not used it in any of my production code (PL/SQL Challenge), but I could see it being handy if I needed to produce a report or log in some way the rows modified and what to.

    Anyone else out there with a use case?

    ReplyDelete

Post a Comment

Popular posts from this blog

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get

My two favorite APEX 5 features: Regional Display Selector and Cards

We (the over-sized development team for the PL/SQL Challenge - myself and my son, Eli) have been busy creating a new website on top of the PLCH platform (tables and packages): The Oracle Dev Gym! In a few short months (and just a part time involvement by yours truly), we have leveraged Oracle Application Express 5 to create what I think is an elegant, easy-to-use site that our users will absolutely love.  We plan to initially make the Dev Gym available only for current users of PL/SQL Challenge, so we can get feedback from our loyal user base. We will make the necessary adjustments and then offer it for general availability later this year. Anyway, more on that as the date approaches (the date being June 27, the APEX Open Mic Night at Kscope16 , where I will present it to a packed room of APEX experts). What I want to talk about today are two features of APEX that are making me so happy these days: Regional Display Selector and Cards. Regional Display Sel