Method and apparatus for operating on data with a conceptual data manipulation language

• US 6,460,043 B1
• Filed: 02/26/1999
• Issued: 10/01/2002
• Est. Priority Date: 02/04/1998
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Brandes, Kristi L., Tabbara, Bassam, Mariani, Rico
• Primary Examiner(s): ROBINSON, GRETA LEE
• Application Number:
  US09/258,417
• Time in Patent Office: 1,313 Days
• Field of Search: 707/2, 707/3, 707/100, 707/101, 707/4, 707/102
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2423 Interactive query statement specification based on a database schema
• CPC Class Codes: G06F 16/2433 Query languages
• CPC Class Codes: G06F 16/2452 Query translation
• CPC Class Codes: G06F 16/289 Object oriented databases
• 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

Abstract

A data services layer is disclosed which maintains a dictionary of conceptual information and physical information about the data. Machine-readable requests to access the data are in a form related to a conceptual organization of the data, and is not specific to a physical organization of the data. A machine-readable query to obtain a subset of the data is produced by referencing the dictionary of conceptual and physical information about the data. The conceptual information is obtained from an object-relational-model of the data, and the physical information indicates how the data is organized on the data storage medium. Requests are written in a conceptual query language (CQL) which substantially uses terms belonging to or derived from a natural language. CQL includes terms in the classes of names and concepts, and wherein name terms are used to describe objects in the object-relational-model of the data, and concept terms are used to specify the data subset desired. Concept terms specify Facts desired from the data, and filters and sort specifications to be applied to the Facts. In an example embodiment, the data is organized in rows, and CQL includes a select command that retrieves data in rows. A set of data representing a profile of performance characteristics related to how to retrieve data is provided, and queries are formed based at least in part on the performance characteristics.

Claims

1. A method for operating on data stored on a computer readable medium, comprising:

creating a database of conceptual information and physical information about the data, wherein the conceptual information is mapped to the physical information, and storing the database on a computer readable data storage medium;

receiving a conceptual request to operate on the data, wherein the conceptual request is in a form related to a conceptual organization of the data; and

in response to the conceptual request, creating a data manipulation request to operate on the data by referencing the database of conceptual information and physical information about the data, and wherein the data manipulation request references the data at least in part in a manner related to a physical organization of the data.

2. A method according to claim 1 wherein the conceptual information is expressed in terms of data entities that have a relationship to one another.

3. A method according to claim 2 wherein the conceptual request identifies data to be operated on as entities, and not by the physical information about the data.

4. A method according to claim 1 wherein the conceptual information is derived from a conceptual model of the data.

5. A method according to claim 1 where the conceptual information is derived from an Entity-Relation model of the data.

6. A method according to claim 4 wherein a mapping of the conceptual model is stored in a spreadsheet.

7. A method according to claim 4 wherein a mapping of the conceptual model is stored in plain text.

8. A method according to claim 1 wherein the data manipulation request is submitted to a host physical system, and wherein the physical information is automatically extracted from the host physical system by inspection thereof.

9. A method according to claim 1 wherein the conceptual request is written in a conceptual query language (CQL) which substantially uses terms belonging to or derived from a natural language.

10. A method according to claim 9 wherein the natural language is substantially American English.

11. A method according to claim 9 wherein the CQL includes terms in the classes of objects and predicates.

12. A method according to claim 11 wherein the predicates indicate one or more roles the objects play.

13. A method according to claim 9 wherein the data is organized in rows, and CQL includes a select command that retrieves data in rows.

14. A method according to claim 13 wherein the rows may be organized hierarchically.

15. A method according to claim 1 further including receiving the conceptual request in a data services layer, and wherein the data services layer creates the data manipulation request.

16. A method according to claim 15 wherein the data services layer is designed specifically for a particular type of physical data store.

17. A method according to claim 15 wherein at least two different data services layers can be used to receive the same conceptual request, and wherein each different data services layer creates a different data manipulation request depending on the underlying physical data store of a particular data services layer.

18. A method according to claim 1 wherein the conceptual information is mapped to the physical information at a first time, the physical information is changed at a later time, and the conceptual information is re-mapped to the changed physical information;

and wherein a second conceptual request received after the conceptual information is re-mapped results in a second data manipulation request that references the changed physical information without a change in the form of conceptual requests.

19. A method according to claim 1 wherein the conceptual information is mapped to the physical information at a first time, the conceptual information is changed at a later time, and the changed conceptual information is re-mapped to the physical information;

and wherein a second conceptual request received after the conceptual information is re-mapped results in a second data manipulation request that references the physical information without a change in the form of conceptual requests.

20. A method according to claim 15 wherein the conceptual information is mapped to the physical information at a first time, the conceptual information is changed at a later time, and the changed conceptual information is re-mapped to the physical information;

and wherein a second conceptual request received after the conceptual information is re-mapped results in a second data manipulation request that references the physical information without a change in the form of conceptual requests.

21. A method according to claim 1 further comprising providing a profile of performance characteristics related to retrieving the data, and wherein the data manipulation request is formed based in part on the profile of performance characteristics.

22. A method according to claim 21 further including receiving the conceptual request in a data services layer, and wherein the data services layer creates the data manipulation request using the profile of performance characteristics.

23. A method according to claim 22 wherein the profile of performance characteristics is used by differing data services layers independent of the particulars of conceptual requests submitted to the data services layers.

24. A method according to claim 23 wherein the profile of performance characteristics embody knowledge of different operating environments including the nature and quantity of the data, characteristics of an interpreter of the data manipulation request, and the network topology.

25. A method according to claim 24 wherein the profile of performance characteristics provides domain specific knowledge to the differing data services layers in a generic fashion, so that the differing data services layers remain domain independent.

35. A computer readable medium having a computer program encoded therein, wherein the computer program is executable on a computer to perform the method of claim 1.

36. A computer readable medium having a computer program encoded therein, wherein the computer program is executable on a computer to perform the method of claim 9.

26. Apparatus for operating on data stored on a computer readable medium, comprising:

a database of conceptual information and physical information about the data, the database stored on a computer readable data storage medium;

one or more software components configured to execute on a computer and receive a machine-readable request to operate on the data, wherein the request is in a form related to a conceptual organization of the data; and

the one or more software components further configured to produce a machine-readable query to operate on the data, wherein the query is formed by referencing the database of conceptual information and physical information about the data.

27. Apparatus according to claim 26 wherein the conceptual information is obtained from an object-relational-model of the data.

28. Apparatus according to claim 26 wherein the physical information indicates how the data is organized on the data storage medium.

29. Apparatus according to claim 26 wherein the request is written in a conceptual query language (CQL) which substantially uses terms belonging to or derived from a natural language.

30. Apparatus according to claim 29 wherein the natural language is substantially American English.

31. Apparatus according to claim 29 wherein the CQL includes terms in the classes of objects and predicates.

32. Apparatus according to claim 31 wherein the predicates specify roles that the objects play.

33. Apparatus according to claim 29 wherein the data is organized in rows, and CQL includes a select command that retrieves data in rows.

34. Apparatus according to claim 26 further including a set of data representing a profile of performance characteristics related to how to retrieve the data, and wherein the data manipulation request is formed based at least in part on the profile of performance characteristics.

37. Apparatus for operating on data stored on a computer readable medium, comprising:

a database of conceptual information and physical information about the data, the database stored on a computer readable data storage medium;

means for receiving a machine-readable request to operate on the data, wherein the request is in a form related to a conceptual organization of the data; and

means for producing a machine-readable query to operate on the data, wherein the query is formed by referencing the database of conceptual information and physical information about the data.

38. Apparatus according to claim 37 wherein the conceptual information is obtained from an object-relational-model of the data.

39. Apparatus according to claim 38 wherein the physical information indicates how the data is organized on the data storage medium.

40. Apparatus according to claim 39 wherein the request is written in a conceptual query language (CQL) which substantially uses terms belonging to or derived from a natural language.

41. Apparatus according to claim 40 wherein the natural language is substantially American English.

42. Apparatus according to claim 40 wherein the CQL includes terms in the classes of objects and predicates.

43. Apparatus according to claim 42 wherein the predicates specify roles that the objects play.

44. Apparatus according to claim 40 wherein the data is organized in rows, and CQL includes a select command that retrieves data in rows.

45. Apparatus according to claim 37 further including a set of data representing a profile of performance characteristics related to how to retrieve data, and wherein the data manipulation request is formed based at least in part on the performance characteristics.

46. Apparatus according to claim 37 wherein the means for receiving includes a data manipulation request engine and a data provider, wherein the data provider includes means for managing sessions in the database, and wherein the means for producing a machine-readable query includes a query engine to translate a CQL data manipulation request to the machine-readable request to operate on the data, and to submit the machine-readable request to the data provider.

47. Apparatus according to claim 37 wherein the machine-readable query is written in a data manipulation language.

48. Apparatus according to claim 47 wherein the data manipulation language is standard query language (SQL).