RUNTIME CLASS DATABASE OPERATION

• US 20080263078A1
• Filed: 08/14/2007
• Published: 10/23/2008
• Est. Priority Date: 04/20/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Pather, Shyamalan, Reed, Jeffrey E., Derstadt, Jeffrey Michael, Conrad, Andrew J., Perry, Carl Yates
• Granted Patent: US 8,037,039 B2
• Time in Patent Office: Days
• US Class Current: 707/102
• CPC Class Codes: G06F 16/90335 Query processing

Abstract

Programmers typically like operating with databases through use of classes. Classes allow a user to function with a database through use of a non-database programming language. To ease use of the classes, a class context is generated at runtime that does not force a programmer to handle various source files that are a product of class generation. Therefore, the user can have the ease of using classes without having to perform extra actions.

Claims

1. A system, comprising:

a reception component that obtains entity data derived from information stored in a database; and

a generation component that produces at least one class based on entity data at runtime.

2. The system of claim 1, wherein the reception component obtains the entity data from an auxiliary location.

3. The system of claim 1, further comprising a normalization component that homogenizes at least one name included in the database.

4. The system of claim 1, further comprising a definition component that composes at least one rule utilized in production of at least one class.

5. The system of claim 1, further comprising a chain component that links at least two rules together for use in production of at least one class.

6. The system of claim 1, further comprising an order component places at least one rule in a sequence, wherein the generation component accesses at least one rule for production of at least one class in accordance with the sequence.

7. The system of claim 1, further comprising artificial intelligence that makes one inference, at least one determination, or at least one of each in relation to operation of the generation component.

8. The system of claim 1, further comprising a workspace component that creates a shell that can hold at least one entity based on received entity data.

9. The system of claim 1, further comprising a build component that regulates control of the generation component.

10. The system of claim 1, further comprising a query component that executes logic in production of at least of at least one class.

11. The system of claim 1, further comprising a framework component creates a class context from at least one produced class.

12. The system of claim 1, further comprising an input component that entertains commands from an auxiliary location for manipulation of at least one rule employed in production of at least one class.

13. A method, comprising

constructing at least one general class from at least one map file that relates to a database, at least one name service, logic, or a combination thereof, and

creating a context class based on at least one general class.

14. The method of claim 13, further comprising receiving at least one map file for constructing at least one general class from an auxiliary location.

15. The method of claim 13, further comprising generating a map file for constructing at least one general class based on database information.

16. The method of claim 15, further comprising operating a query upon the database, wherein a result of the query is used in generation of a map file.

17. The method of claim 13, further comprising attempting to locate at least one pre-existing class with a name that complements at least one general class.

18. The method of claim 13, further comprising undertaking to find at least one function of a pre-existing class with a name match at least one property name associated with at least one general class.

19. A system, comprising:

means for collecting logic that regulates generation of at least one class; and

means for implementing collected logic.

20. The system of claim 20, further comprising means for replacing stored logic with logic created by a user.