Abstract: A method, device, and non-transitory computer-readable storage medium are provided for efficiently registering a relational schema. In co-compilation and data guide approaches, a subset of entities from schema descriptions are selected for physical registration, and other entities from the schema descriptions are not physically registered. In the co-compilation approach, a first schema description references a second schema description, and the subset includes a set of entities from the second schema description that are used by the first schema description. In the data guide approach, the subset includes entities that are used by a set of structured documents. In a pay-as-you-go approach, schema registration includes logically registering entities without creating relational database structures corresponding to the entities. A database server may execute database commands that reference the logically registered entities.

Abstract: A method, device, and non-transitory computer-readable storage medium are provided for efficiently registering a relational schema. In co-compilation and data guide approaches, a subset of entities from schema descriptions are selected for physical registration, and other entities from the schema descriptions are not physically registered. In the co-compilation approach, a first schema description references a second schema description, and the subset includes a set of entities from the second schema description that are used by the first schema description. In the data guide approach, the subset includes entities that are used by a set of structured documents. In a pay-as-you-go approach, schema registration includes logically registering entities without creating relational database structures corresponding to the entities. A database server may execute database commands that reference the logically registered entities.

Abstract: A method, device, and non-transitory computer-readable storage medium are provided for efficiently registering a relational schema. In co-compilation and data guide approaches, a subset of entities from schema descriptions are selected for physical registration, and other entities from the schema descriptions are not physically registered. In the co-compilation approach, a first schema description references a second schema description, and the subset includes a set of entities from the second schema description that are used by the first schema description. In the data guide approach, the subset includes entities that are used by a set of structured documents. In a pay-as-you-go approach, schema registration includes logically registering entities without creating relational database structures corresponding to the entities. A database server may execute database commands that reference the logically registered entities.

Abstract: A method, device, and non-transitory computer-readable storage medium are provided for efficiently registering a relational schema. In co-compilation and data guide approaches, a subset of entities from schema descriptions are selected for physical registration, and other entities from the schema descriptions are not physically registered. In the co-compilation approach, a first schema description references a second schema description, and the subset includes a set of entities from the second schema description that are used by the first schema description. In the data guide approach, the subset includes entities that are used by a set of structured documents. In a pay-as-you-go approach, schema registration includes logically registering entities without creating relational database structures corresponding to the entities. A database server may execute database commands that reference the logically registered entities.

Abstract: Techniques for implementing a scalable DOM and a pluggable DOM are provided. A scalable DOM implementation manages a DOM tree in memory to free unreferenced nodes, avoid generating nodes unnecessarily, and avoid storing multiple versions of the same data on disk. A pluggable DOM implementation includes an abstract interface that is defined between the API layer and the data layer of a DOM implementation. An implementation of the abstract interface is defined for each data source that is plugged in to the pluggable DOM implementation and that stores XML data in a different format.

Abstract: An XML Extractor that extracts XML data from streamed input based on registered XPaths is provided. XPaths and associated content handlers instances are registered at runtime with the XML Extractor. The XML Extractor receives streaming input that represents XML data at a stream-based parser, and evaluates the received input against the registered XPaths expression. In response to detecting that the received streaming input includes an XPath that matches a registered XPath expression, the XML Extractor generates output to the content handler associated with the matching registered XPath expression.

Abstract: Methods and apparatus for enabling an object associated with an XML node class to be used for both a document object model (DOM) application programming interface (API) that supports an in-memory representation of XML nodes and a DOM API that supports a database-backed representation of XML nodes are disclosed. According to one aspect of the present invention, a method for creating an object that represents an XML node in a Java space includes determining whether the object is to represent a pure node. An object of a first class is created to represent a database-backed node when the object is not determined to represent the pure node, and the object of the first class is created to represent a pure node when the object is determined to represent the pure node. The object includes the same set of fields whether the object represents a pure node or a database-backed node.

Abstract: Techniques for implementing a scalable DOM and a pluggable DOM are provided. A scalable DOM implementation manages a DOM tree in memory to free unreferenced nodes, avoid generating nodes unnecessarily, and avoid storing multiple versions of the same data on disk. A pluggable DOM implementation includes an abstract interface that is defined between the API layer and the data layer of a DOM implementation. An implementation of the abstract interface is defined for each data source that is plugged in to the pluggable DOM implementation and that stores XML data in a different format.

Abstract: Techniques for implementing a schema-aware mid-tier binary XML are provided. Token vocabularies are stored in a repository that is accessible to mid-tier applications from separate database systems. The token vocabularies are thus shared among the mid-tier applications of each database system. The repository may be part of a file system or database that is separate from any of the database systems, or the repository may be part of one of the database systems.

Abstract: An XML processing model enables applications that use an XML stream to perform metadata-based or other processing of data during a data validation operation while preserving a streaming processing model. For example, while an XML node is being validated, requests can be received regarding the status of the validation and any processing that may be required with the node in order to conform it to requirements of an external application. A validator exposes public APIs that allow such validation-time requests from an event handler that is associated with an external application and that is registered with the XML stream. Messages that identify schema annotation definitions are provided to an external application to direct the type of processing to be performed on nodes at application runtime. Thus, applications can process a node according to the annotation definition concurrently with validation of the given node by the validator.

Abstract: Techniques for implementing a scalable DOM and a pluggable DOM are provided. A scalable DOM implementation manages a DOM tree in memory to free unreferenced nodes, avoid generating nodes unnecessarily, and avoid storing multiple versions of the same data on disk. A pluggable DOM implementation includes an abstract interface that is defined between the API layer and the data layer of a DOM implementation. An implementation of the abstract interface is defined for each data source that is plugged in to the pluggable DOM implementation and that stores XML data in a different format.

Abstract: Techniques for implementing a scalable DOM and a pluggable DOM are provided. A scalable DOM implementation manages a DOM tree in memory to free unreferenced nodes, avoid generating nodes unnecessarily, and avoid storing multiple versions of the same data on disk. A pluggable DOM implementation includes an abstract interface that is defined between the API layer and the data layer of a DOM implementation. An implementation of the abstract interface is defined for each data source that is plugged in to the pluggable DOM implementation and that stores XML data in a different format.

Abstract: Techniques for implementing a schema-aware mid-tier binary XML are provided. Token vocabularies are stored in a repository that is accessible to mid-tier applications from separate database systems. The token vocabularies are thus shared among the mid-tier applications of each database system. The repository may be part of a file system or database that is separate from any of the database systems, or the repository may be part of one of the database systems.

Abstract: Methods and apparatus for enabling an object associated with an XML node class to be used for both a document object model (DOM) application programming interface (API) that supports an in-memory representation of XML nodes and a DOM API that supports a database-backed representation of XML nodes are disclosed. According to one aspect of the present invention, a method for creating an object that represents an XML node in a Java space includes determining whether the object is to represent a pure node. An object of a first class is created to represent a database-backed node when the object is not determined to represent the pure node, and the object of the first class is created to represent a pure node when the object is determined to represent the pure node. The object includes the same set of fields whether the object represents a pure node or a database-backed node.

Abstract: An XML Extractor that extracts XML data from streamed input based on registered XPaths. XPaths and associated content handlers instances are registered at runtime with the XML Extractor. The XML receives streaming input that represents XML data at a stream-based parser, and evaluates the received input against the registered XPaths expression. In response to detecting that the received streaming input includes an XPath that matches a registered XPath expression, generating output to the content handler associated with the matching registered XPath expression.

Abstract: An XML processing model enables applications that use an XML stream to perform metadata-based or other processing of data during a data validation operation while preserving a streaming processing model. For example, while an XML node is being validated, requests can be received regarding the status of the validation and any processing that may be required with the node in order to conform it to requirements of an external application. A validator exposes public APIs that allow such validation-time requests from an event handler that is associated with an external application and that is registered with the XML stream. Messages that identify schema annotation definitions are provided to an external application to direct the type of processing to be performed on nodes at application runtime. Thus, applications can process a node according to the annotation definition concurrently with validation of the given node by the validator.