From 90edb265e396312e4a0c15d021745a944648e7ee Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Sat, 22 Jun 2002 02:04:55 +0000 Subject: Implement SQL99 CREATE CAST and DROP CAST statements. Also implement alternative forms to expose the PostgreSQL CREATE FUNCTION features. Implement syntax for READ ONLY and READ WRITE clauses in SET TRANSACTION. READ WRITE is already implemented (of course). Implement syntax for "LIKE table" clause in CREATE TABLE. Should be fairly easy to complete since it resembles SELECT INTO. Implement MATCH SIMPLE clause for foreign key definitions. This is explicit SQL99 syntax for the default behavior, so we now support it :) Start implementation of shorthand for national character literals in scanner. For now, just swallow the leading "N", but sometime soon let's figure out how to pass leading type info from the scanner to the parser. We should use the same technique for binary and hex bit string literals, though it might be unusual to have two apparently independent literal types fold into the same storage type. --- doc/src/sgml/features.sgml | 58 +++++++++++++++++++++++----------------------- 1 file changed, 29 insertions(+), 29 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/features.sgml b/doc/src/sgml/features.sgml index b023225a158..06b4f4e0acd 100644 --- a/doc/src/sgml/features.sgml +++ b/doc/src/sgml/features.sgml @@ -1,29 +1,29 @@ SQL99 Feature List - - Supported Features + + SQL92 defined three feature sets for + compliance: basic, intermediate, and advanced. Most database + products claiming SQL standards compliance were + compliant at only the basic level, since the entire set of + intermediate and advanced features was either too voluminous or in + conflict with legacy behaviors. + - - SQL92 defined three feature sets for - compliance: basic, intermediate, and advanced. Most database - products claiming SQL standards compliance were - compliant at only the basic level, since the entire set of - intermediate and advanced features was either too voluminous or in - conflict with legacy behaviors. - + + SQL99 defines a large set of individual + features rather than the ineffectively broad three levels found in + SQL92. We provide a list of supported features, + followed by a list of the features defined in SQL99 which are not + yet supported in PostgreSQL. + - - SQL99 defines a large set of individual - features rather than the ineffectively broad three levels found in - SQL92. We provide a list of supported features, - followed by a list of the features defined in SQL99 which are not - yet supported in PostgreSQL. - + + Supported Features @@ -1132,6 +1132,11 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 tho Array as result type of functions + + S211 + User-defined cast functions + CREATE CAST(type AS type) + T031 BOOLEAN data type @@ -1147,11 +1152,6 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 tho DISTINCT predicate - - T171 - LIKE clause in table definition - - T191 Referential action RESTRICT @@ -1318,7 +1318,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 tho E152-02 SET TRANSACTION statement: READ ONLY and READ WRITE clauses - + Syntax accepted; READ ONLY not supported E171 @@ -1621,11 +1621,6 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 tho Subtype treatment TREAT(expr AS type) - - S211 - User-defined cast functions - CREATE CAST(type AS type) WITH - S231 Structured type locators @@ -1712,6 +1707,11 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.2 2002/06/19 06:11:36 tho Recursive query + + T171 + LIKE clause in table definition + CREATE TABLE T1 (LIKE T2) + T211-05 Ability to specify a search condition that must be true -- cgit v1.2.3