Skip to main content

The PL/SQL Collections Resource Center

Collections (Oracle PL/SQL's data structure to implement arrays, lists, stacks, queues, etc.) are not only handy in and of themselves, but are used for many key features of this powerful database programming language, including:
  • High performance querying with BULK COLLECT
  • Super-fast, bulk non-query DML operations with FORALL
  • Table functions (functions that can be treated like a table in a SELECT's FROM clause)
PL/SQL offers three types of collections - associative arrays, nested tables, and varrays - each with their own characteristics and ideal use cases.

If you are not already using collections on a regular basis in PL/SQL, you are really missing out.

Use this article as starting point for accessing a number of useful resources for getting up to speed on collections, and putting them to use in your programs.

Documentation

The PL/SQL User Guide offers detailed coverage of collection features here. It starts by reviewing the differences between collections types.


Articles

ORACLE-BASE: Collections in PL/SQL - a roundup of collection features by Tim Hall, with lots of coverage of MULTISET operators (set operations in PL/SQL, not SQL)

Multi-level collections in Oracle - great article by Adrian Billington on this advanced feature of collections (also known as nested collections)

New to 18c: Qualified expressions for associative array: it's just one new feature for collections, but it's a great one - essentially constructor functions for this type of collection. Plus I wanted to show you that even this "late in the game" as 18c, we are still enhancing collection functionality.

LiveSQL Scripts

LiveSQL offers 24x7 access to the latest version of Oracle Database. You can "play around" with SQL and PL/SQL in a scratchpad environment. It also offers a code library. There are literally dozens of scripts in that library that focus on various aspects of collections. Start here and then tune your search accordingly.

Videos


An 11-video Youtube playlist on my Practically Perfect PL/SQL channel. Just to give you a sense of the depth of coverage, total time is over 4.5 hours.


Playlist by Manish Sharma: PL/SQL Collections in Oracle Database

Manish (aka, Rebellion Rider) is one of the most prolific publishers of videos on Oracle PL/SQL. Check out this 17 video playlist for fast, basic videos on various aspects of collections.





Labels:

Comments

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
24 comments
Read more

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
14 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch,
4 comments
Read more