SQL:1999
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
SQL:1999 (also called SQL 3) was the fourth revision of the SQL database query language. It introduced a large number of new features, many of which required clarifications in the subsequent SQL:2003. The latest revision of the standard is SQL:2011.
Contents
Summary
The ISO standard documents were published between 1999 and 2002 in several installments, the first one consisting of multiple parts. Unlike previous editions, the standard's name used a colon instead of a hyphen for consistency with the names of other ISO standards. The first installment of SQL:1999 had five parts:
- SQL/Framework ISO/IEC 9075-1:1999
- SQL/Foundation ISO/IEC 9075-2:1999
- SQL/CLI : an updated definition of the extension Call Level Interface, originally published in 1995, also known as CLI-95 ISO/IEC 9075-3:1999
- SQL/PSM : an updated definition of the extension Persistent Stored Modules, originally published in 1996, also known as PSM-96 ISO/IEC 9075-4:1999
- SQL/Bindings ISO/IEC 9075-5:1999
Three more parts, also considered part of SQL:1999 were published subsequently:
- SQL/MED Management of External Data (SQL:1999 part 9) ISO/IEC 9075-9:2001
- SQL/OLB Object Language Bindings (SQL:1999 part 10) ISO/IEC 9075-10:2000
- SQL/JRT SQL Routines and Types using the Java Programming Language (SQL:1999 part 13) ISO/IEC 9075-13:2002
New features
Lua error in package.lua at line 80: module 'strict' not found.
Data types
Boolean data types
The SQL:1999 standard calls for a Boolean type,[1] but many commercial SQL Servers (Oracle Database, IBM DB2) do not support it as a column type, variable type or allow it in the results set. Microsoft SQL Server is one of the few database systems that properly supports BOOLEAN values using its "BIT" data type. Every 1-8 BIT fields occupies one full byte of space on disk. MySQL interprets "BOOLEAN" as a synonym for TINYINT (8-bit signed integer).[2] PostgreSQL provides a standard conforming Boolean type [3]
Distinct user-defined types of power
Sometimes called just distinct types, these were introduced as an optional feature (S011) to allow existing atomic types to be extended with a distinctive meaning to create a new type and thereby enabling the type checking mechanism to detect some logical errors, e.g. accidentally adding an age to a salary. For example:
create type age as integer FINAL;
create type salary as integer FINAL;
creates two different and incompatible types. The SQL distinct types use name equivalence not structural equivalence like typedefs in C. It's still possible to perform compatible operations on (columns or data) of distinct types by using an explicit type CAST.
Few SQL systems support these. IBM DB2 is one those supporting them.[4] Oracle database does not currently support them, recommending instead to emulate them by a one-place structured type.[5]
Structured user-defined types
<templatestyles src="Module:Hatnote/styles.css"></templatestyles>
These are the backbone of the object-relational database extension in SQL:1999. They are analogous to classes in objected-oriented programming languages. SQL:1999 allows only single inheritance.
Common table expressions and recursive queries
SQL:1999 added a WITH [RECURSIVE] construct allowing recursive queries, like transitive closure, to be specified in the query language itself; see common table expressions.
Some OLAP capabilities
GROUP BY was extended with ROLLUP, CUBE, and GROUPING SETS.
Role-based access control
Full support for RBAC via CREATE ROLE.
References
- ↑ ISO/IEC 9075-2:1999 section 4.6 Boolean types
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ PostgreSQL documentation about Boolean Type
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
Further reading
- Lua error in package.lua at line 80: module 'strict' not found.
- Lua error in package.lua at line 80: module 'strict' not found.
