DBMS Extensions
OpenSQL statements work with all Enterprise Access, EDBC, and DBMS servers. However, the underlying DBMS typically supports additional SQL statements and extensions. (For example, Ingres SQL includes statements that support rules and database events, and the DB2 UDB SQL CREATE TABLE statement includes extensions governing “editprocs.”)
OpenSQL provides the following methods for issuing DBMS‑specific statements from an OpenSQL application:
• Ingres SQL extensions
Extensions can be coded directly in an application. The embedded SQL or 4GL preprocessors recognize the extension and execute it properly. However, extended statements will fail if issued against a non‑Ingres DBMS.
• DIRECT EXECUTE IMMEDIATE
The DIRECT EXECUTE IMMEDIATE statement passes a statement to the underlying DBMS. OpenSQL does not attempt to process or translate the statement. The DIRECT EXECUTE IMMEDIATE statement can be used with any SQL statement that can be executed dynamically (statements that can be issued with a DBMS EXECUTE IMMEDIATE). Statements that return rows (for example, SELECT or FETCH) cannot be issued.
• Enterprise Access and EDBC with clause
Many Enterprise Access and EDBC products support WITH clauses that provide the ability to access DBMS extensions to database connection and Data Definition Language (DDL) SQL statements.
Last modified date: 08/14/2024