Having a single set of object relational mappings across different instances of the same schemas

• US 20060184568A1
• Filed: 02/15/2005
• Published: 08/17/2006
• Est. Priority Date: 02/15/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Barcia, Roland
• Granted Patent: US 7,536,409 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A method, system, and computer instructions for providing a single set of object relational mappings across different instances of the same schemas. With the present invention, multiple datasources are first configured for class (or set of object definitions). A mapping identifier is set at runtime, wherein the mapping ID is used to access the correct datasource. Mapping code is then generated from the datasource based on the mapping identifier. A schema identifier is acquired from the generated mapping code and prepended to tables in the in the SQL generated code. The schema name is used to connect to the correct schema within a datasource. The mapping ID is also used to access the correct JNDI name to access the correct data source which represents a physical database.

Claims

1. A method in a data processing system for providing a single set of object relational mappings across different instances of the same schemas, comprising:

configuring multiple datasources for a class;

setting a mapping identifier at runtime, wherein the mapping identifier is used to access a particular datasource;

generating mapping code from the particular datasource based on the mapping identifier;

acquiring a schema identifier from the generated mapping code;

prepending the schema identifier to tables in a SQL generated code; and

using a schema name associated with the schema identifier to connect to a schema instance in the particular datasource.

2. The method of claim 1, wherein configuring multiple datasources for a class includes defining multiple entries in a file, and wherein each entry is keyed with an identifier.

3. The method of claim 1, wherein the mapping identifier is set to a current running thread.

4. The method of claim 3, wherein a context is associated with the current running thread, and wherein the context is used to associate data with the current running thread and pass the data between application layers.

5. The method of claim 1, wherein the schema name is used to obtain a correct name from a directory for connecting to the datasource.

6. The method of claim 1, wherein the mapping identifier is set using the mapping identifier associated with one of a requesting user or role.

7. A data processing system for providing a single set of object relational mappings across different instances of the same schemas, comprising:

an application runtime administrative interface for configuring multiple datasources for a class;

an internal application programming interface for setting a mapping identifier at runtime, wherein the mapping identifier is used to access a particular datasource; and

an object relational mapping code generator for generating mapping code from the particular datasource based on the mapping identifier;

wherein the internal application programming interface acquires a schema identifier from the generated mapping code; and

wherein the object relational mapping code generator prepends the schema identifier to tables to tables in a SQL generated code; and

wherein the internal application programming interface uses a schema name associated with the schema identifier to connect to the particular datasource.

8. The data processing system of claim 7, wherein configuring multiple datasources for a class includes defining multiple entries in a file, and wherein each entry is keyed with an identifier.

9. The data processing system of claim 7, wherein the mapping identifier is set to a current running thread.

10. The data processing system of claim 9, wherein a context is associated with the current running thread, and wherein the context is used to associate data with the current running thread and pass the data between application layers.

11. The data processing system of claim 7, wherein the schema name is used to obtain a correct naming and directory interface name for connecting to the datasource.

12. The data processing system of claim 7, wherein the datasource is a cache.

13. The data processing system of claim 7, wherein the mapping identifier is set using the mapping identifier associated with one of a requesting user or role.

14. A computer program product in a computer readable medium for providing a single set of object relational mappings across different instances of the same schemas, comprising:

first instructions for configuring multiple datasources for a class;

second instructions for setting a mapping identifier at runtime, wherein the mapping identifier is used to access a particular datasource;

third instructions for generating mapping code from the particular datasource based on the mapping identifier;

fourth instructions for acquiring a schema identifier from the generated mapping code;

fifth instructions for prepending the schema identifier to tables in a SQL generated code; and

sixth instructions for using a schema name associated with the schema identifier to connect to a schema instance in the particular datasource.

15. The computer program product of claim 14, wherein configuring multiple datasources for a class includes defining multiple entries in a file, and wherein each entry is keyed with an identifier.

16. The computer program product of claim 14, wherein the mapping identifier is set to a current running thread.

17. The computer program product of claim 16, wherein a context is associated with the current running thread, and wherein the context is used to associate data with the current running thread and pass the data between application layers.

18. The computer program product of claim 14, wherein the schema name is used to obtain a correct naming and directory interface name for connecting to the datasource.

19. The computer program product of claim 14, wherein the datasource is a cache.

20. The computer program product of claim 14, wherein the mapping identifier is set using the mapping identifier associated with one of a requesting user or role.