Data base management system extending structure

• US 4,894,771 A
• Filed: 09/29/1988
• Issued: 01/16/1990
• Est. Priority Date: 12/19/1987
• Status: Expired due to Term

• Current Assignee: Ricoh Company Limited
• Original Assignee: Ricoh Company Limited
• Inventors: Shirai, Yasuto, Fujishiro, Issei, Kunii, Hideko, Kunii, Tosiyasu
• Primary Examiner(s): NOT, DEFINED
• Application Number:
  US07/251,097
• Time in Patent Office: 474 Days
• Field of Search: 364/200, 364/300, 364/900
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2452 Query translation
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation

Abstract

A data base management system extending structure includes a data base management system and an extended data base language pre-compiler for pre-compiling an extended data base language into a data base language with which the data base management system can make an access. The extended data base language is added with a link attribute information to the data base language, where the link attribute information specifies relationships of representation objectives.

Claims

1. A data base management system extending structure based on a link-oriented data model, said data base management system extending structure comprising:

a data base management system;

an extended data base language pre-compiler for pre-compiling an input file described in an extended data base language into an output file described in a data base language with which said data base management system can make an access; and

a control part for controlling operations of said data base management system and said extended data base language pre-compiler,

said extended data base language being added with a link attribute information to the data base language, said link attribute information specifying relationships of representation objectives.

2. A data base management system extending structure as claimed in claim 1 in which said extended data base language pre-compiler has an extended data definition language pre-compiler for for pre-compiling an input file described in an extended data definition language into an output file described in a data definition language with which said data base management system can make an access and an extended data manipulation language pre-compiler for pre-compiling an input file described in an extended data manipulation language into an output file described in a data manipulation language with which said data base management system can make an access, said extended data definition language being added with the link attribute information to the data definition language, said extended data manipulation language being added with the link attribute information to the data manipulation language.

3. A data base management system extending structure as claimed in claim 2 in which said data base management system is a GraphBase.

4. A data base management system extending structure as claimed in claim 1 in which said data base management system is a GraphBase.

5. A data base management system extending structure as claimed in claim 1 which further comprises a data base language file and an extended data base language file, said extended data base language pre-compiler pre-compiling an input file of said extended data base language file described in the extended data base language into an output file described in the data base language with which said data base management system can make an access.

6. A data base management system extending structure as claimed in claim 5 in which said data base language file has a data definition language file and a data manipulation language file, and said extended data base language file has an extended data definition language file and an extended data manipulation language file.

7. A data base management system extending structure as claimed in claim 6 in which said data base management system is a GraphBase.

8. A data base management system extending structure as claimed in claim 1 in which said input file described in the extended data base language represents an extended link-oriented data model as

R₁ (f₀, f₁, . . . ,f_n) f₀ :

URI

R₂ (g₀,g₁, . . . ,g_m) g₀ ;

URI

L;

R₁ →

R₂ (at₁, at₂, . . . , at_k)

where R_i (i=1,2) are record-types (R₁, R₂), f_i (i=0, . . . , n) and g_j (j=0, . . . , m) are fields of the record-types R₁ and R₂, f₀ and g₀ are unique record identifiers (URI), a real link-type L is made from the record-type R₁ to the record-type R₂, and at_i (i=1, . . . , k) is permitted in the real link-type L of the link-oriented data model.

9. A data base management system extending structure as claimed in claim 8 in which said output file described in the data base language with which said data base management system can make an access represents the link-oriented data model as

R_c (f₀,g₀, at₁, at₂, . . . , at_k)

(f₀, g₀)=Unique Link Identifier

Virtual L_vl :

R₁ (one)→

R_c (many)

Virtual L_v2 ;

R₂ (one)→

R_c (many).

10. A data base management system extending structure based on a link-oriented data model, said data base management system extending structure comprising:

a data base management system;

an extended data definition language pre-compiler for pre-compiling an input file described in an extended data definition language into an output file described in a data definition language with which said data base management system can make an access;

an extended data manipulation language pre-compiler for pre-compiling an input file described in an extended data manipulation language into an output file described in a data manipulation language with which said data base management system can make an access; and

a control part for controlling operations of said data base management system, said extended data definition language pre-compiler and said extended data manipulation language pre-compiler,

said extended data definition language being added with a link attribute information to the data definition language, said extended data manipulation language being added with a link attribute information to the data manipulation language, said link attribute information specifying relationships of representation objectives.

11. A data base management system extending structure as claimed in claim 10 in which said data base management system is a GraphBase.

12. A data base management system extending structure as claimed in claim 10 in which said input file described in the extended data definition language and/or the extended data manipulation language represents an extended link-oriented data model as

R₁ (f₀, f₁, . . . , f_n) f₀ :

URI

R₂ (g₀, g₁, . . . , g_m) g₀ ;

URI

L;

R₁ →

R₂ (at₁, at₂, . . . , at_k)

where R_i (i=1,2) are record-types (R₁, R₂), f_i (i=0, . . . , n) and g_j (j=0, . . . , m) are fields of the record-types R₁ and R₂, f₀ and g₀ are unique record identifiers (URI), a real link-type L is made from the record-type R₁ to the record-type R₂, and at_i (i=1, . . . , k) is permitted in the real link-type L of the link-oriented data model.

13. A data base management system extending structure as claimed in claim 12 in which said output file described in the data definition language and/or the data manipulation language with which said data base management system can make an access represents the link-oriented data model as

R_c (f₀, g₀, at₁, at₂, . . . , at_k)

(f₀, g₀)=Unique Link Identifier

Virtual L_v1 :

R₁ (one)→

R_c (many)

Virtual L_v2 ;

R₂ (one)→

R_c (many).

14. A data base management system extending structure based on a link-oriented data model, said data base management system extending structure comprising:

a data base management system;

a data definition language file described by a data definition language with which said data base management system can make an access;

a data manipulation language file described by a data manipulation language with which said data base management system can make an access;

an extended data definition language file described by the data definition language added with a link attribute information specifying relationships of representation objectives;

an extended data definition language pre-compiler for pre-compiling an input file described in the extended data definition language into an output file described in the data definition language;

an extended data manipulation language pre-compiler for pre-compiling an input file described in the extended data manipulation language into an output file described in the data manipulation language; and

a control part for controlling operations of said data base management system, said data definition language file, said data manipulation language file, said extended data definition language file, said extended data manipulation language file, said extended data definition language pre-compiler and said extended data manipulation language pre-compiler.

15. A data base management system extending structure as claimed in claim 14 in which said data base management system is a GraphBase.

16. A data base management system extending structure as claimed in claim 14 in which said input file described in the extended data definition language and/or the extended data manipulation language represents an extended link-oriented data model as

R₁ (f₀, f₁, . . . , f_n) f₀ :

URI

R₂ (g₀, g₁, . . . , g_m) g₀ ;

URI

L;

R₁ →

R₂ (at₁, at₂, . . . , at_k)

where R_i (i=1,2) are record-types (R₁, R₂), f_i (i=0, . . . , n) and g_j (j=0, . . . , m) are fields of the record-types R₁ and R₂, f₀ and g₀ are unique record identifiers (URI), a real link-type L is made from the record-type R₁ to the record-type R₂, and at_i (i=1, . . . , k) is permitted in the real link-type L of the link-oriented data model.

17. A data base management system extending structure as claimed in claim 16 in which said output file described in the data definition language and/or the data manipulation language with which said data base management system can make an access represents the link-oriented data model as

R_c (f₀, g₀, at₁, at₂, . . . , at_k)

(f₀, g₀)=Unique Link Identifier

Virtual L_v1 :

R₁ (one)→

R_c (many)

Virtual L_v2 ;

R₂ (one)→

R_c (many).

18. A data base management system extending structure as claimed in claim 14 in which said data defintion language file and/or said data manipulation language file describes an entity-relationship model in a virtual link-type as

R₁ (f_c, . . . )

f_c :

URI

R₂ ( . . . , f_c, . . . )

Virtual L(f_c);

R₁ (one)→

R₂ (many)

(at₁, . . . , at_n)

where R₁ and R₂ are record-types, URI denotes a unique record identifier, L is a virtual link made between the record-types R₁ and R₂ through a common field, a field f_c is a foreign key of the record-type R₂, and link attributes to be added to the virtual link-type L are listed in an attribute list (at₁, . . . , at_n),

said extended data definition language file and/or said extended data manipulation language file adding an intended link attribute to the record-type R₂ as a new field thereby resulting in an extended schema

R₁ (f_c, . . . )

R₂ (f_c, . . . , at₁, . . . , at_n)

Virtual L(f_c);

R₁ (one)→

R₂ (many).