Efficiently registering a relational schema

US9330124B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9330124-B2
Application numberUS-201314044982-A
CountryUS
Kind codeB2
Filing dateOct 3, 2013
Priority dateNov 30, 2010
Publication dateMay 3, 2016
Grant dateMay 3, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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. A request to store data for the entities may be executed by creating relational database structures to store the data.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving a request to create unspecified relational database structures for storing, in a relational database, structured documents described by at least a first schema description that references a second schema description; in response to receiving the request: determining that the first schema description uses a first set of entities of the second schema description, wherein the second schema description includes the first set of entities and a second set of entities that are not used by the first schema description; and creating first relational database structures corresponding to the first set of entities of the second schema description without creating second relational database structures corresponding to the second set of entities of the second schema description; wherein the method is performed by one or more special-purpose computing devices. 2. The method of claim 1 , wherein the structured documents comprise XML documents, wherein the first schema description comprises a first XML schema, and wherein the second schema description comprises a second XML schema. 3. The method of claim 1 , wherein the first relational database structures comprise relational database tables and types. 4. The method of claim 1 , comprising creating a structured index that indexes the first set of entities of the second schema description but not the second set of entities of the second schema description. 5. A method comprising: receiving a request to create an unspecified relational schema for storing, in a relational database, structured documents described by one or more schema descriptions; in response to receiving the request, storing particular information that defines a set of entities included in the one or more schema descriptions without creating relational database structures for the set of entities; using the particular information to execute a database command that references one or more entities of the set of entities even though one or more relational database structures for the one or more entities have not been created; wherein the method is performed by one or more special-purpose computing devices. 6. The method of claim 5 , wherein the structured documents comprise XML documents, wherein the one or more schema descriptions comprises one or more XML schemas. 7. The method of claim 5 , wherein the storing of the particular information comprises storing the particular information without creating relational database tables and types that represent entities of the set of entities. 8. The method of claim 5 , further including; receiving from a client a second request to execute the one or more database commands, executing the one or more database commands without any indication to the client that the one or more relational database structures did not exist when the second request was received. 9. The method of claim 5 , comprising: receiving a second request to store data for at least one entity of the set of entities; and in response to receiving the second request: using the particular information to create at least one new relational database structure for the at least one entity; and storing the data in the at least one new relational database structure. 10. The method of claim 9 , wherein the storing of the particular information comprises storing the particular information without creating relational database tables and types that represent entities of the set of entities, and wherein the using of the particular information to create at least one new relational database structure for the at least one entity comprises using the particular information to create at least one new relational database table and type that represents the at least one entity. 11. The method of claim 9 , wherein receiving a second request includes receiving the second request from a client, the method further including executing the second request without any indication to the client that the one or more relational database structures did not exist when the second request was received. 12. One or more non-transitory storage media comprising stored instructions which, when executed by one or more computing devices, cause: receiving a request to create unspecified relational database structures for storing, in a relational database, structured documents described by at least a first schema description that references a second schema description; in response to receiving the request: determining that the first schema description uses a first set of entities of the second schema description, wherein the second schema description includes the first set of entities and a second set of entities that are not used by the first schema description; and creating first relational database structures corresponding to the first set of entities of the second schema description without creating second relational database structures corresponding to the second set of entities of the second schema description. 13. The one or more non-transitory storage media of claim 12 , wherein the structured documents comprise XML documents, wherein the first schema description comprises a first XML schema, and wherein the second schema description comprises a second XML schema. 14. The one or more non-transitory storage media of claim 12 , wherein the first relational database structures comprise relational database tables and types. 15. The one or more non-transitory storage media of claim 12 , wherein the instructions include instructions that, when executed by said one or more computing devices, cause creating a structured index that indexes the first set of entities of the second schema description but not the second set of entities of the second schema description. 16. One or more non-transitory storage media comprising stored instructions which, when executed by one or more computing devices, cause: receiving a request to create an unspecified relational schema for storing, in a relational database, structured documents described by one or more schema descriptions; in response to receiving the request, storing particular information that defines a set of entities included in the one or more schema descriptions without creating relational database structures for the set of entities; using the particular information to execute a database command that references one or more entities of the set of entities even though one or more relational database structures for the one or more entities have not been created. 17. The one or more non-transitory storage media of claim 16 , wherein the structured documents comprise XML documents, wherein the one or more schema descriptions comprises one or more XML schemas. 18. The one or more non-transitory storage media of claim 16 , wherein the instructions include instructions that, when executed by said one or more computing devices, cause the storing of the particular information at least in part by storing the particular information without creating relational database tables and types that represent entities of the set of entities. 19. The one or more non-transitory storage media of claim 16 , wherein the instructions include instructions that, when executed by said one or more computing devices, cause: receiving from a client a second request to execute the one or more database commands; executing the one or more database commands without any indication to the client that the one or more relational database structures did not exist when the second request was received.

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9330124B2 cover?
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 descript…
Who is the assignee on this patent?
Oracle Int Corp
What technology area does this patent fall under?
Primary CPC classification G06F17/30312. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue May 03 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).