Abhyudaya Agrawal

7523131, Apr 21, 2009

Feb 10, 2005

11/056312

James W. Warner - Mountain View CA, US
Abhyudaya Agrawal - San Francisco CA, US
Hui Zhang - Fremont CA, US
Muralidhar Krishnaprasad - Fremont CA, US
Ravi Murthy - Fremont CA, US
Zhen Hua Liu - San Mateo CA, US
Nipun Agarwal - Santa Clara CA, US
Vikas Arora - San Francisco CA, US
Susan M. Kotsovolos - San Carlos CA, US
Anand Manikutty - Foster City CA, US
Rohan Angrish - Redwood City CA, US

Oracle International Corporation - Redwood Shores CA

G06F 17/00

707102, 707 4, 715234

To associate XML data objects (“child objects”), stored in rows of relational or object-relational tables, with the appropriate XML data objects (“parent objects”) from which the child objects descend, tables that contain child objects (“out-of-line” tables) are constructed with an additional column. In one embodiment, this column stores values that identify the root objects, in the appropriate table, from which the respective child objects descend. Hence, the root object from which any given object descends is traceable by following the respective value back to the corresponding root object. In one embodiment, this column stores values that identify the complete XML hierarchical path, through multiple tables, back to the root object from which the respective child objects descend. Consequently, XML query language queries against XML documents stored in such tables can be rewritten as SQL queries against the data in the tables, even in the presence of cyclic constructs.

7761479, Jul 20, 2010

Sep 11, 2006

11/519720

Abhyudaya Agrawal - San Francisco CA, US
Thomas Baby - Foster City CA, US
Ravi Murthy - Fremont CA, US
Nipun Agarwal - Santa Clara CA, US

Oracle International Corporation - Redwood Shores CA

G06F 7/00
G06F 17/00

707803, 707954

Techniques manage the presence of repeated constructs within a complex type at the time of schema registration. At registration, techniques detect repeated elements in the XML schema and analyze whether the repeated elements are from the same complex type. If so, techniques perform additional analysis to determine a minimal common ancestor. Within the context of a minimal common ancestor, techniques determine the maximum number of times an element may occur in the schema. In a choice content model, the largest maximum occurrence value is selected. In other content models, the maximum occurrence value is determined by adding together the occurrence values for the repeated elements. Then, when an object relational table is generated for the XML schema, the maximum number of times that an element appears in the schema is this value. Techniques retain the advantages of object relational storage, even after a schema evolution.

7849106, Dec 7, 2010

Dec 3, 2004

11/003611

Abhyudaya Agrawal - San Francisco CA, US
Ravi Murthy - Fremont CA, US
Nipun Agarwal - Santa Clara CA, US
Eric Sedlar - San Francisco CA, US

Oracle International Corporation - Redwood Shores CA

G06F 7/00
G06F 17/30

707803, 707809

A method and apparatus for facilitating the management of metadata is disclosed, specifically by associating metadata with an XML schema. The database system provides a method that allows end users to maintain additional information describing resources. User-defined metadata attributes are associated as an XML schema which in turn is mapped to a table, referred to as the user metadata table. The XML schema contains user-defined information specifying the metadata that the end-user wants the system to store and maintain. Additionally, a reference is created between an entry in the user metadata table and its corresponding resource entry in the resource table. The resources are accessed directly or by issuing queries against the user metadata table. The querying of the user metadata table gains the benefit of fast and efficient query results and access time.

7870163, Jan 11, 2011

Sep 28, 2006

11/540341

Abhyudaya Agrawal - San Francisco CA, US
Thomas Baby - Foster City CA, US
Nipun Agarwal - Santa Clara CA, US
Sam Idicula - San Jose CA, US
Ravi Murthy - Fremont CA, US
Eric Sedlar - Redwood City CA, US

Oracle International Corporation - Redwood Shores CA

G06F 17/30

707802, 707803

In-place XML schema evolution occurs by evaluating an existing XML schema in a database system to see if it is compatible with a new XML schema. To determine if the old schema is compatible with the new schema, a lock-step traversal is performed on the two schemas. Each instruction in the old schema is compared to instructions in the new schema. Detected differences between the two schemas are evaluated to determine if existing XML documents are still compatible with the new schema. If they are, then an in-place schema evolution operation can take place. The in-place schema operation basically, involves appending the updated object information to the underlying object type and preserving the order of elements in a document by storing element mapping information on disk.

8346725, Jan 1, 2013

Sep 15, 2006

11/521907

Thomas Baby - Foster City CA, US
Abhyudaya Agrawal - San Francisco CA, US
Sam Idicula - San Jose CA, US
Nipun Agarwal - Santa Clara CA, US

Oracle International Corporation - Redwood Shores CA

G06F 7/00

707638, 707695, 707806

XML schema evolutions can be performed on an XML-type database using partial data copy techniques. The partial data copy techniques provide mechanisms to identify a minimal set of data in the database that needs be copied out in order for schema evolution operations to occur. Identifying the minimal set of data involves comparing an existing XML schema to a new XML schema and determining the differences between the two schemas. Based on those differences, a minimal set of data can be determined. That data can then be copied to a temporary storage location, while the XML schema and its associated database structure are updated to conform to the new XML schema. Then, the minimal set of data is copied back into the modified database structure.

8554789, Oct 8, 2013

Oct 7, 2005

11/246001

Abhyudaya Agrawal - San Francisco CA, US
Ravi Murthy - Fremont CA, US
Nipun Agarwal - Santa Clara CA, US
Sivasankaran Chandrasekar - Palo Alto CA, US
Eric Sedlar - San Francisco CA, US

Oracle International Corporation - Redwood Shores CA

G06F 17/30
G06F 12/00

707778, 707829

A database system automatically detects a cyclic construct in a XML schema, determines a database representation for the cyclic construct, and maps the XML schema and elements involved in the cyclic construct to the database representation.

20070038649, Feb 15, 2007

Aug 11, 2005

11/202463

Abhyudaya Agrawal - San Francisco CA, US
Ravi Murthy - Fremont CA, US
Sivasankaran Chandrasekar - Palo Alto CA, US
Nipun Agarwal - Santa Clara CA, US
Eric Sedlar - San Francisco CA, US

G06F 7/00

707100000

A database server registers an XML schema and determines a database representation for the XML schema and mapping information, determining what database types should be used to represent an XML schema and/or how instances of the XML schema are stored by a database system. The mapping information indicates the mapping between the constructs declared in the XML schema and the constructs included in the appropriate database representation. The XML schema may contain annotations that describe one or more properties of a database representation of an XML date-time type. Based on the annotations, the database determines an appropriate database representation and generates mapping information mapping the declaration of the XML date-time type of the XML schema to the constructs of the database representation.

20070083542, Apr 12, 2007

Oct 7, 2005

11/246039

Abhyudaya Agrawal - San Francisco CA, US
Sivasankaran Chandrasekar - Palo Alto CA, US
Ravi Murthy - Fremont CA, US
Nipun Agarwal - Santa Clara CA, US
Eric Sedlar - San Francisco CA, US

G06F 7/00

707102000

A database server determines, on an element-level of granularity, what form of VARRAY storage to map collections of elements defined by a XML schema. A collection element may be mapped to an in-line VARRAY or an out-of-line VARRAY. The determination may based on a variety of factors, including the database type mapped to the collection element, database limitations that limit the form storage for certain database types, and annotations (“mapping annotations”) embedded within that XML schema that specifying a database type for database representation of a collection element or a form of VARRAY storage.