Using Embedded SQL with ODBC
Contents
- ODBC SQL
Support - ODBC Name
qualification - ODBC
SQL functions - ODBC
Using escape clauses - ODBC
Transaction management statements - ODBC
Using CONNECT, DISCONNECT, COMMIT, and ROLLBACK - ODBC
Performance and locking - ODBC
Non-cursor statements - ODBC
DELETE, INSERT, and UPDATE - ODBC
SELECT - ODBC Cursor
statements - ODBC
Retrieval using cursors - ODBC
FETCH NEXT - ODBC
FETCH FIRST, FETCH PRIOR, and FETCH LAST - ODBC
Update - ODBC
Database stored procedures - ODBC
Retrieval - ODBC
DECLARE and EXECUTE - ODBC
DECLARE and EXECUTE with PBNewSPInvocation - ODBC
FETCH - ODBC
CLOSE - ODBC
EXECUTE - ODBC Using
database stored procedures in DataWindow objects
About this chapter
When you create scripts for a PowerBuilder application, you can use
embedded SQL statements in the script to perform operations on the database.
The features supported when you use embedded SQL depend on the DBMS to which
your application connects.
Overview
When you use the ODBC interface to connect to a backend database, you
can use embedded SQL in your scripts.
You can embed the following types of SQL statements in scripts and
user-defined functions if the ODBC driver you are using and the backend DBMS
you are accessing supports this functionality. (Not all backend databases
support cursor statements and database stored procedures.)
-
Transaction management statements
-
Non-cursor statements
-
Cursor statements
-
Database stored procedures
ODBC API
The ODBC interface uses the ODBC application programming interface
(API) to interact with the backend database.
When you use embedded SQL, PowerBuilder makes the required calls to
the backend database. Therefore, you do not need to know anything about the
ODBC API to use embedded SQL with PowerBuilder.
See also