|
Problem IT36235
|
Status: Closed |
PRECOMPILER STRIPS C STYLE COMMENTS FROM SQL, CANNOT USE INLINEDOPTIMIZATION GUIDELINES
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
The trouble is that the precompiler strips C-style comments from
the SQL. Therefore, OPTIMIZATION guidelines in the form of
c-style comments cannot be used. So given this statement
DECLARE c_sale CURSOR FOR SELECT * FROM t1 left join t2
/* */;
The actual statement sent to the compiler is just "SELECT * FROM
t1 left join t2". All embedded C-style comments can be
preserved since our SQL compiler already handles them since
v8.2. Currently, given this statement:
EXEC SQL select count(*) into :result from -- line comment
/*comment 1*/sysibm.sysdummy1 /* comment2 */;
The compiler currently sees:
10976 data DB2 UDB aps precompiler svc db2CompileSql api
(3.3.31.159.3.32)
pid 15793 tid 140296211830528 cpid 14 node 0 probe 32
bytes 108
Data1 (PD_TYPE_STRINGN,100) String with size:
select count(*) into : from
sysibm.sysdummy1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6 or higher *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* N/A *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to 11.5.6 or higher *
**************************************************************** |
| Comment |
See Error Description |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.03.2021
26.07.2021
26.07.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
