Re: Help with Pro*C compilation
From: <rwoods01_at_interserv.com>
Date: 1995/10/01
Message-ID: <44kuj9$jqa_at_data.interserv.net>#1/1
and conditionally execute that. This way you can still use SQLCHECK=FULL which is required for embedded PL/SQL and yet get the precompiler to ignore those statements that may or may not be used.
Date: 1995/10/01
Message-ID: <44kuj9$jqa_at_data.interserv.net>#1/1
May I suggest you not hardcode the potentially bogus SQL statements as:
EXEC SQL select .... from garbage where .....; to:
varchar sqlstmt[100]; strcpy ( sqlstmt.arr, "EXEC SQL select .... from garbage where .....;" ); sqlstmt.len = strlen ( sqlstmt.arr ); EXEC SQL PREPARE ..... EXEC SQL DECLARE .....
and conditionally execute that. This way you can still use SQLCHECK=FULL which is required for embedded PL/SQL and yet get the precompiler to ignore those statements that may or may not be used.
Rich Woods
Oracle Worldwide Customer Support
Received on Sun Oct 01 1995 - 00:00:00 CET