SEQUEL 2: A Unified Approach to Data Definition, Manipulation, and Control

@article{Chamberlin1976SEQUEL2A,
  title={SEQUEL 2: A Unified Approach to Data Definition, Manipulation, and Control},
  author={Donald D. Chamberlin and Morton M. Astrahan and Kapali P. Eswaran and Patricia P. Griffiths and Raymond A. Lorie and James W. Mehl and Phyllis Reisner and Bradford W. Wade},
  journal={IBM J. Res. Dev.},
  year={1976},
  volume={20},
  pages={560-575}
}
SEQUEL 2 is a relational data language that provides a consistent, English keyword-oriented set of facilities for query, data definition, data manipulation, and datac ontrol. SEQUEL 2 may be used either as a stand-alone interface for nonspecialists in data processing or as a data sublanguage embedded in a host programming language for use by application programmers and data base administrators. This paper describes SEQUEL 2 and the means by which it is coupled to a host language. 
Database programming with data abstractions
This paper describes how a general purpose programming language supporting the notion of data abstraction can be used as a data definition and manipulation language for database management systems.Expand
An integrated data base language
TLDR
Care has been taken to ensure that the language HYPOL helps in writing structured programs, and in arriving at this language the capability concept has been used to define access control requirements of a user. Expand
An Access Specification Language for a Relational Data Base System
TLDR
It is conjecture that the introducing of an access specification language provides a conceptual platform for the handling of the "optimization" problem and is implemented as a target language for the optimizer part of the complier. Expand
Toward a unified view of data base management, programming languages, and operating systems-a tutorial
Abstract This paper identifies some common concepts in programming languages, data base management, and operating systems. We present an approach to unifying these concepts based upon the notion ofExpand
A data sublanguage for formulation of linear mathematical models
  • J. Choobineh, J. Sena
  • Computer Science
  • [1988] Proceedings of the Twenty-First Annual Hawaii International Conference on System Sciences. Volume III: Decision Support and Knowledge Based Systems Track
  • 1988
TLDR
The database language SQL is extended to allow the specification of constraints, computed attributes, triggers, and optimizations for mathematical linear programming problems and a macro architecture for the implementation of the system is proposed. Expand
The data management facilities of PLAIN
TLDR
PLAIN incorporates a relational database definitional facility, along with low-level and high-level operations on relations, showing how the database operations are combined with programming language notions such as type checking, block structure, expression evaluation and iteration. Expand
Query-by-Example: A Data Base Language
Discussed is a high-level data base management language that provides the user with a convenient and unified interface to query, update, define, and control a data base. When the user performs anExpand
Comparsing of database intervaces for application programming
TLDR
The evolution of interfaces to databases at the application programming level is analyzed in terms of the growing needs for more reliable programs written in high level languages, for which programmer efficiency is more important than machine efficiency. Expand
DATA MANAGEMENT FOR MICROCOMPUTERS
TLDR
The common data base architecture exploits functional commonality within and across systems to facilitate the compact implementation of a single system which supports file and data base functionality for various programming languages, data models, and data architectures. Expand
Data abstraction, views and updates in RIGEL
TLDR
A data abstraction facility, unlike those proposed for other data base programming languages, is described, which provides a better notation to specify the interface between a program and a data base and to support the disciplined use of views. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 17 REFERENCES
Specifying queries as relational expressions: the SQUARE data sublanguage
TLDR
A data sublanguage called SQUARE, intended for use in ad hoc, interactive problem solving by non-computer specialists, and is shown to be relationally complete; however, it avoids the quantifiers and bound variables required by languages based on the relational calculus. Expand
SEQUEL: A structured English query language
TLDR
The data manipulation facility for a structured English query language (SEQUEL) which can be used for accessing data in an integrated relational data base. Expand
Views, authorization, and locking in a relational data base system
TLDR
The examples in this paper will be drawn from a data base which describes a department store and consists of three relations: EMP, SAL, MGR, DEPT, and LOC. Expand
INGRES: a relational data base system
INGRES (Interactive Graphics and Retrieval System) is a relational data base and graphics system which is being implemented on a PDP-11/40 based hardware configuration at Berkeley. INGRES runs as aExpand
System R: relational approach to database management
TLDR
This paper contains a description of the overall architecture and design of the system, and emphasizes that System R is a vehicle for research in database architecture, and is not planned as a product. Expand
Human factors evaluation of two data base query languages: square and sequel
TLDR
Two data base query languages, SQUARE and SEQUEL, which are intended for use in an interactive mode by both programmers and professional non-programmers (e.g., accountants, lawyers, managers). Expand
A relational model of data for large shared data banks
  • E. Codd
  • Medicine, Computer Science
  • CACM
  • 1970
TLDR
A model based on n-ary relations, a normal form for data base relations, and the concept of a universal data sublanguage are introduced and certain operations on relations are discussed and applied to the problems of redundancy and consistency in the user's model. Expand
Functional specifications of a subsystem for data base integrity
This paper defines an integrity subsystem for an integrated data base management system, and shows how integrity is distinguished from the related areas of security, consistency, and reliability. TheExpand
An authorization mechanism for a relational database system
TLDR
A multiuser database system must selectively permit users to share data, while retaining the ability to restrict data access, and an algorithm for detecting exactly which of B's grants should be revoked is presented. Expand
A multi-level relational system
TLDR
A relational data base is composed of a set of time varying relations inter-related through common domains. Expand
...
1
2
...