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