Abstract:
A system and method for updating collection-valued and other complex structured columns in a nested table using a nested extension of an UPDATE statement that is analogous to the syntax and semantics of the UPDATE statement that is used to modify scalar-valued columns of the table (called the outer UPDATE). Using the same syntactic and semantic constructs as the table at the outer level allows an existing implementation that processes modifications to relational tables to reuse its implementation techniques for processing outer updates to modify collection-valued columns as well. The UPDATE extensions enable the specification of updates to nested collections embedded at arbitrary levels of depth in the object model. The new syntax is embedded inside the outer UPDATE statement in a way that parallels the structure of the data itself and thus maps more directly to the user&#39;s conceptual model of the data.

Description:
FIELD OF THE INVENTION 
   The present invention relates to database systems and, more particularly, to a system and method for using nested relational SQL language extensions to modify tables with a hierarchical structure (such as nested tables and tables that store complex-structured objects or XML) in arbitrary ways in one step and for providing the mechanisms (such as change descriptor and leveraging of query optimization and query execution techniques) to achieve complex and partial updates efficiently. 
   BACKGROUND OF THE INVENTION 
   The SQL query language provides a user with the ability to query (and modify) tabular data stored using the relational data model. The relational data model dictates that each cell in a table (a column of a row) is a single scalar (or atomic) value. The structured query language (SQL) is an American National Standards Institute (ANSI) standard used to communicate with a relational database. SQL statements are used to perform tasks such as update data or retrieve data from a relational database. Although many database systems use SQL, many of them also have their own additional proprietary extensions that are usually only used on their system. However, the standard SQL commands such as “Select”, “Insert”, “Update”, “Delete”, “Create”, and “Drop” can be used to accomplish many things that one desires to do with a relational database and are believed to be well known to those skilled in the database art. 
   Recent extensions to the relational data model relax the restriction of storing a single scalar value in a cell and allow each cell in a table to be a collection of values itself. Each element inside this collection can in turn contain a collection itself, i.e. the collection can be nested to arbitrary levels of depth. Tables with such collection-valued cells with multiple values can be broadly called nested tables. This development presents the problem of how to extend the SQL language to modify the collection values in such a nested table. For example, a technique for modifying the collection-valued cells to permit the simultaneous change of scalar values at any nesting level is desired. 
   Current implementations of nested tables and associated standards offer extensions for querying and updating collections in a nested table. In a conventional nested table system, however, the nested scalar values are updated one level at a time for each level of scalar values in a collection-valued cell, thus requiring multiple updates to change the stored values in a multi-level cell. For example, U.S. Pat. No. 6,564,203 describes techniques for updating data that logically resides in one or more nested collections in a nested collection column. A Data Manipulation Language (DML) statement that operates on one or more of the nested collections is detected and trigger code is executed once for each individual element within the nested collections targeted by the DML statement. The trigger code may include references to parent values; however, the triggers are designed to fire when a row of a database table or a table view is updated, inserted or deleted. In other words, only a single row is updated at a time. This process is slow and tedious and does not permit updates at any designated nested level. 
   U.S. Pat. No. 6,493,708 discloses a mechanism for defining a hierarchical dimension, the various levels thereof, and the relationships among the levels using a CREATE DIMENSION statement that includes various LEVEL statements to identify the levels of the hierarchy. A dimension table embeds the hierarchical relationships between granules in various levels of the dimension, assuming that the levels go from a finer to a coarser level. However, no general mechanism is taught for updating nested tables for values in respective rows that are not necessarily related to each other as finer/coarser representations of the same data. 
   The SQL 2003 standard specifies two kinds of collections—arrays and multisets. Columns of a table can be one of these two types. In existing database systems that implement arrays and multisets, the standard specifies syntax and semantics for modifying the collection-valued column in its entirety where the old value is replaced by an entirely new value. The prior art does not specify any way to modify the collection-valued column incrementally. A technique is desired that permits one to perform incremental modifications to such collections since it can be very expensive to replace an entire large collection with a new collection while the need is to only modify a small portion of it. The present invention addresses these needs in the art. 
   SUMMARY OF THE INVENTION 
   The present invention meets the above-mentioned needs in the art by providing a new way to update collection-valued columns in a nested table using a nested extension of the SQL UPDATE statement. The proposed extension uses syntax and semantics to modify collection-valued columns that is analogous to the syntax and semantics of the conventional UPDATE statement that is used to modify scalar-valued columns of the table (called the outer UPDATE). This is desirable since using the same syntactic and semantic constructs as the table at the outer level allows an existing implementation that processes modifications to relational tables to reuse its implementation techniques for processing updates to modify collection-valued columns as well. Also, such UPDATE extensions in accordance with the invention enable the specification of updates to nested collections embedded at arbitrary levels of depth in the hierarchy. 
   The new syntax is embedded inside the outer UPDATE statement in a way that parallels the structure of the data itself. The syntax thus maps more directly to the user&#39;s conceptual model of the data and is hence easier to understand. The proposed extension to the UPDATE statement allows updates to both the collection-valued columns and to other scalar-valued columns simultaneously using the same statement which allows for efficient processing of the modification. 
   A relational database system that implements UPDATE statements using change descriptors in accordance with the invention includes a parser that parses a database modification (query) statement and produces a logical description of changes to the table as specified by the UPDATE statement, a query optimizer that produces the execution algorithm that will perform the modifications, and finally a query execution engine that implements the execution algorithm. The execution algorithm consists of the following steps: (i) determine the rows in the complex structured type column (e.g., nested table) that need to be updated and calculate the new values for the columns in the complex structured type column to be updated, and (ii) apply the calculated new values to the complex structured type column. For modifications to collection-valued columns, step (ii) uses a data structure (change descriptor) that represents an aggregation of changes to the values in the collection-valued column and the location of the values to be updated in the hierarchy of the complex structured type column. In step (ii), the query execution engine reads the change descriptor and applies the changes as described by it to the collection-valued columns in addition to using simple scalar updates for the scalar valued columns. 
   The method for implementing the UPDATE extensions uses a technique, called the change descriptor, which is a data structure that aggregates all changes, both scalar and collection-valued, into a single value that provides a complete description of the changes to be made in a collection-valued column. The change descriptor tells the query execution engine what to change and where and is packaged as a conventional scalar but with all the hierarchical information needed to modify the scalars in the designated hierarchical levels. The change descriptor thus enables the efficient application of multiple updates at various granularity levels in a single operation. The change descriptor also enables the implementation of efficient index maintenance algorithms by updating only the indexes affected by the specific scalar fields modified at various nesting levels by the SET clause in the UPDATE operation and also updating only those rows of the index that correspond to the actual elements that got modified by the UPDATE operation. The change descriptor also has the benefit of separating the computation of the changes from their application itself (known as Halloween Protection), i.e. to prevent the update statement from side effecting itself. This could happen if the computation and the application of the changes were not strongly separated, because the first phase could be improperly affected, as a result of seeing the intermediate changes to the data the second phase might have produced. 
   The invention thus enables the use of nested relational SQL language extensions to modify tables with a hierarchical structure (such as nested tables and tables that store complex structured objects or XML) in arbitrary ways in one step and provides the mechanisms (change descriptor, leveraging of query optimization and query execution techniques) to achieve complex and partial updates efficiently. The SQL language extensions of the invention also enable rich and efficient support for managing and querying complex structured type relational or XML data in a database adapted to implement the invention. 

   
     BRIEF DESCRIPTION OF THE DRAWINGS 
     The foregoing summary, as well as the following detailed description of the invention, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, the drawings include exemplary embodiments of various aspects of the invention; however, those skilled in the art will appreciate that the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings: 
       FIG. 1  illustrates a nested table update of the Salary scalar which is implemented by enumerating the rows that satisfy the predicate in the query and calculating the new value of the Salary column for each row. 
       FIGS. 2-4  illustrate three examples of nested UPDATE statements in accordance with the invention including diagrams outlining the change descriptor content and the effects of its application. 
       FIG. 5  illustrates the steps of parsing, optimizing and executing a regular update of a table using a conventional UPDATE instruction in a conventional SQL Server system. 
       FIG. 6  illustrates the nested update case of the invention whereby the query execution process is modified to compute the change descriptor in accordance with the invention. 
   

   DETAILED DESCRIPTION OF THE INVENTION 
   The subject matter of the present invention is described with specificity to meet statutory requirements (35 U.S.C. 1 et seq.). However, the description itself is not intended to limit the scope of the invention. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways to include different steps or elements similar to the ones described herein as may be used in conjunction with other present or future technologies during the lifetime of this patent. Moreover, although the term “step” may be used herein to connote different aspects of methods employed, this term should not be interpreted as implying any particular order among or between various steps herein disclosed unless and except when a specific order of individual steps is explicitly described as being necessary. 
   Those skilled in the database and memory management arts will appreciate that the present invention will be useful to any extended relational database system that supports nested tables, such as MYSQL. Accordingly, the present invention described herein with respect to  FIGS. 1-6  is to be understood to be applicable to all such systems. 
   Definitions: 
   Complex Structured Type: A complex structured type consists of a set of fields, properties and methods. Each field or property can be one of:
         a scalar type;   a complex structured type itself;   a multiset in which each element is a complex structured type.       

   Complex structured types are restricted to be non-recursive. In other words, a complex structured type cannot include a property of field of that same type. A complex structured type as defined herein includes nested tables, collection-valued tables, and other multi-dimensional data structures. 
   Multisets: A multiset is a type of collection. It is a set of unordered objects with possible duplicates. The multiset is strongly typed in the sense that it defines the type of the elements it contains. This document will use the notation Multiset&lt;T&gt; to denote a multiset of elements of type T. 
   In both complex structured types and multiset-valued types, it is possible to have arbitrarily deep levels of nesting. 
   A complex structured type may be represented canonically with the following syntax. In this example, the AddressType has a field called PhoneNos which is collection-valued and is typed Multiset&lt;PhoneNoType&gt;: 
                                                                   class   AddressType {               SqlString  Street,               SqlString  City,               SqlString  Country,                Multiset&lt;PhoneNoType&gt; PhoneNos                }                        
where PhoneNoType is defined as
 
   
     
       
             
             
           
             
             
             
           
             
             
           
         
             
                 
                 
             
           
           
             
                 
               class PhoneNoType { 
             
           
        
         
             
                 
                 SqlString 
               AreaCode, 
             
             
                 
                 SqlString 
               Number, 
             
             
                 
                 SqlString 
               Extension 
             
           
        
         
             
                 
               } 
             
             
                 
                 
             
           
        
       
     
   
   The following tables use the types defined above. First a MULTISET type is created for a Multiset of AddressType. Then that type is used to define a column of the Employees table: 
   
     
       
             
             
           
             
             
             
           
             
             
           
         
             
                 
                 
             
           
           
             
                 
               CREATE TYPE AddressesType AS MULTISET(AddressType) 
             
             
                 
               CREATE TABLE Employees ( 
             
           
        
         
             
                 
               EmpID 
               int, 
             
             
                 
               FirstName 
               varchar(30), 
             
             
                 
               LastName 
               varchar(30), 
             
             
                 
               Salary 
               int, 
             
             
                 
               Addresses 
               AddressesType 
             
           
        
         
             
                 
               ) 
             
             
                 
                 
             
           
        
       
     
   
   Embodiments of Invention 
   The present invention provides a technique for providing data modification capabilities for tables with complex structures (i.e., tables that contain both structured columns and multiset-valued columns). In a preferred embodiment of the invention, these features are part of a SQL Server engine for updating data stored in a relational database. For example, the present invention is efficiently used in conjunction with applications that often have a data model that is more complex than a 1NF (or “flat”) relational model. The data types that they model have complex internal structure and/or include multisets of values. Typically, such applications model this data using a set of flat tables. Complex structured types and multisets provide a way to model such data whose logical schema maps more naturally to the original data model. The present invention may be used to update relational data in multisets that are embedded inside such a complex structured type. As will be explained in more detail below, the invention also includes the ability to modify multiset data with the level of richness and expressive power that SQL provides at the outer most level on flat tables. 
   In accordance with the invention, an SQL statement is being enhanced to support modifications to collection-valued columns (multisets) of a table. The SQL statement that is being enhanced to support modifications to collection-valued columns of a table in accordance with the invention is the UPDATE statement. The general format of the conventional UPDATE statement is as follows, where syntax elements surrounded by &lt;&gt; are non-terminals that are expanded later in the description: 
   
     
       
             
           
         
             
                 
             
           
           
             
               UPDATE &lt;target-table&gt; 
             
             
               SET &lt;scalar-column-modification1&gt;, &lt;scalar-column-modification&gt;, .... 
             
             
                 ... 
             
             
               WHERE &lt;search-condition&gt; 
             
             
                 
             
           
        
       
     
   
   where &lt;target-table&gt; is the table being modified, &lt;scalar-column-modification&gt; specifies the modification of a scalar-valued column and is of the following form:
 
&lt;target-column1&gt;=&lt;value-expression&gt;
 
   where &lt;target-column&gt; is the name of the column being modified and &lt;value-expression&gt; is a scalar valued expression that supplies the new value to which &lt;target-column&gt; should be modified. 
   The proposed extension of the UPDATE statement in accordance with the invention introduces another kind of modification (&lt;collection-column-modification&gt;) in the SET clause that can be used to modify collection-valued columns. A &lt;collection-column-modification&gt; is one of the following forms: 
   
     
       
             
             
           
         
             
                 
                 
             
           
           
             
                 
                 (UPDATE &lt;collection-valued-column&gt; 
             
             
                 
                 SET ... 
             
             
                 
                 WHERE &lt;search-condition&gt;) 
             
             
                 
               Or 
             
             
                 
                 (DELETE FROM &lt;collection-valued-column&gt; 
             
             
                 
                 WHERE ...) 
             
             
                 
               Or 
             
             
                 
                 (INSERT INTO &lt;collection-valued-column&gt; 
             
             
                 
                 VALUES (...) 
             
             
                 
                 ) 
             
             
                 
                 
             
           
        
       
     
   
   In other words, the &lt;collection-column-modification&gt; uses INSERT/UPDATE/DELETE syntax that is similar to INSERT/UPDATE/DELETE against the outer-table. The SET clause of the inner UPDATE can in turn specify modifications to collection-valued columns inside the outer collection-valued column, and thus enables modifications to collection-valued columns in any level of nesting using the same recursively nested syntactic approach. In essence, modifications on collection-valued columns are modeled as UPDATEs on the outer table by embedding the INSERT/UPDATE/DELETE in the SET clause of the outer UPDATE statement. 
   As noted above, the data structure that aggregates all changes, both scalar and collection-valued, into a single value that provides a complete description of the changes to be made in a complex-structured, object-valued or collection-valued column in accordance with the invention is referred to herein as a “change descriptor.” The change descriptor tells the UPDATE instruction what to change and where in the complex structured type hierarchy and is packaged as a conventional scalar so as to permit the UPDATE instruction to update scalars in the designated hierarchical levels. The change descriptor enables the implementation of efficient index maintenance algorithms by updating only the indexes affected by scalar or collection-valued fields affected by the set clause in the UPDATE operation and also updating only those rows of the index that correspond to the actual elements of the collection that got modified by the UPDATE operation. The present invention thus uses a change descriptor to implement complex and partial updates to table columns that are not scalar, but rather have a hierarchical structure. 
   Examples of the implementation of the change descriptor will be provided below with respect to updates to an Employees table, with the scalar-valued columns: FirstName, LastName and EmployeeID, Salary and a collection-valued column called Addresses which stores a set of addresses. Each address in the collection-valued column has the following scalar-valued columns: Street, City, State, ZipCode and a collection-valued column called PhoneNos. For example: 
   
     
       
             
             
           
             
             
           
             
             
           
             
             
           
         
             
                 
                 
             
           
           
             
                 
               Employees 
             
           
        
         
             
                 
               EmployeeID 
             
             
                 
               FirstName 
             
             
                 
               LastName 
             
             
                 
               Salary 
             
             
                 
               Addresses 
             
           
        
         
             
                 
               Street 
             
             
                 
               City 
             
             
                 
               State 
             
             
                 
               ZipCode 
             
             
                 
               PhoneNos 
             
           
        
         
             
                 
               AreaCode 
             
             
                 
               Number 
             
             
                 
               Extension 
             
             
                 
                 
             
           
        
       
     
   
   The syntax of conventional UPDATE statements only allows modifying table columns as a whole, by assigning them to their new value. As an example, if employees 1234 and 1235 in the table “Employees” are to be given a 10% salary raise, then this operation can be implemented with the following conventional syntax: 
   
     
       
             
             
           
         
             
                 
                 
             
           
           
             
                 
               UPDATE Employees 
             
             
                 
               SET Salary = Salary * 1.1 
             
             
                 
               WHERE EmpID = 1234 OR EmpID = 1235 
             
             
                 
                 
             
           
        
       
     
   
   Such UPDATEs are processed using two phases. During the first phase, the rows to be changed are enumerated and the new values for the columns to be modified are calculated. This process produces a stream of data representing the changes to be performed, called herein a delta stream. In the second phase, the columns are modified as per this delta stream. 
   In accordance with the invention, on the other hand, UPDATE statements modify parts of a complex-structured collection-valued column using a variation of the same mechanism using two phases. In the first phase, in accordance with the invention, the delta stream uses a new data structure that aggregates all the changes to the collection valued column. As illustrated in  FIG. 1 , the first phase of the update will be implemented by enumerating the rows that satisfy the predicate in the query and calculating the new value of the Salary column for each of them. This will produce the delta stream for the update. The second phase includes the step of applying the delta stream to the table itself, so as to perform the previously gathered changes. 
   As described herein, the change descriptor technique is a way to implement fine-grained, rather than full, changes to complex-structured or collection-valued columns, extending the concept of delta stream mentioned above. The set of changes to be applied to a collection-valued column as part of a nested update can be seen as a delta stream in itself. This delta stream is nested inside the top-most delta stream representing the changes to the table. Changes to collection-valued columns contained inside a collection-valued column again can be represented with a further nested delta stream. 
   The change descriptor is a compact and scalar representation of the nested delta streams. Representing it as a scalar value allows it to be seamlessly gathered together with the other new values of regular table columns during the generation of the top-most, table level delta stream. This allows scalar and multi-level nested updates to be mixed together in the same statement. 
   The implementation of the second phase of the update understands that the change descriptor does not contain the full new value of the collection-valued columns, but rather only the set of fine-grained changes to be applied. The implementation is also aware of the storage format of the collection-valued column, and is able to translate the information contained inside the change descriptor into physical operations. Hence, the change descriptor format is rather flexible and not too implementation dependent, and can be used with a variety of other kinds of complex structures such as XML, object types in addition to collection-valued columns. 
     FIGS. 2-4  illustrate three examples of nested update statements, and the corresponding diagrams outlining the change descriptor content and the effects of its application. The first statement ( FIG. 2 ) will change the records for the two employees, at the same time giving the 10% raise and updating the ZipCode for addresses in Washington State. 
   
     
       
             
             
           
         
             
                 
                 
             
           
           
             
                 
                 UPDATE Employees 
             
             
                 
                 SET Salary = Salary 1.1, 
             
             
                 
                 (UPDATE Addresses A(addr) 
             
             
                 
                 SET addr.ZipCode = ‘98074’, 
             
             
                 
                 WHERE addr.State = ‘WA’) 
             
             
                 
               WHERE EmpID = 1234 OR EmpID = 1235 
             
             
                 
                 
             
           
        
       
     
   
   The second statement ( FIG. 3 ) is similar, but it also updates the AreaCode field inside some of phones contained inside the addresses being updated. This shows the ability to modify scalar values in 3 levels of the hierarchy in the same statement (Salary in level 1, Zipcode in level 2 and AreaCode in level 3). 
   
     
       
             
             
           
         
             
                 
                 
             
           
           
             
                 
               UPDATE Employees 
             
             
                 
               SET Salary = Salary * 1.1, 
             
             
                 
                 (UPDATE Addresses A(addr) 
             
             
                 
                 SET addr.ZipCode = ‘98074’, 
             
             
                 
                   (UPDATE addr.PhoneNos P(phone) 
             
             
                 
                   SET phone.AreaCode = ‘425’ 
             
             
                 
                   WHERE phone.AreaCode = ‘206’) 
             
             
                 
                 WHERE addr.State = ‘WA’) 
             
             
                 
               WHERE EmpID = 1234 OR EmpID = 1235 
             
             
                 
                 
             
           
        
       
     
   
   In the third example ( FIG. 4 ), together with the raise, the two employees have their addresses in Seattle removed. 
   
     
       
             
             
           
         
             
                 
                 
             
           
           
             
                 
               UPDATE Employees 
             
             
                 
               SET Salary = Salary * 1.1, 
             
             
                 
                 (DELETE FROM Addresses 
             
             
                 
                 WHERE City = ‘Seattle’) 
             
             
                 
               WHERE EmpID = 1234 OR EmpID = 1235 
             
             
                 
                 
             
           
        
       
     
   
   Code Implementation of Change Descriptors 
   The code for implementing the change descriptors in accordance with the invention operates to build the change descriptors and to consume the change descriptors. The change descriptors are built from the bottom up in the hierarchy, and operators receiving the change descriptors break them down in accordance with the syntax set forth in detail above. The syntax specifies the update location in the hierarchical nested table structure and maintains a hierarchical record of the multi-valued stored data. Since the change descriptor embodies location information as well as scalar information, hierarchical data within a cell may be updated using a single step in the query execution algorithm as in the examples above. 
     FIGS. 5 and 6  illustrate the implementation of the change descriptors of the invention in the examples of  FIGS. 2-4  above.  FIG. 5  illustrates the steps of parsing, optimizing and executing a regular update of a cell using a conventional UPDATE instruction in a conventional SQL Server system.  FIG. 6  illustrates the nested update case of the invention whereby the query execution process is modified to compute the change descriptor in accordance with the syntax above. As illustrated, the relational database system includes a SQL parser that parses the received SQL statement and produces a logical description of what the user requires to be done by the database (e.g., insert, update, or delete data) and a query optimizer that produces an execution algorithm using techniques known in the art. In accordance with the invention, the conventional query execution of  FIG. 5  is modified to further include the step of computing the change descriptor for making each of the changes in the nested tables set forth in the change descriptor. Further, the query execution engine in accordance with the invention is enhanced to read the change descriptor and apply the changes as described by the change descriptor to the table. In the example of  FIG. 6 , the Addresses are updated in addition to the salary. Once the changes are gathered, they are applied to the Employees table in the database (not shown) that is associated with the SQL Server system of the invention. 
   Those skilled in the art will appreciate from  FIG. 6  that the change descriptor of the invention enables the implementation of efficient index maintenance algorithms by updating only the indexes affected by the specific scalar fields modified at various nesting levels by the SET clause in the UPDATE operation and also updating only those rows of the index that correspond to the actual elements that got modified by the UPDATE operation. The change descriptor also has the benefit of separating the computation of the changes from their application (known as Halloween Protection), i.e. to prevent the update statement from side effecting itself. This could happen if the computation and the application of the changes were not strongly separated in two separate steps, because the first phase could be improperly affected, as a result of seeing the intermediate changes to the data the second phase might have produced. 
   Those skilled in the art will also appreciate that the present invention is particularly advantageous for storing large data types as fields of a user defined type within a database management system. It is understood that changes may be made to the embodiments described above without departing from the broad inventive concepts thereof. For example, while an embodiment of the present invention has been described above in the context of Microsoft&#39;s SQL SERVER database management system, it is understood that the present invention may be embodied in any database management system (e.g., object oriented database, XML database, etc.) that supports the use of SQL UPDATE statements. Additionally, while certain aspects of the present invention have been described as being embodied in the context of a relational database system such as SQL Server, it is understood that those aspects of the present invention are by no means necessarily limited to implementation in that environment. Accordingly, it is understood that the present invention is not limited to the particular embodiments disclosed, but is intended to cover all modifications that are within the spirit and scope of the invention as defined by the appended claims.