Code generation patterns

• US 20070027907A1
• Filed: 07/29/2005
• Published: 02/01/2007
• Est. Priority Date: 07/29/2005
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Hejlsberg, Anders, Bolognese, Luca, Meijer, Henricus, Hallam, Peter, Warren, Matthew, Kulkarni, Dinesh
• Granted Patent: US 7,631,011 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• 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

The subject disclosure pertains to code generation patterns for use in object relational mapping. The code patterns may be used to manage bidirectional relationships and ensure consistency. The code patterns may support on-demand or deferred loading of relational data. Change detection and tracking are also provided. In addition, a default member modifier allows developers to override tool generated source code without directly modifying the generated source code.

Claims

1. A computer generated object-relational mapping system comprising:

a first data object component that includes object information that corresponds to a second data object component; and

the second data object component that includes object information that corresponds to the first data object component,

one of the first or second data object components notifies the other of the first or second data object components of a change in the corresponding object information.

2. The system of claim 1, the object information of the first data object component includes a first container component that includes at least one data object component and the object information of the second data object component includes a second container component that includes at least one data object component, the first and second container components manage a bidirectional relationship between the first and second data object components.

3. The system of claim 1, the object information of the first data object component includes a first container component that includes a reference to the second data object component and the object information of the second data object component includes a second container component that includes a reference to the first data object component, the first and second container components manage a bidirectional relationship between the first and second data object components.

4. The system of claim 1, the object information of the first data object component includes a first container component that includes a reference to the second data object component and the object information of the second data object component includes a second container component that includes at least one data object component, the first and second container components manage a bidirectional relationship between the first and second data object components.

5. The system of claim 1, the first and second data object components each include a notification component that includes a delegate function.

6. The system of claim 1, the first data object component includes a loading component that intercepts a reference to the object information for the first data object component and retrieves the object information for the first data object component from a data storage component.

7. The system of claim 1, the first and second data object components each include a change notification component that notifies a change detection component prior to modification of the first or second data object components.

8. The system of claim 7, the change notification component utilizes an event handler.

9. The system of claim 7, the change detection component includes a list of modified data object components that includes a copy of the contents of each modified data object component prior to modification.

10. A method for managing relational data mapped to an object model, comprising:

updating a first data object component that includes object information corresponding to a second data object component that includes object information corresponding to the first data object component;

notifying the second data object component of the update of the first data object component; and

updating the second data object component based upon the update of the first data object component.

11. The method of claim 10, further comprising:

intercepting a reference to the object information for the first data object component;

retrieving the object information for the first data object component from a data storage component; and

populating the object information for the first data object component with the retrieved object information.

12. The method of claim 10, further comprising:

notifying a change detection component prior to updating the first data object component.

13. The method of claim 12, further comprising:

copying the first data object component prior to updating the first data object component; and

storing the copy of the first data object component in a list of modified data object components.

14. The method of claim 13, further comprising:

retrieving a data object component from the list of modified data object components;

comparing the retrieved data object component to corresponding data in the data storage component; and

locating the updated data object component corresponding to the retrieved data object component and storing the updated data object component in the data storage component.

15. The method of claim 10, comprising:

determining the relational data tables utilized by a data storage component; and

instantiating data object tables using a generic class corresponding to the relational data tables utilized by the data storage component.

16. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 10.

17. A method for compiling source code declared in at least two separate locations, comprising:

identifying at least one default class member;

searching the source code for a nondefault class member corresponding to the at least one default class member; and

generating implementation code from the source code utilizing the corresponding nondefault member, if found and utilizing the default class member in the absence of a corresponding nondefault class member.

18. The method of claim 17, the default class member is generated using a blueprint.

19. The method of claim 17, the default class member is generated using a code generating tool.

20. A computer readable medium having stored thereon computer executable instructions for carrying out the method of claim 17.