A relational data base management system

Bracchi, Giampio; Fedeli, A.; Puppa, Paolo

doi:10.1145/800194.805904

Cited by 23 publications

(11 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Among many relational query languages proposed [BI,B2,B3,C3,GI,SI], SEQUEL is an English-like query language with outstanding features.…”

Section: The Query Language -Raquelmentioning

confidence: 99%

Design and implementation of a relational database on a minicomputer

Lien¹

1977

Proceedings of the 1977 Annual Conference on - ACM '77

View full text Add to dashboard Cite

DB85, a relational database management system on a minicomputer Interdata 85, is geseribed. It is a single user system to run on a computer with 64K bytes of memory and disk storage. The system supports a high level, relation-algebraic query language which provides facilities for users to define, create, manipulate, and interrogate the relations in the database. Emphasis in the presentation is on the query language design, physical structures of relations and minicomputer related issues.The approach used in the implementation reflects a clear separation of the logical view and the physical representation of the database.The goal of the project is to investigate minicomputer oriented database technology and to develop a training tool for teaching database concepts.

show abstract

“…Among many relational query languages proposed [BI,B2,B3,C3,GI,SI], SEQUEL is an English-like query language with outstanding features.…”

Section: The Query Language -Raquelmentioning

confidence: 99%

Design and implementation of a relational database on a minicomputer

Lien¹

1977

Proceedings of the 1977 Annual Conference on - ACM '77

View full text Add to dashboard Cite

show abstract

“…For example, although information on education and child exist in the same row in the table, there does not exist any relationship between them except that they are both related to the same person. Hence these tables or Forms are not relational tables [17 -2 I], but perhaps somewhat akin to Bracchi's unnormalized relations [22][23][24]. Note that additional visual aids can be included in the Form's layout if so desired by the user, e.g.…”

Section: Conceptual Data Representationmentioning

confidence: 99%

“…Several existing languages [7,19,22,25,26] were investigated to determine if they may be used for data translation. It was found that they are either too low level, lack the required capability, or are too mathematically oriented for the type of users we visualized.…”

Section: Altering Values Of Data Instances In Different Mannersmentioning

confidence: 99%

A General Methodology for Data Conversion and Restructuring

1976

View full text Add to dashboard Cite

This paper presents a methodology and a model for data conversion or translation. The model assumes that both source and target systems are available and that conversion interfaces may be required to interact between these systems and the conversion system. To achieve data conversion or translation using this approach, two languages are needed: I) a language to describe the data structures, and 2) a language to specify the mapping between source and target data. This paper describes these two languages, DE-FINE and CONVERT and gives numerous examples to show the capabilities of these languages and how they can be used in data conversion and restructuring. Both languages are high level and nonprocedural and have the power to deal with most situations encountered in data conversion processes. In addition, the paper also describes some of the facilities in the languages specifically designed for data checking in a data conversion process.

show abstract

“…Bracchi et al [14] in designing a language (COLARD) for a relational database management system, decided to allow the definition of nonnormalized relations. However, because COLARD is based on first-order predicate calculus, one needs mathematical sophistication to use the language, in spite of the English flavor injected into it.…”

Section: Design Criteria and Underlying Conceptsmentioning

confidence: 99%

Convert

1975

View full text Add to dashboard Cite

the resulting set of assertions would have been the same but the subset of assertions added by a particular query might have been different. Figure 16 contains a data structure diagram for the design that was created by the system. The DOCTOR-PATIENT confiuency is detected from ABOVE assertions made in the second and third queries, and the base for the confluent hierarchy, the TREATMENT record, is discovered from assertions made in the first and second queries. The ABOVE assertions from queries five and six are erased because of redundancy. Only five ABOVE assertions remain, resulting in five of the sets (excluding SYM13 and SYM15) of Figure 16.The INORABOVE assertions are reduced to eleven, with one assertion for each item except for DOCNAME.

show abstract

A relational data base management system

Cited by 23 publications

References 14 publications

Design and implementation of a relational database on a minicomputer

Design and implementation of a relational database on a minicomputer

A General Methodology for Data Conversion and Restructuring

Convert

Contact Info

Product

Resources

About