WO1995003586A1 - Method and apparatus for generation of code for mapping relational data to objects - Google Patents
Method and apparatus for generation of code for mapping relational data to objects Download PDFInfo
- Publication number
- WO1995003586A1 WO1995003586A1 PCT/US1994/007890 US9407890W WO9503586A1 WO 1995003586 A1 WO1995003586 A1 WO 1995003586A1 US 9407890 W US9407890 W US 9407890W WO 9503586 A1 WO9503586 A1 WO 9503586A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- processor
- database
- automatically generate
- class
- routine
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/289—Object oriented databases
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Abstract
A method and apparatus are provided for using an object model (20) of an object-oriented application to automatically map information (50) between an object-oriented application and a structured database (9), such as a relational database. This is done by taking into account all of the semantics (implications) of an object model, such as inheritance and relationships among object classes, and using these semantics to generate a minimal set of routines (F, G, H, J) for each object class that manipulate the object and other objects to which it is related or from which it inherits. The generated routines, when executed, provide transparent access to relational data or other field-delimited data. Object classes and routines generated using the method encapsulate all the details of database access, such that developers (computer programmers) can write object-oriented applications using those object classes without an explicit reference to or knowledge of the underlying database or its structure.
Description
METHOD AND APPARATUS FOR GENERATION OF CODE FOR MAPPING RELATIONAL DATA TO OBJECTS
BACKGROUND OF THE INVENTION The invention relates to the interrelationship of databases, particularly relational databases, and object- oriented systems. More particularly, the invention relates to relationships between objects in object-oriented systems and descriptions of objects storable in field-delimited database structures. Field-delimited databases can structure data into fields which have common attributes. For example, relational databases can structure data into tables, each with columns and rows (in "n" dimensions) forming tuples, upon which certain operations in set algebra can be performed very conveniently.
Object-oriented applications organize data and routines together into encapsulated units referred to as objects. Object-oriented applications lead to modular software systems which have increased flexibility and are easy to alter and maintain.
An object model is a formal description of an object-oriented application. The semantic elements of an object model describe object classes, attributes of object classes, relationships between object classes, and inheritance between object classes. An object model provides a powerful mechanism to represent the real world, for example because objects carry information about inherited characteristics and relationships with other objects. For example, an object model of a car can contain many classes, such as "tire." The tire class can have attributes, such as "pressure"; relationships, such as "tire" is related to an "axle"; and inheritances, such as a "snow tire" inherits from a "tire."
The difference between a relational database management system (RDBMS) and an object-oriented application is that an object "knows" what operations can be performed on its data, whereas an RDBMS only has a set of generic
operations which can be performed on its tuples. The semantics available in an object model are not preserved in a relational database. For example, a "snow tire" knows that it is related to an "axle" and inherits from a "tire." In contrast, a relational database represents this information in three separate data tables with no explicit representation of the relationships between the tables. The tire table in a relational database might have foreign key information referring to the axle table, but this representation of the relationship between tire and axle is implicit. It is up to the developer to know about these relationships, what they mean, and how to handle them.
There is a desire to build object-oriented applications that store and access data found in relational databases. For example, it would be useful to employ a plan for an automobile (an object model) to build a vehicle (an object) from an organized inventory of auto parts (a relational database) . A system is needed which can map information between a database and an object-oriented application based on the semantics of an object model. More particularly, what is needed is a mechanism for using the semantic elements of an object model to generate routines that map data between a database and an object-oriented application. Systems are known for manual mapping between objects in knowledge bases and database management systems. One approach is to employ a static class library as an interface between an object-oriented system and a relational database. An example is METHOD FOR INTEGRATING A KNOWLEDGE-BASED SYSTEM WITH AN ARBITRARY RELATIONAL DATABASE SYSTEM, U.S. Patent No. 4,930,071 issued 5/29/90 and assigned to IntelliCorp, Inc. of Mountain View, California. In static-type systems, objects can be extended to handle concepts such as relationships and inheritance, but they must be manually extended if they are to model complex real world structures. This limits their usefulness to building relatively simple object models from existing data, such as those used in rapidly building prototype systems. It is believed that there are commercial
systems which use the static-type class approach. Among the candidates include "ProKappa" from IntelliCorp, "DB.H++" from Rogue Wave of Corvallis, Oregon, and possibly "Open ODB" from Hewlett Packard Company of Cupertino, California and "UniSQL from UniSQL of Austin, Texas.
SUMMARY OF THE INVENTION According to the invention, a method and apparatus are provided for using an object model of an object-oriented application to automatically map information between an object-oriented application and a structured database, such as a relational database. This is done by taking into account all of the semantics (implications) of an object model, such as inheritance and relationships among object classes, and using these semantics to generate a minimal set of routines for each object class that manipulate the object and other objects to which it is related or from which it inherits. The generated routines, when executed (that is, when converted to an executable form which is then executed) , provide transparent access to relational data or other field-delimited data. Object classes and routines generated using the method encapsulate all the details of database access, such that developers (computer programmers) can write object-oriented applications using those object classes without any explicit reference to or knowledge of the underlying database or its structure. By working with the objects, the user of such applications transparently manipulates the database without needing to know anything of its structure. Applications can be written using the object classes to transparently integrate information from multiple databases.
The method of the invention comprises accepting a user-defined object model as a "blueprint" for an object- oriented application; accepting or constructing a schema of the structure of data in a database; and accepting or constructing a transform defining the mapping between the database schema and the object model. Based on these inputs the method automatically generates source code routines for each object class to perform four tasks: to create, retrieve,
update, and delete instances of the object class and automatically make the corresponding changes in the database. These source code routines can subsequently be executed.
The invention will be better understood by reference to the following detailed description in connection with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram of a computer system in accordance with the invention.
Fig. 2 is a schematic diagram representing the correspondence between a database schema and an object model by means of a transform.
Fig. 3 is a flow chart representing an overview of the method steps.
Fig. 4 is a flow chart representing the process for constructing the database schema and transform.
Fig. 5 is a flow chart representing the process for writing code which when executed creates an object instance and its corresponding structured information in the database.
Fig. 6 is a flow chart representing the process for writing code which when executed retrieves an object instance base on its corresponding structured information in the database. Fig. 7 is a flow chart representing the process for writing code which when executed updates an object instance and its corresponding structured information in the database. Fig. 8 is a flow chart representing the process for writing code which when executed deletes an object instance and makes corresponding changes to structured information in the database.
DESCRIPTION OF A SPECIFIC EMBODIMENT Following is a description of a specific embodiment of the method of the present invention. Section 1 sets forth terminology that is used in the remainder of the description. Section 2 provides a description of a computing system that can be used to support the steps of the method. Section 3
describes the inputs to the method. Section 4 describes an overview of the method steps. Sections 5 and 6 give more detailed descriptions of specific method steps. Section 7 concludes the description.
1. Terminology
It is helpful to clarify the general meanings of terms used in connection with object-oriented systems.
An "object class" is a set of data (attributes) and functional capabilities (routines) encapsulated into a single logical entity. For example, an employee class may be characterized by a telephone number attribute and a "hire_employee" routine.
An "object instance" is an embodiment (instantiation) of an object class. Instances are differentiated from one another by their attribute values, but not their routines (capabilities) . For example, Jane Smith may be a first person-object instance and John Doe may be a second person-object instance. The term "object" is often used by itself to refer loosely to either an object class or an object instance, the difference being understood in context.
An "object-oriented application" is an operational computer program which when employed on an appropriate computer system uses a set of object instances that work in cooperation to perform useful work. For example, an object- oriented application could be built to manage personnel records for a company, including such operations as hire new employee or add an employee to a department. An "object model" is a set of object classes that together form a blueprint for building an object-oriented application. Each object class of an object model can have attributes, inheritances, and relationships.
A "relationship" defines a link between two object classes. For example, an employee class may be related to the department class. Each specific employee, for example, "Jane Smith," would have a relationship with a specific department, such as "engineering." Relationships can be one-to-one, one-
to-many, or many-to-many. An example of a one-to-one relationship can be a relationship between employee and parking place such that each employee can have a single parking place. An example of a one-to-many relationship can be a relationship between department and employee such that each department can employ multiple employees. An example of a many-to-many relationship can be a relationship between employee and project such that each employee serves on multiple projects, and each project consists of multiple employees.
"Attributes" are data elements of object classes which are expressed through particular values in object instances. For example, a person class can have the attribute "name", and a particular person instance can have the name value "Jane Smith."
An "object ID" is used to uniquely identify each object instance. The object ID can generated in one of two ways. It can be generated by the application, which can automatically assign a unique object ID for each new object instance. Alternatively it can comprise a set of attributes that are guaranteed in the object model to always form a unique set of values for an instance. In this case, the create routine will require a unique set of attributes in order to create a new object instance. A "routine" is a functional capability associated with an object class. For example, the routine "hire_employee" could be used to create a new employee instance.
"Inheritance" represents a specialization of an object class in which the specialized class shares all of the attributes and routines of parent classes. Thus the employee class can inherit certain attributes, such as name, from the person class. In this case, the person class is called the "parent" of the employee class, and the employee class is called the "child" of the person class.
Inheritance can extend across many object class "generations." For example, the object class "snow tire" can inherit from the object class "tire", which in turn can
inherit from the object class "car_part". In this example, "car_part" is a parent of the object class "tire" and an ancestor of the object class "snow tire".
Inheritance can be "vertical" (concrete) or "horizontal" (abstract) according to how the information corresponding to inherited attributes is stored in the database. In the case of vertical inheritance between two object classes in an object model, the database contains data associated with each object class. In the case of horizontal inheritance between two object classes in the object model, the database does not contain data associated with each object class. For example, suppose that there are two object classes, "person" and "employee," and that "employee" inherits from "person." If this inheritance is vertical, then there can be a "person" table in the database which contains the attributes for each "person". If the inheritance is horizontal, there is no "person" table in the database. All the attributes of "person" are found in the "employee_data" table. Horizontal and vertical inheritance can be mixed within the same object model.
The attributes, inheritances, and relationships of all the object classes of an object model are called the "semantics" or "semantic elements" of the object model. An object model contains certain information associated with its semantics. For each attribute, the object model contains information as to whether that attribute is to be associated with the object ID for the class. For each inheritance, the object model contains information as to whether the inheritance is vertical or horizontal (concrete or abstract) . For each relationship, the object model contains information about a "delete action" associated with that relationship. The delete action specifies what happens to object instances of a related class whenever an object instance of the given class is deleted. For example, if an object instance of the object class "department" is deleted, the delete action for the employee-department relationship can specify that the employees of that department are to be deleted as well. For each relationship in the object model,
δ referential integrity must be maintained in the corresponding database tables. Referential integrity requires that the foreign key columns for any particular row always refer to valid primary key columns in the related table.
2. System Overview
Fig. 1 illustrates a digital computing system suitable to implement the method of the present invention in a typical embodiment. The system comprises computing hardware and related system software that together support the execution of method software 15, which is software that carries out the steps of the method of the invention. More particularly, the system of Fig. 1 comprises a processor 1 that is coupled to a memory 2, a storage device 3 (such as a hard disk) , and a user interface such as graphical user interface 5. The processor 1 is also coupled to at least one database, in this case to database 9 via network 7. In the illustrated embodiment the database 9 has its own associated hardware including a database processor 10 that is distinct from processor 1. In other embodiments the database 9 is a software entity that is executed by processor 1, and network 7 is not present. It will be appreciated by those of skill in the art that a wide range of computing system configurations can be used to support the method of the present invention including, for example, configurations that employ multiple processors and multiple databases.
Method software 15 makes use of certain components that are also shown in Fig. 1. Among these components are an object model 20, a database schema 30, and transform 50. Object model 20, database schema 30, and transform 50 are accepted or created at run time by the method. In Fig. l they are illustrated as inputs to be accepted. Information about the object model 20 can be accepted using the processor 1 in conjunction with graphical user interface 5 or storage device 3 to input the object model. Information about the database schema 30 and transform 50 can be accepted in a like manner; alternatively, database schema 30 and transform 50 can be constructed by the method using processor 1.
The method generates source code 12 representing code for each of the object classes in the object model 20 as output. This code, when converted to an executable form and executed, can create, retrieve, update, and delete object instances. Source code 12 can, for example, be output to storage device 3 or user interface 5, held in memory 2 and made available for further processing, or immediately or subsequently executed by processor 1 or another processor.
3. Method Inputs
Fig. 2 is a schematic diagram representing the correspondence between the database schema 30 and the object model 20 by means of a transform 50 for an example object- oriented application. According to the method of the invention, an object model is used to describe the structure of an object-oriented application, including the structure of each object in the application and the relationships and inheritances between objects. In Fig. 2, the object model 20 represents the structure of a personnel records management application. For purposes of this example, the object model 20 has three object classes: department class 101, employee class 105, and person class 109. The object model 20 contains attributes 102, 103 for the department class 101; attributes 106, 107 for the employee class 105; and attributes 110, 111 for the person class 109. The object model 20 also contains one relationship, called works_in (relationship example 104) , and one inheritance, in which employee class 105 inherits from person class 109 (inheritance example 108) . The works_in relationship expresses the idea that each department has some number of related employees that work in the department. The inheritance between employee class 105 and person class 109 expresses the idea that an employee is a kind of person (that is, employee is a child class of person, and person is a parent class of employee) . The object model 20 also contains information (not shown) about what attributes form the object ID for each class, whether the inheritance between employee and person is vertical or horizontal, and what kind of delete
action is associated with the relationship between department and employee. In this example, employee class 105 inherits vertically from its parent, person class 109.
The database schema 30 for a field-delimited database can be organized into tables, as in a relational database. As shown in Fig. 2, an exemplary relational database comprises a department table 113, an employee table 116 and a person table 122. Within each table 113, 116, 122 are columns that can be of three types: primary key, foreign key, and data.
A primary key column is employed to uniquely identify each row in a table. Multiple primary key columns can also be used in combination to uniquely identify each row in the table; an example is a combination of a first name column 123 and a last name column 124 as in person table 122. Column 114 of the department table 113, column 117 of the employee table 116, and columns 123 and 124 of person table 122 are primary key columns.
A foreign key column (or columns) can be employed to logically connect a row in a given table to a unique or specific row in another table. For example, column 121 in employee table 116 is a foreign key to column 114 of department table 113, and columns 119 and 120 of employee table 116 are foreign keys to columns 123 and 124 of person table 122.
A data column is employed to store information that is neither a primary key nor a foreign key. For example, location column 115 of department table 113 and phone (telephone number) column 118 of employee table 116 are data columns. Person table 122 has no data columns.
The transform 50 describes a mapping between elements of the object model 20 and elements of the database schema 30. Specifically, the transform 50 describes four kinds of mappings. First, there is the mapping between the attributes that make up an object ID for an object instance and the primary key columns in one or more database tables. For example the transform 50 maps the object ID attribute 102 to primary key column 114. Second, there is a mapping between
an object class attribute in a object model and a column or columns in a database. For example, the transform 50 maps attribute 107 to column 118. Third, there is the mapping between a relationship in an object model and a foreign key column or columns in a database table. For example, the transform 50 maps relationship 104 to column 121. Fourth, there is the mapping between inheritance and a foreign key column or columns in a database. For example, the transform 50 maps inheritance 108 to columns 119 and 120.
4. Method Overview
The flow chart of Fig. 3 provides an overview of the operation of the method of the invention. The method accepts object model 20 and accepts or creates database schema 30 and transform 50. Using these three elements as input, the method automatically generates source code. More particularly, the method generates the object classes in object model 20. Each generated object class contains routines to create, retrieve, update, and delete instances of that object class. Each routine takes into account the full semantics of the object model, including attributes, inheritances, and relationships in the object model. The method outputs the generated code as source code 12, which optionally can be converted to an executable form which can then be executed. The steps of the method are performed by processor 1 in conjunction with the other system components to which it is coupled. For example, processor 1 can act in conjunction with user interface 5 to accept object model 20, database schema 30, and transform 50. As another example, processor 1 can use storage device 3 to store the output source code 12, or can use network 7 to communicate the source code 12 to another processor also coupled to network 7.
The first step in the method is to accept an object model 20 (Step A) . Thereafter, if there is an existing database (Step B) , the method accepts a database schema 30 and a transform 50 from an external source (Step C) . Otherwise, the method constructs a database schema 30 and a transform 50 derived from the object model 20 (Step D) .
Thereafter a loop (step E) comprising steps F, G, H, and J is executed repeatedly, once for each object class in the object model, to generate source code routines to create (Step F) , retrieve (Step G) , update (Step H) , and delete (Step J) instances of that object class. The code generated by this loop can, for example, be C++ code where each object class in the object model is represented as a C++ class and the generated source code routines are represented as C++ routines (methods) associated with the class. Alternatively, any kind of general purpose programming language can be used to embody the code. It will be appreciated by those of skill in the art that the Steps F, G, H, and J, although conceptually distinct, can be combined or intertwined in some embodiments. Also it will be appreciated that in some embodiments each of the routines generated during the loop can be implemented as a collection of smaller routines that perform subsets of the total functionality described here.
After the loop (Step E) is complete the code generated during the loop is output (Step K) . The code can be stored, typically in a storage device such storage device 3. Alternatively or additionally, it can be displayed via user interface 5 or made available via memory 2 to the processor 1 or via network 7 to another processor for further processing. After the generated code is output, optionally this code (that is, an executable form of this code) can be executed (Step L) . Custom code can be added to the generated code, run-time libraries can be linked in, and the resulting software can be run. Execution can be performed subsequently to code generation. Execution can be carried out by processor 1 or by another processor.
5. Constructing the Database Schema and Transform
Fig. 4 illustrates in more detail the process for constructing the database schema 30 and transform 50 when the schema and transform are not accepted from an external source (Step D of Fig. 3) . A loop (Step DA) is executed repeatedly, once for each semantic element of the object model. A test is made of the semantic element (Step DB) . If the element
defines a new class, a table is added to the database schema, and a corresponding transform is added to map that table to its related class (Step DC) . For each attribute in the object model, a column is added to the database table schema and a corresponding transform is added to map that database column to the class attribute (Step DD) .
For vertical inheritance, attributes and relationships are associated with the class in which they were defined. For horizontal inheritance, attributes and relationship are associated only with the lowest level child table of the database schema. For each vertically inherited parent class, foreign key columns are added that refer to the parent table and a transform is created to map these foreign key columns to the class inheritance property (Step DF) . It will be appreciated that these primary key columns of each child table can also serve as foreign key columns which point to the parent table. For each horizontally inherited parent class, the attributes and relationships of the parent class are added to the schema for the current class (Step DE) . Alternatively, a type code column can be added to the table to differentiate between child classes.
For each one-to-one and one-to-many relationship in the object model, a foreign key column or foreign key columns are added to the database table schema in the appropriate table (Step DG) . For each many-to-many relationship in the object model, a separate join table is added to the database schema (Step DH) . This table contains foreign key references to each of the two related tables. In either case (that is, for any relationship) a corresponding transform is also created to map the foreign key columns to the class relationship.
Once the loop for all objects has been completed, construction of the schema 30 and transform 50 is complete. Next the method writes a routine which, when converted to an executable form which is then executed, creates a structured database corresponding to the database schema 30 generated by the method (Step DI) . Finally, the database schema 30 and transform 50 are made available for further processing (Step
DJ) , for example, by writing the information to storage device 3.
6. Details of Method Steps to Generate Routines For each class in the object model 20, the method generates a minimal set of operations to manipulate an object instance of the class and other object instances to which it is related or from which it inherits. More specifically, for each object class, four types of routines are written. These routines provide the functions of creating, retrieving, updating, and deleting instances of that object class. For each routine the method iterates through the object model to draw out the implications of each object model semantic element for that routine and object class. In other words, the method looks through the object model and finds every semantic element in the object model—that is, every attribute, relationship, or inheritance—that needs to be considered in order to write the given routine for the given object class, and incorporates this information when writing the routine. Once again, it will be appreciated that in some embodiments each of the routines generated during the loop can be implemented as a collection of smaller routines that perform subsets of the total functionality described here. It will be appreciated that the method uses techniques similar to those used in a programming language compiler. In the method, however, the "programming language" comprises an object model and, optionally, a database schema and transform, and the output of the "compiler" is the source code that is generated.
6.1 Steps to generate a routine to create an object instance
The flow chart of Fig. 5 expands step F of Fig. 3 to provide additional detail. It illustrates the steps to generate a create routine for a particular object class (Step
FA) .
The method performs a loop for each object model semantic element relevant to this class (Step FB) . To find these elements the method scans the entire object model and
extracts semantics that define the attributes, inheritances, and relationships for this class. Depending on the kind of semantic found (Step FC) , the method generates code to reflect the implications of the semantic in the create routine. For an object model semantic that defines an attribute of the class (Step FD) , the method performs steps that depend on the kind of attribute. If the attribute is defined as being part of the object ID (Step FG) , the method writes code that when executed (that is, when converted to an executable form which is then executed) forms a query to the database to ensure that the combination of primary key attributes define a unique object instance. If the object model indicates that the object ID attribute is to be generated by the method (Step FH) , the method writes code that when executed will generate automatically a unique primary key value for the object instance being created. For all other attribute types (Step Fl) , the attribute value for this instance is added to the database insert command (see below) .
For an object model semantic specifying that this object class inherits from a parent class, the method determines the type of inheritance (Step FE) . If the inheritance is vertical (Step FJ) , the method writes code which when executed will call the create routine for a parent instance and pass that routine the inputs it requires. If the inheritance is horizontal (Step FK) , the method adds the parent class attributes to the database insert statement for the object instance that this routine creates.
For an object model semantic that specifies a relationship between this object class and another object class, the method determines the type of relationship (Step FF) . If the relationship is one-to-one, the method uses the transform 50 to determine which database table contains the foreign key information for this relationship. The method then writes code that when executed updates that table to reflect a primary-foreign key relationship between the two tables. For example, if each employee can have one car, it can be the case that a car table contains a foreign key which points to the employee table (e.g., the employee's ID number),
or it can be the case that the employee table contains a foreign key which points to the car table (e.g., the car's license plate number) . The transform 50 tells the method which of these two is in fact the case—or more generally, where the foreign key information for a given relationship is stored.
If the relationship is one-to-many (Step FM) , the method determines which "side" of the relationship this object class is on—that is, whether this object class is on the "1" side or the "many" side of the relationship. If this class is on the "1" side of a one-to-many relationship (e.g., an employee can work in only one department) , foreign key information for the relationship can be stored in this class. Accordingly, the method generates code which when executed uses the object ID attributes of the related instance to set the foreign key column values for the instance being created (Step FO) . If this class is on the "many" side of the relationship (e.g., a department can have many employees), the method writes code which when executed will update the foreign key for the related class to point to the primary key of the object instance being created (Step FN) .
If the relationship is many-to-many (Step FP) , the method generates code that when executed sends a database insert command to create a new row in the join table which connects the two related classes. This row will contain foreign key pointers to each of the two related instances. For example, if an employee is related to a project through a many-to-many relationship, this relationship will be created by adding a row to the assignment table which "points to" a particular employee and a particular project, thereby joining the two.
After all the semantic elements of the object model are interpreted, the method writes code which when executed will create an object instance of the given class in the object-oriented application (Step FQ) . For example, in the C++ language, an instance is created which has all the attributes defined in the object model, which has pointers or arrays to represent its relationships and which uses built-in
language constructs to represent inheritance. Also, the method writes code that when executed will send an insert command or commands to the database to store in the database all the information for this new object instance (Step FR) . These database commands insert rows into the database that correspond to the attribute values of the new object instance and its parent instances. Further, these commands update rows in the database tables associated with related object instances to reflect the relationships between the new instance and the related instances.
The code to create the new object instance (which was generated in Step FQ) and the code to make the associated changes to the database (which was generated in step FR) are combined in a single routine. This routine, which is a routine to create an object instance of this class, is made available for further processing (Step FS) . When executed, this routine will take as inputs the attributes of the object instance to be created, the attributes of the ancestor instances to be inherited by the new object instance, and the related instances to which the new object instance will be associated. Its output will be a new object structure in the application consisting of the new object instance and its relationships and inheritanc.es with other instances, and a corresponding data structure in the database. A benefit of this routine is that it creates the database structure transparently. The developer has only to call the routine in the object-oriented application; the corresponding data structure in the database is created automatically.
6.2 Steps to generate a routine to retrieve an object instance
The flow chart of Fig. 6 expands on Step G of Fig. 3 to give additional detail. It illustrates the steps to generate a retrieve routine for a particular object class (Step GA) .
The method performs a loop for each object model semantic element relevant to this class (Step GB) . To find these elements the method scans the entire object model and
extracts semantics that define the attributes, inheritances, and relationships for this class.
Depending on the kind of semantic found (Step GC) , the method generates code to reflect the implications of that semantic in the retrieve routine. For an object model semantic that defines an attribute of the class (step GD) , the method performs steps that depend on the kind of attribute. If the attribute is defined as being part of the object ID (step GG) , the method writes code that when executed adds that attribute to the query selector clause. The selector clause will be used to retrieve the row from a database table whose primary key columns match the attribute values in the selector clause. If the object model indicates that the primary key attribute has been generated by the method (Step GH) , the method writes code that when executed will add that attribute value to the query selector clause. For all other attribute types (Step Gl) , the attribute name is added to the query return clause (see below) .
For an object model semantic specifying that this object class inherits from a parent class, the method determines the type of inheritance (Step GE) . If the inheritance is vertical (Step GJ) , the method writes code which when executed will call the retrieve routine for a parent instance and pass that routine its required inputs. If the inheritance is horizontal (Step GK) , the method adds the parent class attributes to the database query return clause for this (child) class.
For an object model semantic that specifies a relationship between this object class and another object class, the method determines the type of relationship (Step GF) . If the relationship is one-to-one, the method uses the transform 50 to determine which database table contains the foreign key information for this relationship. The method then writes code that when executed queries the related table based on the primary-foreign key relationship between the two tables.
If the relationship is one-to-many (Step GM) , the method determines which "side" of the relationship this object
class is on—that is, whether this object class is on the "1" side or the "many" side of the relationship. If this class is on the "1" side of a one-to-many relationship, the method generates code which when executed sends a database query to the related table using the foreign key attributes for this instance (Step GO) . For example, if an employee object instance "John" is related to a department object instance "Engineering," the employee will contain a foreign key attribute, "Engineering," which "points to" John's department. To generate code to retrieve the department related to "John," the method writes code which when executed will select the department named "Engineering" from the department table in the database. If the object class is on the "many" side of the relationship, the method writes code which when executed will send a query to the database to access the related database table using the primary key of this class (Step GN) . For example, to generate code to retrieve the employees related to the "Engineering" department, the method writes code which when executed will select all employees with the foreign key "Engineering" from the employee table in the database.
If the relationship is many-to-many (Step GP) , the method generates code that when executed sends a database query command to the join table which connects the two related classes with the primary key of this object instance as the selector. For each row returned by this query, the method writes code which when executed sends a query to the related table using the join table foreign key as a selector. For example, if an employee, "John," is related to a project, "Vacation Policy," through a many-to-many relationship, the first step will be to query the join table, "Assignments," for all assignments which "point to" John through their foreign key. For each row returned from this query, a second query can be issued to obtain the project related to that join table row through the foreign key relationship. In this example the assignment table would contain a row pointing to both "John" and "Vacation Policy."
After all the semantic elements of the object model are interpreted, the method writes code that when executed will send a query command or commands to the database to retrieve from the database all the information for a particular object instance (Step GQ) . These query commands will retrieve rows in the database that correspond to the primary key values of the object instance being retrieved or the foreign key values for the appropriate object instances. The method also writes code which when executed will format the rows returned from the database into object instances in the object-oriented application (Step GR) . For example, in the C++ language, an object instance is created based on data retrieved from the database. This object instance contains all the attributes defined in the object model, has pointers or arrays to its related object instances, and uses built-in language constructs to represent its inheritances.
The code to retrieve object instance information from the database (which was generated in Step GQ) and the code to create the retrieved object instance information from the database (which was generated in Step GR) are combined in a single routine. This routine is made available for further processing (Step GS) . When executed, this routine will take as inputs the primary key attributes for the object instance to be retrieved. Its output will be a new object structure in the application consisting of the retrieved object instance (that is, the object instance formed from the results of the database query) and its relationships and inheritances with other object instances. Put another way, whereas the create routine described above with reference to Fig. 5 creates an object instance for which no corresponding data is yet present in the database, the retrieve routine described here with reference to Fig. 6 creates an object instance for which corresponding data is already present in the database.
6.3 Steps for generating a routine to update an object instance
The flow chart of Fig. 7 expands on Step H of Fig. 3 to give additional detail. It illustrates the steps to
generate an update routine for a particular object class (Step HA) .
The method performs a loop for each relevant object model semantic element for this class (Step HB) . To find these elements the method scans the entire object model and extracts semantics that define the attributes, inheritances, and relationships for this class.
Depending on the kind of semantic found (Step HC) , the method generates code to reflect the implications of that semantic in the update routine. For an object model semantic that defines an attribute of the class (step HD) , the method performs steps that depend on the kind of attribute. If the attribute is defined as being part of the object ID (step HG) , the method writes code that when executed adds that attribute to the update selector clause. The selector clause will be used to update the row from a database table whose primary key columns match the attribute values in the selector clause. If the object model indicates that the object ID attribute has been generated by the method (Step HH) , the method writes code that when executed will add that attribute value to the update selector clause. For all other attribute types (Step HI) , the changed attribute name and new value are added to the update command.
For an object model semantic that specifies that this object class inherits from a parent class, the method determines the type of inheritance (Step HE) . If the inheritance is vertical (Step HJ) , the method writes code which when executed will call the update routine for a parent instance and pass that routine its required inputs. If the inheritance is horizontal (Step HK) , the method adds the changed parent class attributes to the database update command for this (child) class.
For an object model semantic that specifies a relationship between this object class and another object class, the method writes code which when executed checks the referential integrity constraints for this relationship (Step HF) . That is, it must be ensured that foreign key references in the database remain valid after the update.
Thereafter the method determines the type of relationship (Step HL) . If the relationship is one-to-one, the method uses the transform 50 to determine which database table contains the foreign key information for this relationship. The method then writes code that when executed updates the related table based on the primary-foreign key relationship between the two tables (Step HM) .
If the relationship is one-to-many, the method determines the "side" of the relationship upon which this object class is, i.e., whether this object class is on the "1" side or the "many" side of the relationship (Step HN) . If this class is on the "1" side of a one-to-many relationship, the method generates code which when executed adds primary key attributes for the related instance to the database update command for this instance (Step HP) . If the object class is on the "many" side of the relationship, the method writes code which when executed will send an update to the database to set the foreign key attributes in the related table to the primary key for the object instance given as input to the update routine (Step HO) .
If the relationship is many-to-many (Step HQ) , the method generates code that when executed sends a database update command to the join table which connects the two related classes with the primary key of the object instance given as input to the update routine as the update selector.
In other words, the join table will be updated to "point to" a new related object.
After all the semantic elements of the object model are interpreted, the method writes code that when executed will send an update command or commands to the database to store in the database all the information for the object instance given as input to the update routine (Step HR) . These update commands alter rows in the database that correspond to the primary key values of the object instance being updated or the foreign key values for the relationships for the object instance being updated. The method also writes code which when executed will update the application object structure, to reflect the changes made to the database (Step
HS) . For example, if the database update fails, the object instance will not be changed in the object-oriented application. The method ensures that at all times the information in the database properly reflects the information in the object-oriented application.
The code to update the database (which was generated in step HR) and the code to reflect the database changes in the object-oriented application (which was generated in Step HS) are combined into a routine to update an object instance, which is made available for further processing (Step HT) . When executed, this routine will take as inputs the object instance to be updated and the changes to be made. Its output will be an updated object structure in the application consisting of the updated object instance and its updated relationships and inheritances with other object instances, and corresponding changes in the database. A benefit of this routine is that changes to the database are made transparently based on changes to the object instance.
6.4 Steps to generate a routine to delete an object instance
The flow chart of Fig. 8 expands on Step J of Fig. 3 to give additional detail. It illustrates the steps to generate a delete routine for a particular object class (Step JA) .
The method performs a loop for each relevant object model semantic element for this class (Step JB) . To find these elements the method scans the entire object model and extracts semantics that define the attributes, inheritances, and relationships for this class.
Depending on the kind of semantic found (Step JC) , the method generates code to reflect the implications of that semantic in the delete routine. For an object model semantic that defines an attribute of the class (step JD) , the method performs steps that depend on the kind of attribute. If the attribute is defined as being part of the object ID (step JG) , the method writes code that when executed adds that attribute to the delete selector clause. The selector clause will be used to delete the row from a database table whose primary key
columns match the attribute values in the selector clause. If • the object model indicates that the object ID attribute has been generated by the method (Step JH) , the method writes code that when executed will add that attribute value to the delete selector clause.
For an object model semantic specifying that this object class inherits from a parent class, the method determines the type of inheritance (Step JE) . If the inheritance is vertical (Step Jl) , the method writes code which when executed will call the delete routine for a parent instance and pass that routine its required inputs. (In the case of horizontal inheritance, the database information associated with the parent instance will be automatically deleted when the child instance is deleted.) For an object model semantic that specifies a relationship between this object class and another object class, the method writes code that when executed retrieves all the object instances related to the object instance to be deleted (Step JF) . Next, the method determines the proper delete action for the relationship (Step JJ) . If the delete action specified by the object model is "block" (Step JK) , the delete routine will be cancelled if there are any object instances related through this relationship. For example, if there any employees related to a particular department, an attempt to delete that department would fail if the delete action for the relationship is block. If the delete action is "propagate" (Step JL) , the delete routine is called for each related instance. For example, if the delete action is Propagate, an attempt to delete a department would also delete all the employees in that department. If the delete action is "remove" (Step JM) , the relationship pointer for each related object instance will be set to null, or the relationship information will be deleted from the join table. For example, if the delete action is Remove, an attempt to delete a department would succeed and would remove the relationship pointer between each employee and that department.
After all the semantic elements of the object model are interpreted, the method writes code that when executed
will send a delete command or commands to the database to delete from the database all the information for a particular object instance (Step JN) . These delete commands remove rows in the database that correspond to the primary key values of the object instance being deleted and update or delete rows that correspond to foreign key values for the object instance to which the deleted object is related. Once this information has been deleted from the database, the method writes code which when executed will update the object instances in the object-oriented application appropriately (Step JO) . In particular, the changes may not succeed (e.g. , if blocked) or may propagate to other object instances causing widespread changes to object instances in the object-oriented application. The code to modify the database (which was generated in step JN) and the code to reflect the database changes in the object-oriented application (which was generated in step JO) are combined into a routine to delete an object instance, which is made available for further processing (Step JP) . When executed, this routine will take as input the object instance to be deleted. Its output will be an updated object structure in the application and corresponding changes in the database. A benefit of this routine is that changes to the database are made transparently based on the deletion of an object instance.
7. Conclusion
The invention provides a method and apparatus for using an object model of an object-oriented application to automatically map information between an object-oriented application and a structured database, such as a relational database. The invention uses an object model to impose semantics on the object classes of an object-oriented application and on the data from a structured database, such that operations on the object classes are automatically and transparently reflected in the database. The object classes of the object model provide a much more powerful representation of the real world than is provided by the
structured database, in particular because they encapsulate notions of inheritance and relationships. What the user sees is simply an object-oriented system, with no explicit reference whatsoever to the structured database. The method can be used also with two or more different databases, with the object model transparently integrating them. The invention can be used where a site or a company has a plurality of incompatible, pre-existing databases (legacy databases) that need to be integrated in a single application. The update routines that the invention generates for each object class change all databases transparently, so that the user or programmer sees only the objects and not the databases.
Furthermore, the invention allows significant flexibility in customizing the generated routines. For example, each routine generated according to the method can optionally call an externally generated (e.g., by a programmer) "notification hook" routine just before or just after the generated routine performs its operations. In this notification hook routine, custom source code can be added to perform additional operations and thereby modify the behavior of the object class. For example, a notification hook routine called just before performing the create routine for the tire class object can assign a serial number to the tire instance being created.
Significant flexibility is also allowed in the choice of database used by the invention. The invention shields the user or programmer from any knowledge of the underlying database or databases. That is, the routines generated according to the method are identical, regardless of the underlying database. Thus a user can switch databases by changing only a run-time object management library, without having to make any other changes to the object-oriented application. Still further variations and extensions will be apparent to those of skill in the art within the scope of the invention.
The invention has been explained with reference to specific embodiments. Other embodiments are contemplated without departing from the spirit and scope of the invention. For example, the invention can be used not only with relational data, but also any field-delimited data, such as spreadsheet databases, hierarchical databases or flat file databases which are field delimited. It is therefore not intended that this invention be limited, except as indicated by the appended claims.
Claims
1. A method for automatically mapping information between an object-oriented application and a structured database, said method being carried out using a digital computing system comprising a processor, said method comprising the steps of: using said processor to accept an object model, said object model being a formal description of said object- oriented application; using said processor to automatically generate code, said code being suitable for conversion to an executable form that when executed automatically maps said information between said object-oriented application and said structured database; and using said processor to output said code.
2. A method for automatically mapping information between an object-oriented application and a structured database, said method being carried out using a digital computing system comprising a processor, said method comprising the steps of: using said processor to accept an object model, said object model being a formal description of said object- oriented application; using said processor to make available for processing a database schema that represents the structure of data in said structured database; using said processor to make available for processing a transform that represents a mapping between said object model and said database schema; using said processor to automatically generate code, said code being suitable for conversion to an executable form that when executed automatically maps said information between said object-oriented application and said structured database; and using said processor to output said code.
3. The method of claim 2 wherein said step of using said processor to make available for processing a database schema comprises using said processor to accept said database schema, and wherein said step of using said processor to make available for processing a transform comprises using said processor to accept said transform.
4. The method of claim 2 wherein said computing system further comprises an input means coupled to said processor, wherein said step of using the processor to make available for processing a database schema comprises using said processor in conjunction with said input means to input said database schema, and wherein said step of using said processor to make available for processing a transform comprises using said processor in conjunction with said input means to input said transform.
5. The method of claim 2 wherein said step of using the processor to make available for processing a database schema comprises using said processor to construct said database schema, and wherein said step of using the processor to make available for processing a transform comprises using said processor to construct said transform.
6. The method of claim 2 wherein said step of using said processor to automatically generate code includes using said processor to automatically generate said code comprising object classes containing routines according to said object model, said database schema, and said transform.
7. The method of claim 2 wherein said step of using said processor to automatically generate code includes using said processor to interpret semantic elements in said object model.
8. The method of claim 2 wherein said step of using said processor to accept an object model comprises using said processor to accept an object model comprising semantic elements including attributes of object classes including object ID attributes, relationships between object classes, and inheritances between object classes; wherein said step of using said processor to make available for processing a database schema includes using said processor to make available for processing a database schema that describes tables organized in rows and columns, each one of said tables having at least one primary key column that uniquely identifies rows in said table, and optionally at least one foreign key column that represents a mapping between a row in said table and a row in another table of said structured database; and wherein said step of using said processor to make available for processing a transform includes using said processor to make available for processing a transform that comprises a set of mappings between said semantic elements of said object model and said database schema.
9. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate each one of said object classes from the object model with at least one table described by said database schema, according to said mappings of said transform.
10. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate said object ID attributes from said object model with primary key columns in at least one table described by said database schema, according to said mappings of said transform.
11. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate attributes from said object model with columns in a single table described by said database schema, according to said mappings of said " transform.
12. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate a one-to-one relationship between object classes of said object model with at least one foreign key column in at least one table described by said database schema, according to said mappings of said transform.
13. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate a one-to-many relationship between object classes of said object model with at least one foreign key column in at least one table of said database schema, according to said mappings of said transform.
14. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate a many-to-many relationship between object classes of said object model with a join table described by said database schema, said join table for containing foreign key references to primary key columns corresponding to related object classes of said object model, according to said mappings of said transform.
15. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to associate a vertical inheritance between a child object class and a parent object class of said object model with at least one foreign key column in a table described by said database schema that corresponds to said child object class, according to said mappings of said transform.
16. The method of claim 8 wherein said step of using said processor to automatically generate code further comprises using said processor to represent a horizontal inheritance between a child object class and a parent object class of said object model by copying attributes of said parent object class into a table described by said database schema corresponding to said child object class according to said mappings of said transform.
17. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said routines being suited to manipulate an instance of said object class.
18. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for creating object instances of said object class.
19. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for retrieving object instances of said object class.
20. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for updating object instances of said object class.
21. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for deleting object instances of said object class.
22. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for creating an object instance of said object class, said routine for creating an object instance of said object class being suitable for conversion to an executable form that when executed causes a new object instance to be created in said object-oriented application and further causes corresponding structured information to be added to said structured database, said structured information reflecting said new object instance.
23. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for retrieving an object instance of said object class, said routine for retrieving an object instance being suitable for conversion to an executable form that when executed causes a new object instance to be created in said object-oriented application, said new object instance having attribute values, relationships, and inheritances determined according to corresponding information in said structured database.
24. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for updating an object instance of said object class, said routine for updating an object instance being suitable for conversion to an executable form that when executed causes modifications to certain structured information in said structured database and further causes the attribute values, inheritances, and relationships of an object instance in said object-oriented application to be modified to reflect said modifications to said certain structured information in said structured database.
25. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for a plurality of object classes determined by said object model and a set of routines for each object class of said plurality, said set comprising a routine for deleting an object instance of said object class, said routine for deleting an object instance being suitable for conversion to an executable form that when executed causes an object instance to be deleted in said object-oriented application and further causes corresponding structured information to be modified in said structured database.
26. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate a create routine for each object class in a plurality of object classes determined by said object model, said create routine comprising the step of generating a unique object ID.
27. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate a delete routine for each object class in a plurality of object classes determined by said object model, said delete routine comprising the step of blocking the deletion of an object instance based on the existence of a relationship between said object instance and another object instance.
28. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate a delete routine for each object class in a plurality of object classes determined by said object model, said delete routine comprising the step of propagating the deletion of a first object instance to a second object instance based on the relationship between said first object instance and said second object instance.
29. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate a delete routine for each object class in a plurality of object classes determined by said object model, said delete routine comprising the step of removing a relationship between a first object instance and a second object instance.
30. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for object classes and routines according to said object model, said database schema, and said transform, at least one routine of said generated routines calling a notification hook routine in connection with the execution of said at least one routine of said generated routines, said notification hook routine being externally generated.
31. The method of claim 2 wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate code for object classes and routines according to said object model, said database schema, and said transform, including a routine to create at least one table in said structured database that corresponds to an object class in said object model.
32. The method of claim 2 wherein said structured database is a field-delimited database, and wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate source code that is suitable for conversion to an executable form which when executed automatically maps said information between said object-oriented application and said field- delimited database.
33. The method of claim 2 wherein said structured database is a relational database comprising relational data and wherein said step of using said processor to automatically generate code comprises using said processor to automatically generate source code that is suitable for conversion to an executable form which when executed automatically maps said information between said object-oriented application and said relational database.
34. A method for automatically mapping information between an object-oriented application and a plurality of structured databases, said method being carried out using a digital computing system comprising at least one processor, said method comprising the steps of: using a processor of said digital computing system to accept an object model, said object model being a formal description of said object-oriented application; using said processor to automatically generate code, said code being suitable for conversion to an executable form that when executed automatically maps said information between said object-oriented application and the structured databases of said plurality; and using said processor to output said code.
35. The method of claim 34 wherein said step of using said processor to automatically generate code further comprises using said processor to interpret object classes and to associate each one of said object classes with at least one table in at least one structured database of said structured databases.
36. A method for automatically generating code to support an object-oriented application that interacts transparently with a field-delimited database, said method performed by a processor coupled to an input means and an output means, said method comprising the steps of: (a) using said processor and said input means to accept an object model, said object model being a formal description of said object-oriented application, said object model comprising at least one object class and semantics including attributes, relationships, and inheritances associated with each object class;
(b) using said processor to obtain a database schema;
(c) using said processor to obtain a transform, said transform representing a mapping between said object model and said schema;
(d) for each object class in said object model, using said processor to generate code for each object class, including code for four routines associated with said object class, said four routines being: a routine to create an instance of said object class; a routine to retrieve an instance of said object class; a routine to update an instance of said object class; and a routine to delete an instance of said object class, each of said four routines taking into account said semantics of said object model; and using said processor and said output means to output the code thus generated.
37. An apparatus for automatically mapping information between an object-oriented application and a structured database, said apparatus comprising a digital computing system further comprising a processor, a memory coupled to said processor, a user interface coupled to said first processor, a storage device coupled to said processor, a network coupled to said processor, a database processor coupled to said network and supporting said structured database, and: means associated with said processor for accepting an object model, said object model being a formal description of said object-oriented application; means associated with said processor for automatically generating code that when executed automatically maps said information between said object-oriented application and said structured database; and means associated with said processor for outputting said code.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US9532293A | 1993-07-21 | 1993-07-21 | |
US08/095,322 | 1993-07-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1995003586A1 true WO1995003586A1 (en) | 1995-02-02 |
Family
ID=22251387
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1994/007890 WO1995003586A1 (en) | 1993-07-21 | 1994-07-14 | Method and apparatus for generation of code for mapping relational data to objects |
Country Status (2)
Country | Link |
---|---|
US (1) | US5499371A (en) |
WO (1) | WO1995003586A1 (en) |
Cited By (33)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
AT1104U1 (en) * | 1995-09-26 | 1996-10-25 | Siemens Ag Oesterreich | METHOD FOR STORING PERSISTED OBJECTS OF OBJECT-ORIENTED USER PROGRAMS IN A RELATIONAL DATABASE |
WO1996034350A1 (en) * | 1995-04-24 | 1996-10-31 | Aspect Development, Inc. | Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon |
WO1996041282A1 (en) * | 1995-06-07 | 1996-12-19 | Wall Data Incorporated | Computer system for creating semantic object models from existing relational database schemas |
WO1997007470A1 (en) * | 1995-08-17 | 1997-02-27 | Wall Data Incorporated | Method and apparatus for storing and retrieving data in a relational database using an object model |
FR2738649A1 (en) * | 1995-09-13 | 1997-03-14 | Hewlett Packard Co | METHOD FOR CONVERTING OBJECTS FROM A FLAT SPACE TO A CLASS STRUCTURED SPACE |
US5809297A (en) * | 1993-10-29 | 1998-09-15 | Wall Data Incorporated | Semantic object modeling system for creating relational database schemas |
WO1999009494A1 (en) * | 1997-08-14 | 1999-02-25 | Aoraki Corporation Limited | Relational database coexistence in object oriented environments |
WO1999027447A1 (en) * | 1997-11-20 | 1999-06-03 | Crosskeys Systems Corporation | Knowledge module |
WO1999033002A1 (en) * | 1997-12-22 | 1999-07-01 | Tony Chun Tung Ng | Method and apparatus for creating indexes in a relational database corresponding to classes in an object-oriented application |
EP1012740A4 (en) * | 1996-03-26 | 2000-06-28 | Bull Hn Information Syst | Method of integrating schemas of distributed heterogeneous databases |
GB2347243A (en) * | 1998-12-31 | 2000-08-30 | Ibm | Operations on a relational database upon completion of a transaction by an object-oriented system |
US6175837B1 (en) | 1998-06-29 | 2001-01-16 | Sun Microsystems, Inc. | Object-relational mapping toll that processes views |
US6240413B1 (en) | 1997-12-22 | 2001-05-29 | Sun Microsystems, Inc. | Fine-grained consistency mechanism for optimistic concurrency control using lock groups |
US6243709B1 (en) | 1998-06-29 | 2001-06-05 | Sun Microsystems, Inc. | Method and apparatus for loading stored procedures in a database corresponding to object-oriented data dependencies |
US6268850B1 (en) | 1997-12-22 | 2001-07-31 | Sun Microsystems, Inc. | User interface for the specification of lock groups |
US6279008B1 (en) | 1998-06-29 | 2001-08-21 | Sun Microsystems, Inc. | Integrated graphical user interface method and apparatus for mapping between objects and databases |
US6385618B1 (en) | 1997-12-22 | 2002-05-07 | Sun Microsystems, Inc. | Integrating both modifications to an object model and modifications to a database into source code by an object-relational mapping tool |
US6591275B1 (en) | 2000-06-02 | 2003-07-08 | Sun Microsystems, Inc. | Object-relational mapping for tables without primary keys |
US7076490B2 (en) * | 2001-10-13 | 2006-07-11 | Electronics And Telecommunications Research Institute | Object-relational database management system and method for deleting class instance for the same |
CN1821957A (en) * | 2005-02-18 | 2006-08-23 | 微软公司 | Relationship modeling |
WO2006108753A1 (en) * | 2005-04-14 | 2006-10-19 | International Business Machines Corporation | Relational query of a hierarchical database |
US20110047175A1 (en) * | 2004-04-21 | 2011-02-24 | Kong Eng Cheng | Querying Target Databases Using Reference Database Records |
WO2011038770A1 (en) * | 2009-10-01 | 2011-04-07 | Starcounter Ab | Systems and methods for managing databases |
US8266125B2 (en) | 2009-10-01 | 2012-09-11 | Starcounter Ab | Systems and methods for managing databases |
WO2014153377A1 (en) * | 2013-03-20 | 2014-09-25 | Microsoft Corporation | Extensible and queryable strong types |
US9038177B1 (en) | 2010-11-30 | 2015-05-19 | Jpmorgan Chase Bank, N.A. | Method and system for implementing multi-level data fusion |
US9292588B1 (en) | 2011-07-20 | 2016-03-22 | Jpmorgan Chase Bank, N.A. | Safe storing data for disaster recovery |
US10248668B2 (en) * | 2016-07-18 | 2019-04-02 | International Business Machines Corporation | Mapping database structure to software |
US10467688B1 (en) | 1999-02-09 | 2019-11-05 | Jpmorgan Chase Bank, N.A. | System and method for back office processing of banking transactions using electronic files |
US10540373B1 (en) | 2013-03-04 | 2020-01-21 | Jpmorgan Chase Bank, N.A. | Clause library manager |
CN111026777A (en) * | 2019-12-13 | 2020-04-17 | 中国南方电网有限责任公司 | Entity class code generation method and device, computer equipment and storage medium |
US10885157B2 (en) | 2017-04-03 | 2021-01-05 | International Business Machines Corporation | Determining a database signature |
US11163616B2 (en) | 2017-03-07 | 2021-11-02 | Polyjuice Ab | Systems and methods for enabling interoperation of independent software applications |
Families Citing this family (424)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6070006A (en) * | 1993-04-14 | 2000-05-30 | Kabushiki Kaisha Toshiba | Object oriented software development tool for creation of new class(es) |
JPH06332712A (en) * | 1993-05-25 | 1994-12-02 | Fujitsu Ltd | Data processing system having object |
FR2712101B1 (en) * | 1993-11-05 | 1996-01-05 | Socs Holding | System for controlling a relational database according to an object-oriented access logic limiting the number of accesses to the database, and corresponding method. |
US5764973A (en) * | 1994-02-08 | 1998-06-09 | Enterworks.Com, Inc. | System for generating structured query language statements and integrating legacy systems |
JPH07319917A (en) * | 1994-05-24 | 1995-12-08 | Fuji Xerox Co Ltd | Document data base managing device and document data base system |
FR2721728B1 (en) * | 1994-06-28 | 1996-07-26 | Bull Sa | Method and device for automatically generating spreadsheets. |
US5737736A (en) * | 1994-07-29 | 1998-04-07 | Oracle Corporation | Method and apparatus for storing objects using a c-structure and a bind descriptor |
DE59409041D1 (en) * | 1994-08-04 | 2000-02-03 | Landis & Gyr Tech Innovat | Data arrangement for a device that can be connected to a communication network and method for generating the data arrangement |
JP3310116B2 (en) * | 1994-08-31 | 2002-07-29 | 株式会社東芝 | Knowledge base system |
US5694598A (en) * | 1994-10-12 | 1997-12-02 | U S West Technologies, Inc. | Method for mapping data between a relational format and an object-oriented format |
US5809296A (en) * | 1994-11-29 | 1998-09-15 | St Computer Systems & Services Ltd. | Method and structure for clustering database tables into classes and presenting each class as an E-R model |
US6704744B1 (en) * | 1994-12-07 | 2004-03-09 | Next Computer, Inc. | Method and apparatus for mapping objects to multiple tables of a database |
US5873093A (en) * | 1994-12-07 | 1999-02-16 | Next Software, Inc. | Method and apparatus for mapping objects to a data source |
US5799309A (en) * | 1994-12-29 | 1998-08-25 | International Business Machines Corporation | Generating an optimized set of relational queries fetching data in an object-relational database |
US5893108A (en) * | 1994-12-29 | 1999-04-06 | International Business Machines Corporation | System, method, and computer program product for efficiently translating relational tuples to object-oriented objects |
GB9504217D0 (en) * | 1995-03-02 | 1995-04-19 | Sumitomo Rubber Ind | A method of determining the inflation pressure of a tyre on a moving vehicle |
US5680619A (en) * | 1995-04-03 | 1997-10-21 | Mfactory, Inc. | Hierarchical encapsulation of instantiated objects in a multimedia authoring system |
US6078925A (en) * | 1995-05-01 | 2000-06-20 | International Business Machines Corporation | Computer program product for database relational extenders |
US6678880B1 (en) * | 1995-05-08 | 2004-01-13 | Apple Computer, Inc. | System for iteratively designing an object heterarchy in an object-oriented computing environment |
US6240451B1 (en) * | 1995-05-25 | 2001-05-29 | Punch Networks Corporation | Method and apparatus for automatically disseminating information over a network |
US5694596A (en) | 1995-05-25 | 1997-12-02 | Kangaroo, Inc. | On-line database updating network system and method |
US5640558A (en) * | 1995-05-31 | 1997-06-17 | International Business Machines Corporation | Identifying and analyzing multiple level class relationships in an object oriented system by parsing source code without compilation |
US5829006A (en) * | 1995-06-06 | 1998-10-27 | International Business Machines Corporation | System and method for efficient relational query generation and tuple-to-object translation in an object-relational gateway supporting class inheritance |
US5717924A (en) * | 1995-07-07 | 1998-02-10 | Wall Data Incorporated | Method and apparatus for modifying existing relational database schemas to reflect changes made in a corresponding object model |
FI103155B1 (en) * | 1995-10-11 | 1999-04-30 | Nokia Telecommunications Oy | Procedure for providing computer controlled service |
US5873092A (en) * | 1995-12-14 | 1999-02-16 | International Business Machines Corporation | Information handling system, method, and article of manufacture including persistent, distributed object name services including shared properties |
US5809506A (en) * | 1996-01-22 | 1998-09-15 | International Business Machines Corporation | Method for creating an object base of persisent application objects in an object oriented programming environment and apparatus related thereto |
US5819251A (en) * | 1996-02-06 | 1998-10-06 | Oracle Corporation | System and apparatus for storage retrieval and analysis of relational and non-relational data |
US6128771A (en) | 1996-02-09 | 2000-10-03 | Sun Microsystems, Inc. | System and method for automatically modifying database access methods to insert database object handling instructions |
US5797137A (en) * | 1996-03-26 | 1998-08-18 | Golshani; Forouzan | Method for converting a database schema in relational form to a schema in object-oriented form |
US5850631A (en) * | 1996-03-26 | 1998-12-15 | Bull Hn Information Systems Inc. | Method for providing a graphical interface for the specification of relationships between two schemas |
US5907846A (en) * | 1996-06-07 | 1999-05-25 | Electronic Data Systems Corporation | Method and system for accessing relational databases using objects |
US5987512A (en) * | 1996-06-12 | 1999-11-16 | Sun Microsystems, Inc. | Method and apparatus for access to remote gateway servers |
US5809507A (en) * | 1996-07-01 | 1998-09-15 | Sun Microsystems, Inc. | Method and apparatus for storing persistent objects on a distributed object network using a marshaling framework |
US7680879B2 (en) * | 1996-07-18 | 2010-03-16 | Computer Associates Think, Inc. | Method and apparatus for maintaining data integrity across distributed computer systems |
US5787413A (en) * | 1996-07-29 | 1998-07-28 | International Business Machines Corporation | C++ classes for a digital library |
EP0825506B1 (en) | 1996-08-20 | 2013-03-06 | Invensys Systems, Inc. | Methods and apparatus for remote process control |
US6041179A (en) * | 1996-10-03 | 2000-03-21 | International Business Machines Corporation | Object oriented dispatch optimization |
US5765161A (en) * | 1996-10-25 | 1998-06-09 | International Business Machines Corporation | Method for encapsulating data from non-object-oriented datastores as datastore persistent objects |
US5778379A (en) * | 1996-10-25 | 1998-07-07 | International Business Machines Corporation | Query syntax for accessing non-relational, non-object-oriented datastores |
US5761671A (en) * | 1996-10-25 | 1998-06-02 | International Business Machines Corporation | Method for interfacing queryable datestore persistent objects to non-relational, non-object-oriented datastores |
US5737598A (en) * | 1996-10-25 | 1998-04-07 | International Business Machines Corporation | Method for capturing and cataloging specifications for datastore persistent classes |
US5799313A (en) * | 1996-10-25 | 1998-08-25 | International Business Machines Corporation | Framework for object-oriented access to non-object-oriented datastores |
US5765162A (en) * | 1996-10-25 | 1998-06-09 | International Business Machines Corporation | Method for managing queryable datastore persistent objects and queryable datastore collections in an object-oriented environment |
US5809508A (en) * | 1996-10-25 | 1998-09-15 | International Business Machines Corporation | Method for capturing and cataloging datastore characteristics to define datastore persistent objects |
US5737597A (en) * | 1996-10-25 | 1998-04-07 | International Business Machines Corporation | Method for cataloging datastore characteristics and defining and generating datastore persistent objects |
US5781907A (en) * | 1996-10-25 | 1998-07-14 | International Business Machines Corporation | Method for the incremental presentation of non-object-oriented datastores using an object-oriented queryable datastore collection |
US5764979A (en) * | 1996-10-25 | 1998-06-09 | International Business Machines Corporation | Method for capturing and cataloging program characteristics for the usage of datastore persistent classes |
US5809509A (en) * | 1996-10-25 | 1998-09-15 | International Business Machines Corporation | Method for using a non-object-oriented datastore as a generic persistent datastore for persistent objects |
US5794247A (en) * | 1996-10-25 | 1998-08-11 | International Business Machines Corporation | Method for representing data from non-relational, non-object-oriented datastores as queryable datastore persistent objects |
US5778358A (en) * | 1996-10-25 | 1998-07-07 | International Business Machines Corporation | Query parser for accessing non-relational, non-object-oriented datastores |
US5787436A (en) * | 1996-10-25 | 1998-07-28 | International Business Machines Corporation | Method for using a datastore cursor for the incremental presentation of query results when traversing implied collections in non-object-oriented datastores |
US5765163A (en) * | 1996-10-25 | 1998-06-09 | International Business Machines Corporation | Method for using queryable persistent identifiers to locate data for datastore persistent objects in non-object-oriented datastores |
US5794248A (en) * | 1996-10-25 | 1998-08-11 | International Business Machines Corporation | Method for representing non-object-oriented datastores using a collection of collections data model |
US5907706A (en) * | 1996-11-12 | 1999-05-25 | International Business Machines Corporation | Interactive modeling agent for an object-oriented system |
US5875285A (en) * | 1996-11-22 | 1999-02-23 | Chang; Hou-Mei Henry | Object-oriented data mining and decision making system |
AU5753298A (en) * | 1996-11-27 | 1998-06-22 | Sony Europa B.V. | Method and system for generating software code |
US6038566A (en) * | 1996-12-04 | 2000-03-14 | Tsai; Daniel E. | Method and apparatus for navigation of relational databases on distributed networks |
US6035342A (en) * | 1997-03-19 | 2000-03-07 | Microsoft Corporation | Method and computer program product for implementing object relationships |
US5857197A (en) * | 1997-03-20 | 1999-01-05 | Thought Inc. | System and method for accessing data stores as objects |
GB2324890B (en) | 1997-05-03 | 2002-05-08 | Ibm | Data processing method and apparatus |
US6023578A (en) * | 1997-05-09 | 2000-02-08 | International Business Macines Corporation | Systems, methods and computer program products for generating an object oriented application for an object oriented environment |
US5987247A (en) * | 1997-05-09 | 1999-11-16 | International Business Machines Corporation | Systems, methods and computer program products for building frameworks in an object oriented environment |
US6047284A (en) * | 1997-05-14 | 2000-04-04 | Portal Software, Inc. | Method and apparatus for object oriented storage and retrieval of data from a relational database |
US5937402A (en) * | 1997-06-19 | 1999-08-10 | Ontos, Inc. | System for enabling access to a relational database from an object oriented program |
US5878411A (en) * | 1997-06-27 | 1999-03-02 | International Business Machines Corporation | Dependent object class and subclass mapping to relational data store |
US5937409A (en) * | 1997-07-25 | 1999-08-10 | Oracle Corporation | Integrating relational databases in an object oriented environment |
US6990458B2 (en) * | 1997-08-28 | 2006-01-24 | Csg Systems, Inc. | System and method for computer-aided technician dispatch and communication |
US6144965A (en) * | 1997-09-24 | 2000-11-07 | Sony Corporation | Performing memory management in an object-oriented programming environment |
JPH11126162A (en) * | 1997-10-22 | 1999-05-11 | Sony Corp | Apparatus and method for information processing and recording medium |
US6128622A (en) * | 1997-11-26 | 2000-10-03 | International Business Machines Corporation | IMS web studio taskguide |
US6076090A (en) * | 1997-11-26 | 2000-06-13 | International Business Machines Corporation | Default schema mapping |
US6448981B1 (en) | 1997-12-09 | 2002-09-10 | International Business Machines Corporation | Intermediate user-interface definition method and system |
US6078926A (en) * | 1997-12-18 | 2000-06-20 | Persistence Software, Inc. | Method and apparatus for performing multi-class object fetch in a database management system |
US6205491B1 (en) * | 1997-12-18 | 2001-03-20 | Sun Microsystems, Inc. | Method and apparatus for deferred throwing of exceptions in C++ |
US6360223B1 (en) | 1997-12-22 | 2002-03-19 | Sun Microsystems, Inc. | Rule-based approach to object-relational mapping strategies |
US6182064B1 (en) | 1998-03-06 | 2001-01-30 | International Business Machines Corporation | Method and system for identifying an object located among a number of multiple interconnected computing systems |
US6247019B1 (en) | 1998-03-17 | 2001-06-12 | Prc Public Sector, Inc. | Object-based geographic information system (GIS) |
US6262741B1 (en) | 1998-03-17 | 2001-07-17 | Prc Public Sector, Inc. | Tiling of object-based geographic information system (GIS) |
US6144338A (en) * | 1998-03-17 | 2000-11-07 | Prc Public Sector. Inc. | Predictive drop and load algorithm for an object-based geographical information system |
US6163776A (en) * | 1998-03-23 | 2000-12-19 | Software Tree, Inc. | System and method for exchanging data and commands between an object oriented system and relational system |
US6202069B1 (en) | 1998-04-30 | 2001-03-13 | International Business Machines Corporation | Execution paradigm for accessing hierarchical data using an object framework |
US6128611A (en) * | 1998-04-30 | 2000-10-03 | International Business Machines Corporation | Internet-enabled generic application program for accessing hierarchical data |
US6128619A (en) * | 1998-04-30 | 2000-10-03 | International Business Machines Corporation | Generating an internet application for accessing a hierarchical database |
US6529914B1 (en) | 1998-04-30 | 2003-03-04 | International Business Machines Corporation | Object-oriented programming model for accessing hierarchical databases |
US6360229B2 (en) | 1998-04-30 | 2002-03-19 | International Business Machines Corporation | Generic execution model for isolating applications from underlying databases |
US7152031B1 (en) * | 2000-02-25 | 2006-12-19 | Novell, Inc. | Construction, manipulation, and comparison of a multi-dimensional semantic space |
US6141660A (en) * | 1998-07-16 | 2000-10-31 | International Business Machines Corporation | Command line interface for creating business objects for accessing a hierarchical database |
US6430571B1 (en) | 1998-07-16 | 2002-08-06 | International Business Machines Corporation | Multi-frame output form that facilitates internet search and update in a hierarchical database |
US6305007B1 (en) * | 1998-07-24 | 2001-10-16 | Computer Associates Think, Inc. | Object property meta model emulator for legacy data structures |
US6499036B1 (en) * | 1998-08-12 | 2002-12-24 | Bank Of America Corporation | Method and apparatus for data item movement between disparate sources and hierarchical, object-oriented representation |
US6397203B1 (en) | 1998-09-30 | 2002-05-28 | International Business Machines Corporation | Defining object classes to match corresponding specialized data types in a relational database |
US6742175B1 (en) | 1998-10-13 | 2004-05-25 | Codagen Technologies Corp. | Component-based source code generator |
WO2000026750A1 (en) * | 1998-11-05 | 2000-05-11 | NEUVIS, Inc | Method for controlling access to information |
US6253367B1 (en) | 1998-11-18 | 2001-06-26 | Micrografx, Inc. | Method and system for transforming dynamic content for use on the internet |
EP1208482A1 (en) * | 1998-11-30 | 2002-05-29 | Siebel Systems, Inc. | Client server system with thin client architecture |
US6587856B1 (en) | 1998-12-07 | 2003-07-01 | Oracle International Corporation | Method and system for representing and accessing object-oriented data in a relational database system |
US6748374B1 (en) | 1998-12-07 | 2004-06-08 | Oracle International Corporation | Method for generating a relational database query statement using one or more templates corresponding to search conditions in an expression tree |
US7801913B2 (en) * | 1998-12-07 | 2010-09-21 | Oracle International Corporation | System and method for querying data for implicit hierarchies |
US6857123B1 (en) | 1998-12-18 | 2005-02-15 | International Business Machines Corporation | Method and apparatus for a Meta Data Service in a data processing system |
US6502086B2 (en) | 1999-01-04 | 2002-12-31 | International Business Machines Corporation | Mapping binary objects in extended relational database management systems with relational registry |
DE10003015A1 (en) * | 1999-02-06 | 2000-08-17 | Ibm | Computer-aided method for automatically transforming a process model |
US6598056B1 (en) * | 1999-02-12 | 2003-07-22 | Honeywell International Inc. | Remotely accessible building information system |
US6922708B1 (en) | 1999-02-18 | 2005-07-26 | Oracle International Corporation | File system that supports transactions |
US6341289B1 (en) * | 1999-05-06 | 2002-01-22 | International Business Machines Corporation | Object identity and partitioning for user defined extents |
AU5025600A (en) * | 1999-05-17 | 2000-12-05 | Foxboro Company, The | Process control configuration system with parameterized objects |
US7089530B1 (en) * | 1999-05-17 | 2006-08-08 | Invensys Systems, Inc. | Process control configuration system with connection validation and configuration |
US6788980B1 (en) | 1999-06-11 | 2004-09-07 | Invensys Systems, Inc. | Methods and apparatus for control using control devices that provide a virtual machine environment and that communicate via an IP network |
US6408302B1 (en) * | 1999-06-28 | 2002-06-18 | Davox Corporation | System and method of mapping database fields to a knowledge base using a graphical user interface |
US6418451B1 (en) | 1999-06-29 | 2002-07-09 | Unisys Corporation | Method, apparatus, and computer program product for persisting objects in a relational database |
US7152228B2 (en) | 1999-07-08 | 2006-12-19 | Science Applications International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US6199195B1 (en) * | 1999-07-08 | 2001-03-06 | Science Application International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US8335775B1 (en) | 1999-08-05 | 2012-12-18 | Oracle International Corporation | Versioning in internet file system |
US6470354B1 (en) | 1999-08-05 | 2002-10-22 | International Business Machines Corporation | Implementing persistent object services (POS) on top of a relational database |
US6549916B1 (en) | 1999-08-05 | 2003-04-15 | Oracle Corporation | Event notification system tied to a file system |
US7280995B1 (en) | 1999-08-05 | 2007-10-09 | Oracle International Corporation | On-the-fly format conversion |
JP3871832B2 (en) * | 1999-08-20 | 2007-01-24 | 日本電気株式会社 | Data processing program automatic generation system and method, and computer-readable recording medium |
US6931623B2 (en) * | 1999-08-30 | 2005-08-16 | Touchnet Information Systems, Inc. | Method of accessing data and logic on existing systems through dynamic construction of software components |
US6640238B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Activity component in a presentation services patterns environment |
US6636242B2 (en) | 1999-08-31 | 2003-10-21 | Accenture Llp | View configurer in a presentation services patterns environment |
US6640249B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Presentation services patterns in a netcentric environment |
US6578068B1 (en) | 1999-08-31 | 2003-06-10 | Accenture Llp | Load balancer in environment services patterns |
US6842906B1 (en) | 1999-08-31 | 2005-01-11 | Accenture Llp | System and method for a refreshable proxy pool in a communication services patterns environment |
US6615253B1 (en) | 1999-08-31 | 2003-09-02 | Accenture Llp | Efficient server side data retrieval for execution of client side applications |
US6640244B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Request batcher in a transaction services patterns environment |
US6715145B1 (en) | 1999-08-31 | 2004-03-30 | Accenture Llp | Processing pipeline in a base services pattern environment |
US6742015B1 (en) | 1999-08-31 | 2004-05-25 | Accenture Llp | Base services patterns in a netcentric environment |
US6954220B1 (en) | 1999-08-31 | 2005-10-11 | Accenture Llp | User context component in environment services patterns |
US6571282B1 (en) | 1999-08-31 | 2003-05-27 | Accenture Llp | Block-based communication in a communication services patterns environment |
US6601192B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Assertion component in environment services patterns |
US6549949B1 (en) | 1999-08-31 | 2003-04-15 | Accenture Llp | Fixed format stream in a communication services patterns environment |
US6601234B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
US7289964B1 (en) | 1999-08-31 | 2007-10-30 | Accenture Llp | System and method for transaction services patterns in a netcentric environment |
US7185016B1 (en) * | 2000-09-01 | 2007-02-27 | Cognos Incorporated | Methods and transformations for transforming metadata model |
EP1236100A1 (en) * | 1999-10-05 | 2002-09-04 | Togethersoft Corporation | Method and system for displaying changes of source code |
US7810069B2 (en) * | 1999-10-05 | 2010-10-05 | Borland Software Corporation | Methods and systems for relating data structures and object-oriented elements for distributed computing |
US6430556B1 (en) * | 1999-11-01 | 2002-08-06 | Sun Microsystems, Inc. | System and method for providing a query object development environment |
US6496833B1 (en) * | 1999-11-01 | 2002-12-17 | Sun Microsystems, Inc. | System and method for generating code for query object interfacing |
US6571232B1 (en) * | 1999-11-01 | 2003-05-27 | Sun Microsystems, Inc. | System and method for browsing database schema information |
US6928399B1 (en) | 1999-12-03 | 2005-08-09 | Exxonmobil Upstream Research Company | Method and program for simulating a physical system using object-oriented programming |
US6901578B1 (en) * | 1999-12-06 | 2005-05-31 | International Business Machines Corporation | Data processing activity lifecycle control |
US6754670B1 (en) | 1999-12-17 | 2004-06-22 | International Business Machines Corporation | Mapping relational tables to object oriented classes |
US6973639B2 (en) * | 2000-01-25 | 2005-12-06 | Fujitsu Limited | Automatic program generation technology using data structure resolution unit |
EP1122640A1 (en) * | 2000-01-31 | 2001-08-08 | BRITISH TELECOMMUNICATIONS public limited company | Apparatus for automatically generating source code |
US7096418B1 (en) * | 2000-02-02 | 2006-08-22 | Persistence Software, Inc. | Dynamic web page cache |
US6915298B1 (en) * | 2000-02-09 | 2005-07-05 | International Business Machines Corporation | User-defined relationships for diagramming user-defined database relations |
US6792436B1 (en) | 2000-02-11 | 2004-09-14 | Persistence Software, Inc. | Method for synchronizing multiple software caches in a memory |
US7072896B2 (en) * | 2000-02-16 | 2006-07-04 | Verizon Laboratories Inc. | System and method for automatic loading of an XML document defined by a document-type definition into a relational database including the generation of a relational schema therefor |
US6615223B1 (en) | 2000-02-29 | 2003-09-02 | Oracle International Corporation | Method and system for data replication |
US6901403B1 (en) | 2000-03-02 | 2005-05-31 | Quovadx, Inc. | XML presentation of general-purpose data sources |
US6567816B1 (en) | 2000-03-07 | 2003-05-20 | Paramesh Sampatrai Desai | Method, system, and program for extracting data from database records using dynamic code |
US6681383B1 (en) * | 2000-04-04 | 2004-01-20 | Sosy, Inc. | Automatic software production system |
US7334216B2 (en) * | 2000-04-04 | 2008-02-19 | Sosy, Inc. | Method and apparatus for automatic generation of information system user interfaces |
US6609132B1 (en) | 2000-04-11 | 2003-08-19 | Revelink, Inc. | Object data model for a framework for creation, update and view navigation of data objects and textual annotations of relations between data objects |
US6618732B1 (en) | 2000-04-11 | 2003-09-09 | Revelink, Inc. | Database query handler supporting querying of textual annotations of relations between data objects |
US6618733B1 (en) | 2000-04-11 | 2003-09-09 | Revelink Inc. | View navigation for creation, update and querying of data objects and textual annotations of relations between data objects |
WO2001077904A1 (en) * | 2000-04-11 | 2001-10-18 | Revelink, Inc. | Framework for creation, update, query, and view navigation of data objects and textual annotations of relations between data objects |
US7185005B1 (en) | 2000-05-12 | 2007-02-27 | Oracle International Corporation | Nested transactions in a file system |
US7254584B1 (en) | 2000-05-17 | 2007-08-07 | Aol Llc | Relationship-based inherited attributes system |
US9038108B2 (en) * | 2000-06-28 | 2015-05-19 | Verizon Patent And Licensing Inc. | Method and system for providing end user community functionality for publication and delivery of digital media content |
GB0015896D0 (en) * | 2000-06-28 | 2000-08-23 | Twi Interactive Inc | Multimedia publishing system |
US8126313B2 (en) * | 2000-06-28 | 2012-02-28 | Verizon Business Network Services Inc. | Method and system for providing a personal video recorder utilizing network-based digital media content |
US7286977B1 (en) * | 2000-09-05 | 2007-10-23 | Novell, Inc. | Intentional-stance characterization of a general content stream or repository |
US7653530B2 (en) * | 2000-07-13 | 2010-01-26 | Novell, Inc. | Method and mechanism for the creation, maintenance, and comparison of semantic abstracts |
US7672952B2 (en) * | 2000-07-13 | 2010-03-02 | Novell, Inc. | System and method of semantic correlation of rich content |
JP3983961B2 (en) * | 2000-07-18 | 2007-09-26 | 株式会社東芝 | Directory information management apparatus and computer-readable recording medium recording program |
US20100122312A1 (en) * | 2008-11-07 | 2010-05-13 | Novell, Inc. | Predictive service systems |
US20090234718A1 (en) * | 2000-09-05 | 2009-09-17 | Novell, Inc. | Predictive service systems using emotion detection |
US7406471B1 (en) | 2000-09-28 | 2008-07-29 | Oracle International Corporation | Scalable multi-database event processing system using universal subscriber-specific data and universal global data |
WO2002059793A2 (en) * | 2000-10-31 | 2002-08-01 | Michael Philip Kaufman | System and method for generating automatic user interface for arbitrarily complex or large databases |
US8161081B2 (en) | 2001-03-16 | 2012-04-17 | Michael Philip Kaufman | System and method for generating automatic user interface for arbitrarily complex or large databases |
US7885981B2 (en) * | 2000-10-31 | 2011-02-08 | Michael Philip Kaufman | System and method for generating automatic user interface for arbitrarily complex or large databases |
US20030105732A1 (en) * | 2000-11-17 | 2003-06-05 | Kagalwala Raxit A. | Database schema for structure query language (SQL) server |
DE10058391C2 (en) * | 2000-11-24 | 2003-06-18 | Siemens Ag | Object processing device |
US7058648B1 (en) | 2000-12-01 | 2006-06-06 | Oracle International Corporation | Hierarchy-based secured document repository |
US6611898B1 (en) * | 2000-12-22 | 2003-08-26 | Convergys Customer Management Group, Inc. | Object-oriented cache management system and method |
US6915303B2 (en) | 2001-01-26 | 2005-07-05 | International Business Machines Corporation | Code generator system for digital libraries |
US20020116700A1 (en) * | 2001-02-12 | 2002-08-22 | Clemente Izurieta | Method for linking non-object oriented data models to object oriented data models using a technique to achieve zero-size object mapping |
US6847974B2 (en) | 2001-03-26 | 2005-01-25 | Us Search.Com Inc | Method and apparatus for intelligent data assimilation |
US7370272B2 (en) * | 2001-04-14 | 2008-05-06 | Siebel Systems, Inc. | Data adapter |
US6711579B2 (en) | 2001-04-20 | 2004-03-23 | Sree Ayyanar Spinning And Weaving Mills Limited | Data storage schema independent programming for data retrieval using semantic bridge |
WO2002093430A1 (en) * | 2001-05-14 | 2002-11-21 | Infomove, Inc. | Method and apparatus for implementing a data management system using a metadata specification |
US7146399B2 (en) * | 2001-05-25 | 2006-12-05 | 2006 Trident Company | Run-time architecture for enterprise integration with transformation generation |
US7673282B2 (en) * | 2001-05-25 | 2010-03-02 | International Business Machines Corporation | Enterprise information unification |
US7877421B2 (en) * | 2001-05-25 | 2011-01-25 | International Business Machines Corporation | Method and system for mapping enterprise data assets to a semantic information model |
US20030101170A1 (en) * | 2001-05-25 | 2003-05-29 | Joseph Edelstein | Data query and location through a central ontology model |
US20040093559A1 (en) * | 2001-05-25 | 2004-05-13 | Ruth Amaru | Web client for viewing and interrogating enterprise data semantically |
US7099885B2 (en) * | 2001-05-25 | 2006-08-29 | Unicorn Solutions | Method and system for collaborative ontology modeling |
US8412746B2 (en) * | 2001-05-25 | 2013-04-02 | International Business Machines Corporation | Method and system for federated querying of data sources |
US20030163450A1 (en) * | 2001-05-25 | 2003-08-28 | Joram Borenstein | Brokering semantics between web services |
US20060064666A1 (en) * | 2001-05-25 | 2006-03-23 | Amaru Ruth M | Business rules for configurable metamodels and enterprise impact analysis |
US20050038629A1 (en) * | 2001-05-25 | 2005-02-17 | Ruth Amaru | Pricing of enterprise information resource management systems |
US7043481B2 (en) | 2001-06-01 | 2006-05-09 | Thought, Inc. | System, method and software for creating, maintaining, navigating or manipulating complex data objects and their data relationships |
US20070089151A1 (en) * | 2001-06-27 | 2007-04-19 | Mci, Llc. | Method and system for delivery of digital media experience via common instant communication clients |
US20060236221A1 (en) * | 2001-06-27 | 2006-10-19 | Mci, Llc. | Method and system for providing digital media management using templates and profiles |
US8990214B2 (en) * | 2001-06-27 | 2015-03-24 | Verizon Patent And Licensing Inc. | Method and system for providing distributed editing and storage of digital media over a network |
US8972862B2 (en) | 2001-06-27 | 2015-03-03 | Verizon Patent And Licensing Inc. | Method and system for providing remote digital media ingest with centralized editorial control |
US7970260B2 (en) * | 2001-06-27 | 2011-06-28 | Verizon Business Global Llc | Digital media asset management system and method for supporting multiple users |
US7278143B2 (en) * | 2001-06-28 | 2007-10-02 | Microsoft Corporation | System and related methods for accessing management functionality through a command line utility |
US7020660B2 (en) * | 2001-06-29 | 2006-03-28 | Siemens Medical Solutions Health Services Corp. | Data object generator and method of use |
US7366738B2 (en) * | 2001-08-01 | 2008-04-29 | Oracle International Corporation | Method and system for object cache synchronization |
US7003776B2 (en) * | 2001-08-01 | 2006-02-21 | Oic Acquisition I Corporation | System and method for object persistence life-cycle and object caching integration |
US6907433B2 (en) * | 2001-08-01 | 2005-06-14 | Oracle International Corp. | System and method for managing object to relational one-to-many mapping |
US7054858B2 (en) | 2001-08-01 | 2006-05-30 | Oic Acquisition Corporation | System and method for retrieval of objects from object to relational mappings |
US7089533B2 (en) * | 2001-08-01 | 2006-08-08 | Oic Acquisition I Corp | Method and system for mapping between markup language document and an object model |
US20030026143A1 (en) * | 2001-08-03 | 2003-02-06 | Brennan Declan M. | Method for automating the construction of data stores for storing complex relational and hierarchical data and optimising the access and update of the data therein method for defining look and feel of a user interface obviating the requirement to write programming language code |
US7020659B2 (en) * | 2001-08-15 | 2006-03-28 | Oic Acquistion I Corporation | System and method for managing bi-directional relationships between objects |
US7010779B2 (en) | 2001-08-16 | 2006-03-07 | Knowledge Dynamics, Inc. | Parser, code generator, and data calculation and transformation engine for spreadsheet calculations |
US20020169730A1 (en) * | 2001-08-29 | 2002-11-14 | Emmanuel Lazaridis | Methods for classifying objects and identifying latent classes |
US20030154271A1 (en) * | 2001-10-05 | 2003-08-14 | Baldwin Duane Mark | Storage area network methods and apparatus with centralized management |
US6799182B2 (en) * | 2001-11-13 | 2004-09-28 | Quovadx, Inc. | System and method for data source flattening |
AU2002349765B2 (en) * | 2001-11-19 | 2005-01-20 | Mitsubishi Denki Kabushiki Kaisha | Gateway and gateway setting tool |
US20030103080A1 (en) * | 2001-12-05 | 2003-06-05 | Bahman Radjabi | System and method for developing a code generator for object-oriented communication protocol |
US6769048B2 (en) | 2001-12-06 | 2004-07-27 | Sun Microsystems, Inc. | Cache synchronization method, system and apparatus for a distributed application and an object located in a client cache |
US20030115548A1 (en) * | 2001-12-14 | 2003-06-19 | International Business Machines Corporation | Generating class library to represent messages described in a structured language schema |
US7421436B2 (en) * | 2001-12-21 | 2008-09-02 | International Business Machines Corporation | Decentralized many-to-many relationship management in an object persistence management system |
US7096231B2 (en) * | 2001-12-28 | 2006-08-22 | American Management Systems, Inc. | Export engine which builds relational database directly from object model |
US7062502B1 (en) * | 2001-12-28 | 2006-06-13 | Kesler John N | Automated generation of dynamic data entry user interface for relational database management systems |
US7058655B2 (en) * | 2002-01-11 | 2006-06-06 | Sun Microsystems, Inc. | Determining object graph and object graph projection |
US20030163460A1 (en) * | 2002-01-18 | 2003-08-28 | Matthew Shinn | Systems and methods for dynamic querying |
US20030158944A1 (en) * | 2002-02-19 | 2003-08-21 | International Business Machines Corporation | Software control in a business transaction environment |
US7447675B2 (en) * | 2002-02-21 | 2008-11-04 | Bea Systems, Inc. | Systems and methods for cursored collections |
US8099393B2 (en) | 2002-03-22 | 2012-01-17 | Oracle International Corporation | Transaction in memory object store |
US7076567B1 (en) * | 2002-04-25 | 2006-07-11 | Oracle International Corporation | Simplified application object data synchronization for optimized data storage |
US7606881B2 (en) * | 2002-04-25 | 2009-10-20 | Oracle International Corporation | System and method for synchronization of version annotated objects |
US7548935B2 (en) * | 2002-05-09 | 2009-06-16 | Robert Pecherer | Method of recursive objects for representing hierarchies in relational database systems |
US20030233632A1 (en) * | 2002-06-12 | 2003-12-18 | Lockheed Martin Corporation | Automatically generated client application source code using database table definitions |
US7047259B1 (en) | 2002-06-25 | 2006-05-16 | Oracle International Corporation | Rich cross object navigation in mobile applications |
US20040010498A1 (en) * | 2002-07-10 | 2004-01-15 | Lin Tser Yeng | Object persistence to relational database within run-time environment supporting attributes and reflection |
US8375113B2 (en) * | 2002-07-11 | 2013-02-12 | Oracle International Corporation | Employing wrapper profiles |
US7206851B2 (en) * | 2002-07-11 | 2007-04-17 | Oracle International Corporation | Identifying dynamic groups |
US7512585B2 (en) | 2002-07-11 | 2009-03-31 | Oracle International Corporation | Support for multiple mechanisms for accessing data stores |
US7130856B2 (en) | 2002-07-20 | 2006-10-31 | Microsoft Corporation | Map and data location provider |
US7162469B2 (en) * | 2002-07-20 | 2007-01-09 | Microsoft Corporation | Querying an object for properties |
US7139690B2 (en) * | 2002-07-22 | 2006-11-21 | Microsoft Corporation | Object-level conflict detection in an object-relational database system |
EP1387261A1 (en) * | 2002-07-30 | 2004-02-04 | Sereneo | Application software generation and language for software description |
US20040031017A1 (en) * | 2002-08-12 | 2004-02-12 | Shankar Vaidyanathan | System and method for context-sensitive help in a design environment |
US7787489B2 (en) * | 2002-10-07 | 2010-08-31 | Oracle International Corporation | Mobile data distribution |
US7149752B2 (en) * | 2002-12-03 | 2006-12-12 | Jp Morgan Chase Bank | Method for simplifying databinding in application programs |
US7085759B2 (en) | 2002-12-06 | 2006-08-01 | Jpmorgan Chase Bank | System and method for communicating data to a process |
US7236981B1 (en) * | 2002-12-17 | 2007-06-26 | Oracle International Corporation | Technique for generating code to implement value objects for use with database systems |
US20040133594A1 (en) * | 2003-01-03 | 2004-07-08 | Taiwan Semiconductor Manufacturing Co., Ltd. | Database method and system employing data translation capabilities |
US8032439B2 (en) | 2003-01-07 | 2011-10-04 | Jpmorgan Chase Bank, N.A. | System and method for process scheduling |
US7152072B2 (en) * | 2003-01-08 | 2006-12-19 | Fisher-Rosemount Systems Inc. | Methods and apparatus for importing device data into a database system used in a process plant |
US7401156B2 (en) * | 2003-02-03 | 2008-07-15 | Jp Morgan Chase Bank | Method using control interface to suspend software network environment running on network devices for loading and executing another software network environment |
US20040177339A1 (en) * | 2003-03-07 | 2004-09-09 | Microsoft Corporation | Customization of fields in objects in a computing environment |
US7275024B2 (en) | 2003-03-12 | 2007-09-25 | Microsoft Corporation | Automatic generation of a dimensional model for business analytics from an object model for online transaction processing |
US7546226B1 (en) | 2003-03-12 | 2009-06-09 | Microsoft Corporation | Architecture for automating analytical view of business applications |
US7085752B2 (en) * | 2003-03-12 | 2006-08-01 | Microsoft Corporation | Customization of metadata describing objects in a computing environment |
US7634478B2 (en) * | 2003-12-02 | 2009-12-15 | Microsoft Corporation | Metadata driven intelligent data navigation |
US7313561B2 (en) * | 2003-03-12 | 2007-12-25 | Microsoft Corporation | Model definition schema |
US7379998B2 (en) * | 2003-03-31 | 2008-05-27 | Jp Morgan Chase Bank | System and method for multi-platform queue queries |
US7827524B2 (en) * | 2003-04-22 | 2010-11-02 | Computer Associates Think, Inc. | System and method for integrating object-oriented model profiles and object-oriented programming languages |
US20040230602A1 (en) * | 2003-05-14 | 2004-11-18 | Andrew Doddington | System and method for decoupling data presentation layer and data gathering and storage layer in a distributed data processing system |
US7366722B2 (en) * | 2003-05-15 | 2008-04-29 | Jp Morgan Chase Bank | System and method for specifying application services and distributing them across multiple processors using XML |
US8095659B2 (en) | 2003-05-16 | 2012-01-10 | Jp Morgan Chase Bank | Service interface |
US7739313B2 (en) * | 2003-05-30 | 2010-06-15 | Hewlett-Packard Development Company, L.P. | Method and system for finding conjunctive clusters |
FI115676B (en) * | 2003-07-28 | 2005-06-15 | Nolics Oy | A method for object-oriented processing of relational type information |
US8229932B2 (en) | 2003-09-04 | 2012-07-24 | Oracle International Corporation | Storing XML documents efficiently in an RDBMS |
US8694510B2 (en) * | 2003-09-04 | 2014-04-08 | Oracle International Corporation | Indexing XML documents efficiently |
US7904487B2 (en) * | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
US7882132B2 (en) * | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
US20050144174A1 (en) * | 2003-12-31 | 2005-06-30 | Leonid Pesenson | Framework for providing remote processing of a graphical user interface |
US7698361B2 (en) * | 2003-12-31 | 2010-04-13 | Microsoft Corporation | Lightweight input/output protocol |
US6876314B1 (en) | 2004-02-18 | 2005-04-05 | Robocoder Corporation | Self-generating automatic code generator |
US20050216884A1 (en) * | 2004-03-25 | 2005-09-29 | Microsoft Corporation | Object generation |
US9734222B1 (en) | 2004-04-06 | 2017-08-15 | Jpmorgan Chase Bank, N.A. | Methods and systems for using script files to obtain, format and transport data |
US20050222990A1 (en) * | 2004-04-06 | 2005-10-06 | Milne Kenneth T | Methods and systems for using script files to obtain, format and disseminate database information |
US7930277B2 (en) * | 2004-04-21 | 2011-04-19 | Oracle International Corporation | Cost-based optimizer for an XML data repository within a database |
CA2563354C (en) * | 2004-04-26 | 2010-08-17 | Jp Morgan Chase Bank | System and method for routing messages |
US7653651B1 (en) | 2004-04-29 | 2010-01-26 | Sap Ag | System and method for transparent persistence management |
US7469256B1 (en) | 2004-04-29 | 2008-12-23 | Sap Ag | Cached persistent data management through state tracking |
US7590639B1 (en) | 2004-04-29 | 2009-09-15 | Sap Ag | System and method for ordering a database flush sequence at transaction commit |
US7296028B1 (en) * | 2004-04-30 | 2007-11-13 | Sap Ag | System and method for mapping object-oriented program code to a database layer |
WO2005121840A1 (en) * | 2004-06-07 | 2005-12-22 | Exxonmobil Upstream Research Company | Method for solving implicit reservoir simulation matrix equation |
DE602004022517D1 (en) * | 2004-06-15 | 2009-09-24 | Sap Ag | A data processing system and method for monitoring database replication |
EP1782371A4 (en) * | 2004-06-22 | 2009-12-02 | Coras Inc | Systems and methods for software based on business concepts |
US20070208946A1 (en) * | 2004-07-06 | 2007-09-06 | Oracle International Corporation | High performance secure caching in the mid-tier |
US7392471B1 (en) | 2004-07-28 | 2008-06-24 | Jp Morgan Chase Bank | System and method for comparing extensible markup language (XML) documents |
US8010576B2 (en) * | 2004-08-19 | 2011-08-30 | Oracle International Corporation | Inventory and configuration management |
US7328222B2 (en) * | 2004-08-26 | 2008-02-05 | Oracle International Corporation | Method and apparatus for preserving data coherency in a database by generating a command object that includes instructions for writing a data record to a local cache |
US20060064395A1 (en) * | 2004-09-23 | 2006-03-23 | Seguin Christopher A | Data element storage method |
US7630974B2 (en) | 2004-09-28 | 2009-12-08 | Oracle International Corporation | Multi-language support for enterprise identity and access management |
US20060090155A1 (en) * | 2004-10-12 | 2006-04-27 | Gurevich Michael N | Methods and apparatus for message oriented invocation |
US8416251B2 (en) * | 2004-11-15 | 2013-04-09 | Nvidia Corporation | Stream processing in a video processor |
WO2006058336A2 (en) * | 2004-11-29 | 2006-06-01 | Chevron U.S.A. Inc. | Object oriented fluid flow simulation |
US7627547B2 (en) * | 2004-11-29 | 2009-12-01 | Oracle International Corporation | Processing path-based database operations |
US7921076B2 (en) | 2004-12-15 | 2011-04-05 | Oracle International Corporation | Performing an action in response to a file system event |
US8131766B2 (en) * | 2004-12-15 | 2012-03-06 | Oracle International Corporation | Comprehensive framework to integrate business logic into a repository |
US7363317B2 (en) * | 2005-02-15 | 2008-04-22 | International Business Machines Corporation | Memory efficient XML shredding with partial commit |
US8612468B2 (en) * | 2005-03-02 | 2013-12-17 | Red Hat, Inc. | System and method for retrieving data from a relational database management system |
US7984418B2 (en) * | 2005-03-24 | 2011-07-19 | International Business Machines Corporation | Method and apparatus for situationally aware delivery of object instances to a client |
US7693918B2 (en) * | 2005-03-28 | 2010-04-06 | Microsoft Corporation | Rapid prototyping, generating and dynamically modifying a schema representing a database |
US7958486B2 (en) * | 2005-04-22 | 2011-06-07 | Sap Ag | Methods and systems for data-focused debugging and tracing capabilities |
US20060282458A1 (en) * | 2005-04-22 | 2006-12-14 | Igor Tsyganskiy | Methods and systems for merging business process configurations |
US20060293940A1 (en) * | 2005-04-22 | 2006-12-28 | Igor Tsyganskiy | Methods and systems for applying intelligent filters and identifying life cycle events for data elements during business application debugging |
US20060242196A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing application layer integrity as object oriented programming language elements |
US20060242174A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Systems and methods for using object-oriented tools to debug business applications |
US20060242188A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing a missing collection of application elements as deprecated |
US20060242171A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of using code-based case tools to verify application layer configurations |
US20060241961A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of optimizing legacy application layer control structure using refactoring |
US20060242172A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Systems and methods for transforming logic entities of a business application into an object-oriented model |
US20060242177A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing business application runtime exceptions at design time |
US20060293935A1 (en) * | 2005-04-22 | 2006-12-28 | Igor Tsyganskiy | Methods and systems for incrementally exposing business application errors using an integrated display |
US20060241999A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing a sequence of instructions into an object-oriented programming language |
US20060242176A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of exposing business configuration dependencies |
US7542980B2 (en) | 2005-04-22 | 2009-06-02 | Sap Ag | Methods of comparing and merging business process configurations |
US7702638B2 (en) * | 2005-04-22 | 2010-04-20 | Sap Ag | Systems and methods for off-line modeling a business application |
US8539003B2 (en) * | 2005-04-22 | 2013-09-17 | Sap Ag | Systems and methods for identifying problems of a business application in a customer support system |
US20060242194A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Systems and methods for modeling and manipulating a table-driven business application in an object-oriented environment |
US20060242197A1 (en) * | 2005-04-22 | 2006-10-26 | Igor Tsyganskiy | Methods of transforming application layer structure as objects |
US7720879B2 (en) * | 2005-04-22 | 2010-05-18 | Sap Ag | Methods of using an integrated development environment to configure business applications |
US8223935B2 (en) | 2005-04-30 | 2012-07-17 | Oracle International Corporation | Revenue management systems and methods |
US20070028208A1 (en) * | 2005-06-07 | 2007-02-01 | Alec Maki | Runtime generative programming method and system |
EP1935152A4 (en) | 2005-06-28 | 2010-08-04 | Oracle Int Corp | Revenue management system and method |
CA2616194C (en) * | 2005-07-28 | 2015-02-17 | Oracle International Corporation | Revenue management system and method |
US9401080B2 (en) | 2005-09-07 | 2016-07-26 | Verizon Patent And Licensing Inc. | Method and apparatus for synchronizing video frames |
US20070107012A1 (en) * | 2005-09-07 | 2007-05-10 | Verizon Business Network Services Inc. | Method and apparatus for providing on-demand resource allocation |
US8631226B2 (en) * | 2005-09-07 | 2014-01-14 | Verizon Patent And Licensing Inc. | Method and system for video monitoring |
US9076311B2 (en) * | 2005-09-07 | 2015-07-07 | Verizon Patent And Licensing Inc. | Method and apparatus for providing remote workflow management |
US8073841B2 (en) * | 2005-10-07 | 2011-12-06 | Oracle International Corporation | Optimizing correlated XML extracts |
US8356053B2 (en) | 2005-10-20 | 2013-01-15 | Oracle International Corporation | Managing relationships between resources stored within a repository |
US7499933B1 (en) | 2005-11-12 | 2009-03-03 | Jpmorgan Chase Bank, N.A. | System and method for managing enterprise application configuration |
US8223777B2 (en) | 2005-11-15 | 2012-07-17 | Oracle International Corporation | Gateway for achieving low latency and high availability in a real time event processing system |
US8949455B2 (en) | 2005-11-21 | 2015-02-03 | Oracle International Corporation | Path-caching mechanism to improve performance of path-related operations in a repository |
US7801844B2 (en) * | 2005-11-23 | 2010-09-21 | Microsoft Corporation | Surrogate key generation and utilization |
US7574461B1 (en) * | 2005-12-28 | 2009-08-11 | Emc Corporation | Dividing data for multi-thread backup |
US7693889B1 (en) | 2005-12-28 | 2010-04-06 | Emc Corporation | Automated backup and recovery for content repository |
US7487171B2 (en) * | 2005-12-30 | 2009-02-03 | International Business Machines Corporation | System and method for managing a hierarchy of databases |
US20070179959A1 (en) * | 2006-01-30 | 2007-08-02 | Microsoft Corporation | Automatic discovery of data relationships |
US20070250295A1 (en) * | 2006-03-30 | 2007-10-25 | Subx, Inc. | Multidimensional modeling system and related method |
US20080004993A1 (en) * | 2006-05-08 | 2008-01-03 | Horspool Jason A | System and method for managing physical and logical assets |
US7992203B2 (en) * | 2006-05-24 | 2011-08-02 | Red Hat, Inc. | Methods and systems for secure shared smartcard access |
US7624114B2 (en) * | 2006-06-05 | 2009-11-24 | Microsoft Corporation | Automatically generating web forms from database schema |
US8098829B2 (en) * | 2006-06-06 | 2012-01-17 | Red Hat, Inc. | Methods and systems for secure key delivery |
US7822209B2 (en) * | 2006-06-06 | 2010-10-26 | Red Hat, Inc. | Methods and systems for key recovery for a token |
US8495380B2 (en) | 2006-06-06 | 2013-07-23 | Red Hat, Inc. | Methods and systems for server-side key generation |
US8180741B2 (en) | 2006-06-06 | 2012-05-15 | Red Hat, Inc. | Methods and systems for providing data objects on a token |
US8364952B2 (en) | 2006-06-06 | 2013-01-29 | Red Hat, Inc. | Methods and system for a key recovery plan |
US8332637B2 (en) * | 2006-06-06 | 2012-12-11 | Red Hat, Inc. | Methods and systems for nonce generation in a token |
US9769158B2 (en) | 2006-06-07 | 2017-09-19 | Red Hat, Inc. | Guided enrollment and login for token users |
US8099765B2 (en) | 2006-06-07 | 2012-01-17 | Red Hat, Inc. | Methods and systems for remote password reset using an authentication credential managed by a third party |
US8589695B2 (en) * | 2006-06-07 | 2013-11-19 | Red Hat, Inc. | Methods and systems for entropy collection for server-side key generation |
US8412927B2 (en) * | 2006-06-07 | 2013-04-02 | Red Hat, Inc. | Profile framework for token processing system |
US8707024B2 (en) * | 2006-06-07 | 2014-04-22 | Red Hat, Inc. | Methods and systems for managing identity management security domains |
JP2007328692A (en) * | 2006-06-09 | 2007-12-20 | Canon Inc | Algebra operation method and device therefor, and program |
US7610172B2 (en) * | 2006-06-16 | 2009-10-27 | Jpmorgan Chase Bank, N.A. | Method and system for monitoring non-occurring events |
US7945596B2 (en) | 2006-06-20 | 2011-05-17 | Microsoft Corproation | Programming model for customized data objects |
US8806219B2 (en) | 2006-08-23 | 2014-08-12 | Red Hat, Inc. | Time-based function back-off |
US8787566B2 (en) * | 2006-08-23 | 2014-07-22 | Red Hat, Inc. | Strong encryption |
US9038154B2 (en) | 2006-08-31 | 2015-05-19 | Red Hat, Inc. | Token Registration |
US8074265B2 (en) * | 2006-08-31 | 2011-12-06 | Red Hat, Inc. | Methods and systems for verifying a location factor associated with a token |
US8977844B2 (en) | 2006-08-31 | 2015-03-10 | Red Hat, Inc. | Smartcard formation with authentication keys |
US8356342B2 (en) * | 2006-08-31 | 2013-01-15 | Red Hat, Inc. | Method and system for issuing a kill sequence for a token |
US8589869B2 (en) | 2006-09-07 | 2013-11-19 | Wolfram Alpha Llc | Methods and systems for determining a formula |
US7945893B2 (en) * | 2006-10-10 | 2011-05-17 | Oracle International Corporation | Mapping web services description language documents to XQuery functions |
US7797310B2 (en) * | 2006-10-16 | 2010-09-14 | Oracle International Corporation | Technique to estimate the cost of streaming evaluation of XPaths |
US9183321B2 (en) * | 2006-10-16 | 2015-11-10 | Oracle International Corporation | Managing compound XML documents in a repository |
US7827177B2 (en) * | 2006-10-16 | 2010-11-02 | Oracle International Corporation | Managing compound XML documents in a repository |
US8693690B2 (en) * | 2006-12-04 | 2014-04-08 | Red Hat, Inc. | Organizing an extensible table for storing cryptographic objects |
US8015210B2 (en) * | 2006-12-27 | 2011-09-06 | Sap Ag | Method and system for generating string-based addresses |
US8869020B2 (en) * | 2006-12-27 | 2014-10-21 | Sap Ag | Method and system for generating relational spreadsheets |
US20080178152A1 (en) * | 2007-01-23 | 2008-07-24 | Rafal Przemyslaw Konik | Software Code Retention Management |
US20080189311A1 (en) * | 2007-02-01 | 2008-08-07 | Microsoft Corporation | Visual controls for stored procedure and object relational class development |
US8214797B2 (en) * | 2007-02-01 | 2012-07-03 | Microsoft Corporation | Visual association creation for object relational class development |
US8813243B2 (en) * | 2007-02-02 | 2014-08-19 | Red Hat, Inc. | Reducing a size of a security-related data object stored on a token |
US20080189132A1 (en) * | 2007-02-05 | 2008-08-07 | Matthew Minson | Automatic Hospital Bed Accounting System |
US8639940B2 (en) * | 2007-02-28 | 2014-01-28 | Red Hat, Inc. | Methods and systems for assigning roles on a token |
US8832453B2 (en) * | 2007-02-28 | 2014-09-09 | Red Hat, Inc. | Token recycling |
US9081948B2 (en) * | 2007-03-13 | 2015-07-14 | Red Hat, Inc. | Configurable smartcard |
US8024701B2 (en) * | 2007-03-27 | 2011-09-20 | Microsoft Corporation | Visual creation of object/relational constructs |
US20090006449A1 (en) * | 2007-06-29 | 2009-01-01 | Microsoft Corporation | Modeling and Analysis of Computer Networks |
WO2009039411A1 (en) * | 2007-09-21 | 2009-03-26 | Presenceid, Inc. | Systems and methods for receiving and sending messages about changes to data attributes |
US8196126B2 (en) * | 2007-10-29 | 2012-06-05 | Sap Ag | Methods and systems for dynamically generating and optimizing code for business rules |
US8437996B2 (en) * | 2007-12-13 | 2013-05-07 | Exxonmobil Upstream Research Company | Parallel adaptive data partitioning on a reservoir simulation using an unstructured grid |
US8789012B1 (en) * | 2007-12-17 | 2014-07-22 | Cisco Technology, Inc. | System and method for automatically generating computer code to obtain data from devices optionally using a web services interface |
CN101499003A (en) * | 2008-01-31 | 2009-08-05 | 国际商业机器公司 | Method for generating constraint expression related to model and constraint language editor |
US7908252B1 (en) | 2008-03-19 | 2011-03-15 | Crossroads Systems, Inc. | System and method for verifying paths to a database |
US8972433B2 (en) * | 2008-04-18 | 2015-03-03 | Travelport Operations, Inc. | Systems and methods for programmatic generation of database statements |
US8825708B1 (en) * | 2008-04-30 | 2014-09-02 | Netapp, Inc. | Program language binding generation for system interfaces |
CN104407518B (en) | 2008-06-20 | 2017-05-31 | 因文西斯系统公司 | The system and method interacted to the reality and Simulation Facility for process control |
US7958112B2 (en) * | 2008-08-08 | 2011-06-07 | Oracle International Corporation | Interleaving query transformations for XML indexes |
US8032544B2 (en) * | 2008-09-24 | 2011-10-04 | The Boeing Company | Methods and apparatus for generating dynamic program files based on input queries that facilitate use of persistent query services |
CN102138146A (en) * | 2008-09-30 | 2011-07-27 | 埃克森美孚上游研究公司 | Method for solving reservoir simulation matrix equation using parallel multi-level incomplete factorizations |
EP2350810A4 (en) * | 2008-09-30 | 2013-06-05 | Exxonmobil Upstream Res Co | Self-adapting iterative solver |
US8301622B2 (en) * | 2008-12-30 | 2012-10-30 | Novell, Inc. | Identity analysis and correlation |
US8296297B2 (en) * | 2008-12-30 | 2012-10-23 | Novell, Inc. | Content analysis and correlation |
US8386475B2 (en) * | 2008-12-30 | 2013-02-26 | Novell, Inc. | Attribution analysis and correlation |
US8060857B2 (en) * | 2009-01-31 | 2011-11-15 | Ted J. Biggerstaff | Automated partitioning of a computation for parallel or other high capability architecture |
US20100250479A1 (en) * | 2009-03-31 | 2010-09-30 | Novell, Inc. | Intellectual property discovery and mapping systems and methods |
US8601015B1 (en) | 2009-05-15 | 2013-12-03 | Wolfram Alpha Llc | Dynamic example generation for queries |
US8788524B1 (en) | 2009-05-15 | 2014-07-22 | Wolfram Alpha Llc | Method and system for responding to queries in an imprecise syntax |
US8463964B2 (en) | 2009-05-29 | 2013-06-11 | Invensys Systems, Inc. | Methods and apparatus for control configuration with enhanced change-tracking |
US8127060B2 (en) | 2009-05-29 | 2012-02-28 | Invensys Systems, Inc | Methods and apparatus for control configuration with control objects that are fieldbus protocol-aware |
US9864796B2 (en) * | 2009-06-24 | 2018-01-09 | Microsoft Technology Licensing, Llc | Databases from models |
CN102012900B (en) * | 2009-09-04 | 2013-01-30 | 阿里巴巴集团控股有限公司 | An information retrieval method and system |
US8484015B1 (en) | 2010-05-14 | 2013-07-09 | Wolfram Alpha Llc | Entity pages |
US8812298B1 (en) | 2010-07-28 | 2014-08-19 | Wolfram Alpha Llc | Macro replacement of natural language input |
US8458203B2 (en) | 2011-07-11 | 2013-06-04 | Microsoft Corporation | Optimizing data processing using dynamic schemas |
US9069814B2 (en) | 2011-07-27 | 2015-06-30 | Wolfram Alpha Llc | Method and system for using natural language to generate widgets |
US9734252B2 (en) | 2011-09-08 | 2017-08-15 | Wolfram Alpha Llc | Method and system for analyzing data using a query answering system |
US9851950B2 (en) | 2011-11-15 | 2017-12-26 | Wolfram Alpha Llc | Programming in a precise syntax using natural language |
US8589451B1 (en) * | 2012-05-24 | 2013-11-19 | Sap Ag | Systems and methods for generating a common data model for relational and object oriented databases |
US9280788B2 (en) * | 2012-06-13 | 2016-03-08 | Oracle International Corporation | Information retrieval and navigation using a semantic layer |
US9405424B2 (en) | 2012-08-29 | 2016-08-02 | Wolfram Alpha, Llc | Method and system for distributing and displaying graphical items |
US9299050B2 (en) * | 2012-09-04 | 2016-03-29 | Optymyze PTE Ltd. | System and method of representing business units in sales performance management using entity tables containing explicit entity and internal entity IDs |
US20140201115A1 (en) * | 2013-01-15 | 2014-07-17 | Sap Ag | Determining software object relations using neural networks |
US9665403B2 (en) | 2013-03-15 | 2017-05-30 | Miosoft Corporation | Executing algorithms in parallel |
US9613112B2 (en) * | 2013-03-15 | 2017-04-04 | Miosoft Corporation | Structuring data |
US9684491B2 (en) * | 2013-04-30 | 2017-06-20 | Wal-Mart Stores, Inc. | Annotation-based item description |
US9940104B2 (en) * | 2013-06-11 | 2018-04-10 | Microsoft Technology Licensing, Llc. | Automatic source code generation |
CN104376025B (en) * | 2013-08-16 | 2017-10-10 | 华为技术有限公司 | The date storage method and device of distributed data base |
US20160092829A1 (en) * | 2014-09-29 | 2016-03-31 | Oracle International Corporation | Consigned inventory management system |
US10437564B1 (en) | 2016-09-16 | 2019-10-08 | Software Tree, LLC | Object mapping and conversion system |
US10877735B1 (en) | 2017-09-25 | 2020-12-29 | Amazon Technologies, Inc. | Automated generation of software applications using analysis of submitted content items |
US10705805B1 (en) | 2017-12-12 | 2020-07-07 | Amazon Technologies, Inc. | Application authoring using web-of-sheets data model |
US11586603B1 (en) | 2018-05-23 | 2023-02-21 | Amazon Technologies, Inc. | Index sheets for robust spreadsheet-based applications |
US10956130B2 (en) * | 2018-07-05 | 2021-03-23 | Jpmorgan Chase Bank, N.A. | Method and system for implementing a cloud infrastructure visualizer and generator |
US11010143B2 (en) * | 2018-09-28 | 2021-05-18 | Salesforce.Com, Inc. | Executing formulas written using formula language |
US11003427B2 (en) | 2018-09-28 | 2021-05-11 | Salesforce.Com, Inc. | Interface for generating and testing formulas using a formula language |
US11194793B1 (en) | 2019-06-25 | 2021-12-07 | Amazon Technologies, Inc. | Dynamically materialized views for sheets based data |
US11086894B1 (en) | 2019-06-25 | 2021-08-10 | Amazon Technologies, Inc. | Dynamically updated data sheets using row links |
CN110764759B (en) * | 2019-10-29 | 2023-07-25 | 神华神东煤炭集团有限责任公司 | Data conversion method, storage medium and system |
US11704233B2 (en) * | 2021-11-22 | 2023-07-18 | International Business Machines Corporation | Shift left model execution in software delivery |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4930071A (en) * | 1987-06-19 | 1990-05-29 | Intellicorp, Inc. | Method for integrating a knowledge-based system with an arbitrary database system |
US5235701A (en) * | 1990-08-28 | 1993-08-10 | Teknekron Communications Systems, Inc. | Method of generating and accessing a database independent of its structure and syntax |
US5291583A (en) * | 1990-12-14 | 1994-03-01 | Racal-Datacom, Inc. | Automatic storage of persistent ASN.1 objects in a relational schema |
US5295256A (en) * | 1990-12-14 | 1994-03-15 | Racal-Datacom, Inc. | Automatic storage of persistent objects in a relational schema |
US5297279A (en) * | 1990-05-30 | 1994-03-22 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5426780A (en) * | 1992-02-28 | 1995-06-20 | Intergraph Corporation | System for dynamic segmentation analysis using conversion of relational data into object-oriented data |
-
1994
- 1994-07-14 WO PCT/US1994/007890 patent/WO1995003586A1/en active Application Filing
-
1995
- 1995-03-22 US US08/409,476 patent/US5499371A/en not_active Expired - Lifetime
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4930071A (en) * | 1987-06-19 | 1990-05-29 | Intellicorp, Inc. | Method for integrating a knowledge-based system with an arbitrary database system |
US5297279A (en) * | 1990-05-30 | 1994-03-22 | Texas Instruments Incorporated | System and method for database management supporting object-oriented programming |
US5235701A (en) * | 1990-08-28 | 1993-08-10 | Teknekron Communications Systems, Inc. | Method of generating and accessing a database independent of its structure and syntax |
US5291583A (en) * | 1990-12-14 | 1994-03-01 | Racal-Datacom, Inc. | Automatic storage of persistent ASN.1 objects in a relational schema |
US5295256A (en) * | 1990-12-14 | 1994-03-15 | Racal-Datacom, Inc. | Automatic storage of persistent objects in a relational schema |
Cited By (51)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5809297A (en) * | 1993-10-29 | 1998-09-15 | Wall Data Incorporated | Semantic object modeling system for creating relational database schemas |
WO1996034350A1 (en) * | 1995-04-24 | 1996-10-31 | Aspect Development, Inc. | Modeling of object-oriented database structures, translation to relational database structures, and dynamic searches thereon |
AU706724B2 (en) * | 1995-06-07 | 1999-06-24 | Wall Data Incorporated | Computer system for creating semantic object models from existing relational database schemas |
WO1996041282A1 (en) * | 1995-06-07 | 1996-12-19 | Wall Data Incorporated | Computer system for creating semantic object models from existing relational database schemas |
US5819086A (en) * | 1995-06-07 | 1998-10-06 | Wall Data Incorporated | Computer system for creating semantic object models from existing relational database schemas |
WO1997007470A1 (en) * | 1995-08-17 | 1997-02-27 | Wall Data Incorporated | Method and apparatus for storing and retrieving data in a relational database using an object model |
FR2738649A1 (en) * | 1995-09-13 | 1997-03-14 | Hewlett Packard Co | METHOD FOR CONVERTING OBJECTS FROM A FLAT SPACE TO A CLASS STRUCTURED SPACE |
AT1104U1 (en) * | 1995-09-26 | 1996-10-25 | Siemens Ag Oesterreich | METHOD FOR STORING PERSISTED OBJECTS OF OBJECT-ORIENTED USER PROGRAMS IN A RELATIONAL DATABASE |
EP1012740A2 (en) * | 1996-03-26 | 2000-06-28 | Bull HN Information Systems Inc. | Method of integrating schemas of distributed heterogeneous databases |
EP1012740A4 (en) * | 1996-03-26 | 2000-06-28 | Bull Hn Information Syst | Method of integrating schemas of distributed heterogeneous databases |
WO1999009494A1 (en) * | 1997-08-14 | 1999-02-25 | Aoraki Corporation Limited | Relational database coexistence in object oriented environments |
WO1999027447A1 (en) * | 1997-11-20 | 1999-06-03 | Crosskeys Systems Corporation | Knowledge module |
WO1999033002A1 (en) * | 1997-12-22 | 1999-07-01 | Tony Chun Tung Ng | Method and apparatus for creating indexes in a relational database corresponding to classes in an object-oriented application |
US6609133B2 (en) | 1997-12-22 | 2003-08-19 | Sun Microsystems, Inc. | Integrating both modifications to an object model and modifications to a database into source code by an object-relational mapping tool |
US6240413B1 (en) | 1997-12-22 | 2001-05-29 | Sun Microsystems, Inc. | Fine-grained consistency mechanism for optimistic concurrency control using lock groups |
US6268850B1 (en) | 1997-12-22 | 2001-07-31 | Sun Microsystems, Inc. | User interface for the specification of lock groups |
US6374256B1 (en) | 1997-12-22 | 2002-04-16 | Sun Microsystems, Inc. | Method and apparatus for creating indexes in a relational database corresponding to classes in an object-oriented application |
US6385618B1 (en) | 1997-12-22 | 2002-05-07 | Sun Microsystems, Inc. | Integrating both modifications to an object model and modifications to a database into source code by an object-relational mapping tool |
US6175837B1 (en) | 1998-06-29 | 2001-01-16 | Sun Microsystems, Inc. | Object-relational mapping toll that processes views |
US6243709B1 (en) | 1998-06-29 | 2001-06-05 | Sun Microsystems, Inc. | Method and apparatus for loading stored procedures in a database corresponding to object-oriented data dependencies |
US6279008B1 (en) | 1998-06-29 | 2001-08-21 | Sun Microsystems, Inc. | Integrated graphical user interface method and apparatus for mapping between objects and databases |
GB2347243A (en) * | 1998-12-31 | 2000-08-30 | Ibm | Operations on a relational database upon completion of a transaction by an object-oriented system |
GB2347243B (en) * | 1998-12-31 | 2003-04-02 | Ibm | Systems methods and computer program products for ordering objects corresponding to database operations that are performed on a relational database upon |
US6456995B1 (en) | 1998-12-31 | 2002-09-24 | International Business Machines Corporation | System, method and computer program products for ordering objects corresponding to database operations that are performed on a relational database upon completion of a transaction by an object-oriented transaction system |
US10467688B1 (en) | 1999-02-09 | 2019-11-05 | Jpmorgan Chase Bank, N.A. | System and method for back office processing of banking transactions using electronic files |
US6591275B1 (en) | 2000-06-02 | 2003-07-08 | Sun Microsystems, Inc. | Object-relational mapping for tables without primary keys |
US7076490B2 (en) * | 2001-10-13 | 2006-07-11 | Electronics And Telecommunications Research Institute | Object-relational database management system and method for deleting class instance for the same |
US20110047175A1 (en) * | 2004-04-21 | 2011-02-24 | Kong Eng Cheng | Querying Target Databases Using Reference Database Records |
US8346794B2 (en) * | 2004-04-21 | 2013-01-01 | Tti Inventions C Llc | Method and apparatus for querying target databases using reference database records by applying a set of reference-based mapping rules for matching input data queries from one of the plurality of sources |
AU2005246946B2 (en) * | 2005-02-18 | 2011-05-26 | Microsoft Technology Licensing, Llc | Relationship modeling |
EP1693751A3 (en) * | 2005-02-18 | 2007-11-07 | Microsoft Corporation | Relationship modeling |
CN1821957A (en) * | 2005-02-18 | 2006-08-23 | 微软公司 | Relationship modeling |
US7962497B2 (en) | 2005-02-18 | 2011-06-14 | Microsoft Corporation | Relationship modeling |
KR101224813B1 (en) * | 2005-02-18 | 2013-01-21 | 마이크로소프트 코포레이션 | Relationship modeling |
CN1821957B (en) * | 2005-02-18 | 2014-03-12 | 微软公司 | Relationship modeling |
EP1693751A2 (en) * | 2005-02-18 | 2006-08-23 | Microsoft Corporation | Relationship modeling |
WO2006108753A1 (en) * | 2005-04-14 | 2006-10-19 | International Business Machines Corporation | Relational query of a hierarchical database |
WO2011038770A1 (en) * | 2009-10-01 | 2011-04-07 | Starcounter Ab | Systems and methods for managing databases |
US8266125B2 (en) | 2009-10-01 | 2012-09-11 | Starcounter Ab | Systems and methods for managing databases |
US8856092B2 (en) | 2009-10-01 | 2014-10-07 | Starcounter Ab | Systems and methods for managing databases |
US9038177B1 (en) | 2010-11-30 | 2015-05-19 | Jpmorgan Chase Bank, N.A. | Method and system for implementing multi-level data fusion |
US9292588B1 (en) | 2011-07-20 | 2016-03-22 | Jpmorgan Chase Bank, N.A. | Safe storing data for disaster recovery |
US9971654B2 (en) | 2011-07-20 | 2018-05-15 | Jpmorgan Chase Bank, N.A. | Safe storing data for disaster recovery |
US10540373B1 (en) | 2013-03-04 | 2020-01-21 | Jpmorgan Chase Bank, N.A. | Clause library manager |
WO2014153377A1 (en) * | 2013-03-20 | 2014-09-25 | Microsoft Corporation | Extensible and queryable strong types |
US10705802B2 (en) | 2013-03-20 | 2020-07-07 | Microsoft Technology Licensing, Llc | Extensible and queryable strong types |
US10248668B2 (en) * | 2016-07-18 | 2019-04-02 | International Business Machines Corporation | Mapping database structure to software |
US11163616B2 (en) | 2017-03-07 | 2021-11-02 | Polyjuice Ab | Systems and methods for enabling interoperation of independent software applications |
US10885157B2 (en) | 2017-04-03 | 2021-01-05 | International Business Machines Corporation | Determining a database signature |
CN111026777A (en) * | 2019-12-13 | 2020-04-17 | 中国南方电网有限责任公司 | Entity class code generation method and device, computer equipment and storage medium |
CN111026777B (en) * | 2019-12-13 | 2023-09-29 | 中国南方电网有限责任公司 | Entity class code generation method, entity class code generation device, computer equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
US5499371A (en) | 1996-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5499371A (en) | Method and apparatus for automatic generation of object oriented code for mapping relational data to objects | |
US5557785A (en) | Object oriented multimedia information system using information and multiple classes to manage data having various structure and dedicated data managers | |
US5706506A (en) | Method and apparatus for managing relational data in an object cache | |
US6243709B1 (en) | Method and apparatus for loading stored procedures in a database corresponding to object-oriented data dependencies | |
US5937409A (en) | Integrating relational databases in an object oriented environment | |
Atkinson et al. | The object-oriented database system manifesto | |
EP0978061B1 (en) | Object graph editing context and methods of use | |
US5832268A (en) | System and method for supporting complex objects in an object oriented computing environment | |
US5495567A (en) | Automatic interface layout generator for database systems | |
Keller et al. | Persistence software: Bridging object-oriented programming and relational databases | |
US20010016843A1 (en) | Method and apparatus for accessing data | |
Dayal et al. | Simplifying complex objects: The PROBE approach to modelling and querying them | |
Tresch et al. | Meta object management and its application to database evolution | |
Estublier et al. | Three dimensional versioning | |
Kakoudakis et al. | The TAU temporal object model | |
US6658425B1 (en) | Generic data centric object structure and implementation | |
Unland et al. | Object-oriented database systems: concepts and perspectives | |
Hsu et al. | A metadata system for information modeling and integration | |
EP1040432B1 (en) | Method and apparatus for loading stored procedures in a database corresponding to object-oriented data dependencies | |
Bergamaschi et al. | Object Wrapper: an object-oriented interface for relational databases | |
Marcos et al. | Object-oriented database design | |
Freeman et al. | LINQ to SQL Entity Classes | |
Sawyer et al. | A User Interface Framework for an Object-Oriented Database System | |
Chen et al. | Eliminating the impedance mismatch between relational and object-oriented systems | |
Orlandic | A Layered Multi-Model Design Framework for DBMS Construction |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP KR |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: CA |