Oracle
  Home arrow Oracle arrow Associative Arrays in Oracle PL/SQL: I...
Dev Shed Forums 
Administration  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Forums Sitemap 
IBM® developerWorks 
Dedicated Servers 
E-Commerce Hosting 
Linux Web Hosting 
Managed Hosting 
Small Business Hosting 
Download TestComplete 
VPS Hosting 
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
ORACLE

Associative Arrays in Oracle PL/SQL: Introduction
By: Jagadish Chatarji
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 62
    2006-03-13

    Table of Contents:
  • Associative Arrays in Oracle PL/SQL: Introduction
  • Associative Arrays in Oracle PL/SQL: a simple example
  • Associative Arrays in Oracle PL/SQL: traversing consecutively using a FOR loop
  • Associative Arrays in Oracle PL/SQL: counting number of elements using FOR loop

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
     
    ADVERTISEMENT


    Associative Arrays in Oracle PL/SQL: Introduction
    (Page 1 of 4 )

    In this series of articles, we shall concentrate on working with associative arrays in Oracle PL/SQL. Even though I start with simple examples in the first article of this series, I shall introduce you (in my upcoming articles) to the power of much more advanced techniques using associative arrays with Oracle PL/SQL.

    Consider this an add-on to my long PL/SQL series on DevShed.  If you are new to PL/SQL, I strongly suggest you to go through my huge “Database interaction with PL/SQL” series on this website.

    All of the examples in this article have been tested only with Oracle 10g version 2.  I didn’t really test the examples in any of the previous Oracle versions.  I am confident that all of the examples should give no problems when worked with Oracle version 7.3 or above.  You can drop (or post) me a line if you run into trouble with any of them.  The examples can be directly copied, pasted and tested in your favorite PL/SQL environment.  They should work without any change.

    Associative Arrays in Oracle PL/SQL: the beginning

    The “Associative Arrays” are also known as “Index-By” tables in PL/SQL.  We all know that a variable can hold only one value (as the variable occupies one memory location based on the data type chosen).  An “Associative Array” can also be considered a single variable, but with more than one memory location. 

    An “Associative Array” can hold a huge amount of information in several memory locations, identified by some “index.”  This “index” could simply be an integer or string, or something else. 

    In general, an “Associative Array” stores pairs of data (either sequentially or non- sequentially).  Each pair of data would generally contain a “key” and a “value.”  If stored sequentially, the “key” would be nothing but a consecutive number holding the “value.”  While storing information into an “Associative Array,” the user needs to specify both “key” and “value.” 

    This concept looks very similar to the concept of arrays in C/C++.  In C/C++ an array is a continuous memory of several locations starting with zero as index.  But, here the “index” could be anything (there is no strict rule for working with the “index”).

    A typical “Associative Array” in PL/SQL could be declared like this:

    TYPE year_type IS TABLE OF number INDEX BY BINARY_INTEGER;

    The above single statement contains a lot of meaning.  First of all, we are simply defining our own data type, “year_type.” Make sure that “year_type” is not a  variable.  It is a user defined data type.  According to the above statement, “year_type” is a data type which can hold a set (or table) of values (typically of type “number”), organized with a BINARY_INTEGER index.  The BINARY_INTEGER in this scenario simply acts as a location number or position of the memory location within the table (or simply called an index).

    The next section gives you a better understanding with a simple example.

    More Oracle Articles
    More By Jagadish Chatarji


       · Hai everybody. This is going to be another series on working with "Associative...
       · On the positive side, the article is pretty clear on using sparse arrays in PL/SQL....
       · Hello, I may be wrong when I said "I am confident that it works in 7.3 as well". ...
     

       

    ORACLE ARTICLES

    - Tuning PL/SQL Code
    - Debugging PL/SQL Code
    - Testing PL/SQL Code
    - Working With PL/SQL Code
    - Conditional Compilation for Oracle Database ...
    - Compile-Time Warnings for Oracle DB 10g
    - Compiling PL/SQL Code for an Oracle Database
    - Troubleshooting PL/SQL Code
    - Managing PL/SQL Code
    - Data Manipulation and More for HTML DB Appli...
    - Oracle Database Fundamentals
    - Adding Processes to HTML DB Applications
    - Adding Computations, Processes, and Validati...
    - Sub-templates and More with Oracle HTML DB
    - Focusing on Templates in Oracle HTML DB




    © 2003-2008 by Developer Shed. All rights reserved. DS Cluster 4 hosted by Hostway