mirror of
https://github.com/postgres/postgres.git
synced 2025-06-17 17:02:08 +03:00
Clean up references to SQL92
In most cases, these were just references to the SQL standard in general. In a few cases, a contrast was made between SQL92 and later standards -- those have been kept unchanged.
This commit is contained in:
@ -133,7 +133,7 @@ static void setSchemaName(char *context_schema, char **stmt_schema_name);
|
||||
* will be the transformed CreateStmt, but there may be additional actions
|
||||
* to be done before and after the actual DefineRelation() call.
|
||||
*
|
||||
* SQL92 allows constraints to be scattered all over, so thumb through
|
||||
* SQL allows constraints to be scattered all over, so thumb through
|
||||
* the columns and collect all constraints into one place.
|
||||
* If there are any implied indices (e.g. UNIQUE or PRIMARY KEY)
|
||||
* then expand those into multiple IndexStmt blocks.
|
||||
@ -1405,7 +1405,7 @@ transformIndexConstraints(CreateStmtContext *cxt)
|
||||
/*
|
||||
* Scan the index list and remove any redundant index specifications. This
|
||||
* can happen if, for instance, the user writes UNIQUE PRIMARY KEY. A
|
||||
* strict reading of SQL92 would suggest raising an error instead, but
|
||||
* strict reading of SQL would suggest raising an error instead, but
|
||||
* that strikes me as too anal-retentive. - tgl 2001-02-14
|
||||
*
|
||||
* XXX in ALTER TABLE case, it'd be nice to look for duplicate
|
||||
@ -2691,7 +2691,7 @@ transformColumnType(CreateStmtContext *cxt, ColumnDef *column)
|
||||
* that the logic we use for determining forward references is
|
||||
* presently quite incomplete.
|
||||
*
|
||||
* SQL92 also allows constraints to make forward references, so thumb through
|
||||
* SQL also allows constraints to make forward references, so thumb through
|
||||
* the table columns and move forward references to a posterior alter-table
|
||||
* command.
|
||||
*
|
||||
|
Reference in New Issue
Block a user