The ANS Database Committee (X3H2) is currently at work on a proposed standard relational database language (RDL), and has adopted as a basis for that activity a definition of the "structured query language" SQL from IBM [10]. Moreover, numerous hardware and software vendors (in addition to IBM) have already released or at least announced products that are based to a greater or lesser extent on the SQL language as defined by IBM. There can thus be little doubt that the importance of that language will increase significantly over the next few years. Yet the SQL language is very far from perfect. The purpose of this paper is to present a critical analysis of the language's major shortcomings, in the hope that it may be possible to remedy some of the deficiencies before their influence becomes too all-pervasive. The paper's standpoint is primarily that of formal computer languages in general, rather than that of database languages specifically.
[1]
C. J. Date.
A guide to DB2
,
1984
.
[2]
C. J. Date.
Null Values in Database Management
,
1982,
BNCOD.
[3]
Irving L. Traiger,et al.
Granularity of Locks in a Large Shared Data Base.
,
1975,
VLDB 1975.
[4]
C. J. Date.
An Introduction to the Unified Database Language (UDL)
,
1980,
VLDB.
[5]
C. J. Date.
The Outer Join
,
1983,
ICOD.
[6]
C. J. Date.
Some principles of good language design: with especial reference to the design of database languages
,
1984,
SGMD.
[7]
E. F. Codd,et al.
Extending the database relational model to capture more meaning
,
1979,
ACM Trans. Database Syst..
[8]
Irving L. Traiger,et al.
System R: relational approach to database management
,
1976,
TODS.