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

Labels:

Comments

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 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

PL/SQL 101: Save your source code to files

PL/SQL is a database programming language. This means that your source code is compiled into  and executed from within the Oracle Database. There are many fantastic consequences of this fact, many of which are explored in Bryn Llewellyn's Why Use PL/SQL? whitepaper. But this also can mean that developers see the database as the natural repository for the original source code , and this is a bad mistake to make. It's not the sort of mistake any JavaScript or Java or php developer would ever make, because that code is not compiled into the database (well, you can  compile Java into the database, but that's not where 99.99% of all Java code lives). But it's a mistake that apparently too many Oracle Database developers make. So here's the bottom line: Store each PL/SQL program unit in its own file . Use a source code control system to manage those files. Compile them into the database as needed for development and testing. In other words: you should never kee...
16 comments
Read more