This chapter introduces you to the Pro*C/C++ Precompiler. You look at its role in developing application programs that manipulate Oracle data and find out what it enables your applications to do. This chapter contains the following topics:
An Oracle Precompiler is a programming tool that enables the user to embed SQL statements in a high-level source program. As Figure 1-1 shows, the precompiler accepts the source program as input, translates the embedded SQL statements into standard Oracle runtime library calls, and generates a modified source program that you can compile, link, and execute in the usual way.
The Oracle Pro*C/C++ Precompiler lets you use the power and flexibility of SQL in your application programs. A convenient, easy to use interface lets your application access Oracle directly.
Unlike many application development tools, Pro*C/C++ lets you create highly customized applications. For example, you can create user interfaces that incorporate the latest windowing and mouse technology. You can also create applications that run in the background without the need for user interaction.
Furthermore, Pro*C/C++ helps you fine-tune your applications. It allows close monitoring of resource use, SQL statement execution, and various runtime indicators. With this information, you can change program parameters for maximum performance.
Although precompiling adds a step to the application development process, it saves time. The precompiler, not you, translates each embedded SQL statement into calls to the Oracle runtime library (SQLLIB). The Pro*C/C++ precompiler also analyzes host variables, defines mappings of structures into columns, and, with SQLCHECK=FULL, performs semantic analysis of the embedded SQL statements.
If you want to access and manipulate Oracle data, you need SQL. Whether you use SQL interactively through SQL*Plus or embedded in an application program depends on the job at hand. If the job requires the procedural processing power of C or C++, or must be done on a regular basis, use embedded SQL.
SQL has become the database language of choice because it is flexible, powerful, and easy to learn. Being non-procedural, it lets you specify what you want done without specifying how to do it. A few English-like statements make it easy to manipulate Oracle data one row or many rows at a time.
CREATE, ALTER, and DROP database tables dynamically
SELECT, INSERT, UPDATE, and DELETE rows of data
COMMIT or ROLLBACK transactions
An extension to SQL, PL/SQL is a transaction processing language that supports procedural constructs, variable declarations, and robust error handling. Within the same PL/SQL block, you can use SQL and all the PL/SQL extensions.
The main advantage of embedded PL/SQL is better performance. Unlike SQL, PL/SQL provides the ability to group SQL statements logically and send them to Oracle in a block rather than one by one. This reduces network traffic and processing overhead.
See Also:Chapter 7, " Embedded PL/SQL" for information about embedding PL/SQL in Pro*C/C++ programs.
As Figure 1-2 shows, Pro*C/C++ offers many features and benefits, which help you to develop effective, reliable applications.
Writing applications in C or C++.
Following the ANSI/ISO standards for embedding SQL statements in a high-level language.
Taking advantage of dynamic SQL, an advanced programming technique that lets your Program accept or build any valid SQL statement at runtime.
Designing and developing highly customized applications.
Writing shared server process applications.
Automatically converting between Oracle internal datatypes and high-level language datatypes.
Improved performance by embedding PL/SQL transaction processing blocks in your application program.
Specifying useful precompiler options inline and on the command line and change their values during precompilation.
The use of datatype equivalencing to control the way Oracle interprets input data and formats output data.
Separately precompiling several program modules, then link them into one executable Program.
Complete checking of the syntax and semantics of embedded SQL data manipulation statements and PL/SQL blocks.
Concurrent access to Oracle databases on multiple nodes using Oracle Net.
The use of arrays as input and output program variables.
Conditionally precompiling sections of code in your host program so that it can run in different environments.
Direct interface with SQL*Forms through the use of user exits written in a high-level language.
Handling errors and warnings with the SQL Communications Area (SQLCA) and the WHENEVER or DO statement.
The use of an enhanced set of diagnostics provided by the Oracle Communications Area (ORACA).
Working with user-defined object types in the database.
The use of collections (varrays and nested tables) in the database.
The use of LOBs (Large Objects) in the database.
The use of National Character Set data stored in the database.
The use of OCI (Oracle Call Interface) functions in your program.
Pro*C/C++ is a full-featured tool that supports a professional approach to embedded SQL programming.
This section presents some questions that are frequently asked about Pro*C/C++, and about Oracle9i in relation to Pro*C/C++. The answers are more informal than the documentation in the rest of this Guide, but do provide references to places where you can find the reference material.
Here is a short description of VARCHARs:
|VARCHAR2||A kind of column in the database that contains variable-length character data. This is what Oracle calls an "internal datatype", because it is a possible column type.|
|VARCHAR||An Oracle "external datatype" (datatype code 9). You use this only if you are doing dynamic SQL Method 4, or datatype equivalencing.|
|This is a Pro*C/C++ "pseudotype" that you can declare as a host variable in your Pro*C/C++ program. It is actually generated by Pro*C/C++ as a struct, with a 2-byte length element, and a [n]-byte character array.|
No. Pro*C/C++ generates data structures and calls to its runtime library: SQLLIB.
SQLLIB is not externally documented, is unsupported, and might change from release to release. Also, Pro*C/C++ is an ANSI/ISO compliant product, that follows the standard requirements for embedded SQL.
SQLLIB is not an API. While it has user-callable functions, it is primarily a runtime library for the precompiler suite of languages.
If you need to do API coding for the database, either use the Oracle Call Interface, the client side API for the Oracle RDBMS, or mix OCI and Pro*C/C++.
Yes. See Chapter 12, "C++ Applications".
For example, I would d like to be able to input the name of a table in my SQL statements at runtime. But when I use host variables, I get precompiler errors.
In general, you can use host variables at anywhere in a SQL or PL/SQL, statement where expressions are allowed. See "Host Variable Referencing".
However, the following SQL statement, where table_name is a host variable, is illegal:
EXEC SQL SELECT ename,sal INTO :name, :salary FROM :table_name;
There are many options, but we can simplify. First of all, if you need compatibility with previous precompiler releases, and Oracle7, the safest thing to do is use VARCHAR[n] host variables. See "VARCHAR Variable Declaration".
The default datatype for all other character variables in Pro*C/C++ is CHARZ; see "CHARZ". Briefly, this means that you must null-terminate the string on input, and it is both blank-padded and null-terminated on output.
In release 8.0, the CHAR_MAP precompiler option was introduced to specify the default mapping of char variables. See "Precompiler Option CHAR_MAP".
If neither VARCHAR nor CHARZ works for your application, and you need total C-like behavior (null termination, absolutely no blank-padding), use the TYPE command and the C
typedef statement, and use datatype equivalencing to convert your character host variables to STRING. See "User-Defined Type Equivalencing". There is an example program that shows how to use the TYPE command starting on "Example Program: Using sqlvcp()".
Yes. When Pro*C/C++ binds an input or output host variable, it must know the length. When you use VARCHAR[n], or declare a host variable of type char[n], Pro*C/C++ knows the length from your declaration. But when you use a character pointer as a host variable, and use
malloc() to define the buffer in your program, Pro*C/C++ has no way of knowing the length.
On output you must not only allocate the buffer, but pad it out with some non-null characters, then null-terminate it. On input or output, Pro*C/C++ calls
strlen() for the buffer to get the length. See "Pointer Variables".
SPOOL is a special command used in SQL*Plus. It is not an embedded SQL command. See "Key Concepts of Embedded SQL Programming".
Each Oracle installation should have a
demo directory. If the directory is not there, or it does not contain the example programs, see your system or database administrator.
Compiling and linking are very platform specific. Your system-specific Oracle documentation has instructions on how to link a Pro*C/C++ application. On UNIX systems, there is a makefile called
proc.mk in the
demo directory. To link, say, the demo program sample1.pc, you would enter the command line
make -f proc.mk sample1
If you need to use special precompiler options, you can run Pro*C/C++ separately, then do the make. Or, you can create your own custom makefile. For example, if your program contains embedded PL/SQL code, you can enter
proc cv_demo userid=scott/tiger sqlcheck=semantics make -f proc.mk cv_demo
How does this work with the array interface?
Yes. However, for embedded SQL, you must use cursor variables.
No. You can use an older version of Pro*C or Pro*C/C++ with a newer version of the server, but you cannot use a newer version of Pro*C/C++ with an older version of the server.
For example, you can use release 2.2 of Pro*C/C++ with Oracle8i, but you cannot use release 8 of Pro*C/C++ with the Oracle7 server.
You are selecting a NULL into a host variable that does not have an associated indicator variable. This is not in compliance with the ANSI/ISO standards, and was changed beginning with Oracle7.
If possible, rewrite your program using indicator variables, and use indicators in future development. Indicator variables are described "Indicator Variables".
Alternatively, if precompiling with MODE=ORACLE and DBMS=V7 or V8, specify UNSAFE_NULL=YES on the command line (see "UNSAFE_NULL" for more information) to disable the ORA-01405 message.
No. There are some SQLLIB functions that you can call to get information about your program, or its data. The SQLLIB public functions are shown here:
|SQLLIB Public Functions||Description|
|SQLSQLDAAlloc()||Used to allocate a SQL descriptor array (SQLDA) for dynamic SQL Method 4. See "How is the SQLDA Referenced?".|
|SQLCDAFromResultSetCursor()||Used to convert a Pro*C/C++ cursor variable to an OCI cursor data area. See "New Names for SQLLIB Public Functions".|
|SQLSQLDAFree()||Used to free a SQLDA allocated using SQLSQLDAAlloc(). See "New Names for SQLLIB Public Functions".|
|SQLCDAToResultSetCursor()||Used to convert an OCI cursor data area to a Pro*C/C++ cursor variable. See "New Names for SQLLIB Public Functions".|
|SQLErrorGetText()||Returns a long error message. See "sqlerrm".|
|SQLStmtGetText()||Used to return the text of the most recently executed SQL statement. See "Obtaining the Text of SQL Statements".|
|SQLLDAGetNamed()||Used to obtain a valid Logon Data Area for a named connection, when OCI calls are used in a Pro*C/C++ program. See "New Names for SQLLIB Public Functions".|
|SQLLDAGetCurrent()||Used to obtain a valid Logon Data Area for the most recent connection, when OCI calls are used in a Pro*C/C++ program. See "New Names for SQLLIB Public Functions".|
|SQLColumnNullCheck()||Returns an indication of NULL status for dynamic SQL Method 4. See "Handling NULL/Not NULL Datatypes".|
|SQLNumberPrecV6()||Returns precision and scale of numbers. See "Extracting Precision and Scale".|
|SQLNumberPrecV7()||A variant of SQLNumberPrecV6(). See "Extracting Precision and Scale".|
|SQLVarcharGetLength()||Used for obtaining the padded size of a VARCHAR[n]. See "Find the Length of the VARCHAR Array Component".|
|SQLEnvGet()||Returns the OCI environment handle for a given SQLLIB runtime context. See "SQLEnvGet()".|
|SQLSvcCtxGet()||Returns the OCI service context for the database connection. See SQLSvcCtxGet().|
|SQLRowidGet()||Returns the universal ROWID of the last row inserted. See "SQLRowidGet()".|
|SQLExtProcError()||Returns control to PL/SQL when an error occurs in an external C procedure. See "SQLExtProcError()".|
In the preceding list, the functions are thread-safe SQLLIB public functions. Use these functions in all new applications. The names of the functions were changed for release 8.0, but the old names are still supported in Pro*C/C++. For more information about these thread-safe public functions (including their old names), see the table "SQLLIB Public Functions -- New Names".
As of 9.0.1 release, PRO*C/C++ will adopt a similar compatibility rule to OCI8- based applications. In particular, 9i PRO*C/C++ clients will support 8i Servers (184.108.40.206, V817x). This is subject to the same limitations that OCI8 imposes on backward compatibility. Such applications are limited to 8i-supported features. Any application using Oracle9i Server features will not be backward compatible.
Please report any issues with 9i PRO*C/C++ Client using 8i Server to Oracle support.