Method and system for effecting incremental changes to a repository

US10339113B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10339113-B2
Application numberUS-201414492469-A
CountryUS
Kind codeB2
Filing dateSep 22, 2014
Priority dateSep 21, 2013
Publication dateJul 2, 2019
Grant dateJul 2, 2019

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, system, and computer-program product for effecting incremental changes to a repository are disclosed. The method includes receiving an incremental feature package and applying the one or more revisions to the repository. In such methods, systems, and computer-program products, the incremental feature package includes one or more revisions to be made to a repository.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method comprising: receiving, by a computing system, an incremental feature package, wherein the incremental feature package comprises one or more revisions to be made to a repository, the repository including a first set of data that provides a logical construction for the interpretation of a second set of data stored in an associated database, the repository storing a third set of data describing one or more objects, and further wherein the one or more revisions include information for updating a portion of at least one first object stored in the repository, the first object comprising a plurality of components, and the incremental feature package comprises a first delta file, the first delta file being generated based at least in part on a location of a change in the first object and an object tag table comprising the change in the first object; causing, by the computing system, the one or more revisions to be merged with the repository, wherein the one or more revisions update the portion of the first object stored in the repository; and causing, by the computing system, a schema definition of the associated database to be synchronized with a schema definition of the repository. 2. The method of claim 1 , wherein the repository comprises one or more customizations, and the one or more customizations were made by a user. 3. The method of claim 2 , further comprising: customizing the repository, wherein the customizing results in the one or more customizations, the one or more customizations are configured to customize an application program, and the application program is configured to access the repository. 4. The method of claim 2 , wherein the customizing comprises: incorporating a reusable module into an end-user created module. 5. The method of claim 4 , wherein the reusable module is an object, and the object is stored in the repository. 6. The method of claim 4 , further comprising: detecting a conflict between the end-user created module and an existing module, wherein the end-user created module is the result of applying the one or more customizations to the reusable module. 7. The method of claim 1 , wherein the object tag table comprises: a user tag associated with an user associated with the repository, a first object tag associated with the first object, and information describing the change in the first object, wherein the information comprises: a conflict information describing that the change to the first object, based on an object hierarchy, creates a conflict with a second object, an instruction from the user to implement the change, changes in the second object to resolve the conflict, and a record describing that the change to the first object is associated with the repository; wherein generating the first delta file is further based on the change in the second object; wherein causing the schema definition of the associated database to be synchronized with the schema definition of the repository comprises: generating a second delta file based on the object tag table, wherein the second delta file does not contain the change in the first object and the change in the second object, and causing the second delta file to be merged with the associated database. 8. A computer system comprising: a processor; a computer-readable storage medium coupled to the processor; and a plurality of instructions, encoded in the computer-readable storage medium and configured to cause the processor to receive an incremental feature package, wherein the incremental feature package comprises one or more revisions to be made to a repository, the repository including a first set of data that provides a logical construction for the interpretation of a second set of data stored in an associated database, the repository storing a third set of data describing one or more objects, and further wherein the one or more revisions include information for updating a portion of at least one first object stored in the repository, the first object comprising a plurality of components, and the incremental feature package comprises a first delta file, the first delta being generated based at least in part on a location of a change in the first object and an object tag table comprising the change in the first object; cause the one or more revisions to be merged with the repository, wherein the one or more revisions update the portion of the first object stored in the repository; and causing a schema definition of the associated database to be synchronized with a schema definition of the repository. 9. The computer system of claim 8 , wherein the repository comprises one or more customizations, and the one or more customizations were made by a user. 10. The computer system of claim 9 , wherein the plurality of instructions is further configured to cause the processor to: customize the repository, wherein execution of the instructions configured to cause the processor to customize results in the one or more customizations, the one or more customizations are configured to customize an application program, and the application program is configured to access the repository. 11. The computer system of claim 10 , wherein the plurality of instructions configured to cause the processor to customize the repository is further configured to cause the processor to: incorporate a reusable module into an end-user created module. 12. The computer system of claim 11 , wherein the reusable module is an object, and the object is stored in the repository. 13. The computer system of claim 10 , wherein the plurality of instructions configured to cause the processor to apply the one or more revisions to the repository is further configured to cause the processor to: associate a user with a tag; and track a customization made to an object, wherein the object is stored in the repository, and the tracking is performed using the tag. 14. The computer system of claim 8 , wherein the plurality of instructions is further configured to cause the processor to: detect a conflict between the end-user created module and an existing module, wherein the end-user created module is the result of applying the one or more customizations to the reusable module. 15. A computer program product comprising: a plurality of instructions, comprising a set of instructions, executable on a computer system, configured to receive an incremental feature package, wherein the incremental feature package comprises one or more revisions to be made to a repository, the repository including a first set of data that provides a logical construction for the interpretation of a second set of data stored in an associated database, the repository storing a third set of data describing one or more objects, and further wherein the one or more revisions include information for updating a portion of at least one first object stored in the repository, the first object comprising a plurality of components, and the incremental feature package comprises a first delta file, the first delta file being generated based at least in part on a location of a change in the first object and an object tag table comprising the change in the first object; a set of instructions, executable on the computer system, configured to cause the one or more revisions to be merged with the repository, wherein the one or more revisions update the portion of the first object stored in the repository; a set of instructions, executable on the computer system, configured to cause

Assignees

Inventors

Classifications

  • G06F16/21Primary

    Design, administration or maintenance of databases · CPC title

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 US10339113B2 cover?
A method, system, and computer-program product for effecting incremental changes to a repository are disclosed. The method includes receiving an incremental feature package and applying the one or more revisions to the repository. In such methods, systems, and computer-program products, the incremental feature package includes one or more revisions to be made to a repository.
Who is the assignee on this patent?
Oracle Int Corp
What technology area does this patent fall under?
Primary CPC classification G06F16/21. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Jul 02 2019 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).