HP 3000 Manuals HP 3000 Manuals
ALLBASE/SQL Restrictions on the ODBC Grammar
The following table summarizes the ALLBASE/SQL restrictions on the ODBC
grammar:
Table 2-1. ODBC Grammar Statement Restrictions
---------------------------------------------------------------------------------------------
| | |
| Statement | Programming Considerations |
| | |
---------------------------------------------------------------------------------------------
| | |
| CREATE TABLE | UNIQUE|PRIMARY KEY must follow NOT NULL. |
| | |
---------------------------------------------------------------------------------------------
| | |
| DROP TABLE | ALLBASE does not provide CASCADE or |
| | RESTRICT. |
| | |
---------------------------------------------------------------------------------------------
| | |
| ODBC Procedure Extension | ALLBASE/SQL does not provide this |
| | extension. |
| | |
---------------------------------------------------------------------------------------------
| | |
| REVOKE | ALLBASE/SQL does not provide RESTRICT. |
| | |
---------------------------------------------------------------------------------------------
The following ODBC data types are not provided by ALLBASE/SQL:
* LONG VARCHAR
* BIT
* BIGINT
* ODBC Date Time Extension
* ODBC Outer Join Extension
* ODBC Scalar Function Extension
* TIMESTAMP
ALLBASE provides a DATETIME data type that is similar to TIMESTAMP.
ALLBASE/SQL does not implement optimistic locking. Optimistic locking
means that the DBMS does not lock data until just before an update is
made, thus improving concurrency because locks are not held for long.