HPlogo ALLBASE/SQL Reference Manual: HP 9000 Computer Systems > Appendix D Standards Flagging Support

Non-Standard Syntax Rules

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

ALLBASE/SQL supports certain non-FIPS compliant extensions to the standard FIPS syntax rules listed in the ANSI SQL/89 document. The section number, the status rule number, and the FIPS SQL syntax rule for each non-FIPS compliant extension are listed below.

Note that in some cases no flagger warning is generated for these exceptions.

Table D-2 FIPS Syntax Rules and ALLBASE/SQL Exceptions

Section # Status Rule #FIPS SQL Syntax RuleALLBASE SQL Extension
5.3 SR 3All identifiers must be no longer than 18 characters.20 characters are allowed.
5.3 SR 4No identifier may be the same as a keyword, noting that all keywords are specified in upper case.Keywords are not case sensitive; keywords can be identifiers.
5.24 SR 8There may only be one DISTINCT per subquery, not including any nested subqueries.SELECT DISTINCT MAX (DISTINCT C1) FROM T1 is valid.
5.25 SR 5There may only be one DISTINCT per query, not including any subqueries in that query.SELECT DISTINCT MAX (DISTINCT C1) FROM T1 is valid.
5.25 SR 11bEvery <value expression> in the <select list> consists of a <column specification>, and no <column specification> appears more than once - updatability of a table/view.It is possible to update a regular column in a view that contains a virtual column. (No flagger warning is generated).
6.1DDL commands must be used in the CREATE SCHEMA statement.DDL commands can be issued outside of a CREATE SCHEMA statement.
8.6 SR 3bIn a FETCH, only an exact numeric column or expression may be FETCHed into an exact numeric host variable.Compatible data and truncation are allowed. (No flagger warning is generated).
8.6 SR 6aAn INSERT into a character column must be a character string of length less than or equal to the column.Compatible data and truncation are allowed. (No flagger warning is generated).
8.7 SR 6bAn INSERT into an exact numeric column must be an exact numeric value.Compatible data and truncation are allowed. (No flagger warning is generated).
8.10 SR 4bIn a SELECT ... INTO, only an exact numeric column or expression may be selected into an exact numeric host variable.Compatible data and truncation are allowed. (No flagger warning is generated).
8.11 SR 8bAn UPDATE ... WHERE CURRENT of a character column must be a character string of length less than or equal to the column.Compatible data and truncation are allowed. (No flagger warning is generated).
8.11 SR 8cIn an UPDATE ... WHERE CURRENT, only an exact numeric value or NULL may be put in an exact numeric column.Compatible data and truncation are allowed. (No flagger warning is generated).
8.12 SR 6bA searched UPDATE of a character column must be a character string of length less than or equal to the column.Compatible data and truncation are allowed. (No flagger warning is generated).
8.12 SR 6cIn a searched UPDATE, only an exact numeric value (or NULL) may be put in an exact numeric column.Compatible data and truncation are allowed. (No flagger warning is generated).
9.2 SR 1bcCOLON has to precede the host identifier in WHENEVER.The absence of COLON in the front of the label is allowed.

 

NOTE: There is one more exception to the syntax rules listed above:

No flagger warning is generated for a second reference to a non-standard extension within the first non-standard reference.

Feedback to webmaster