My understanding is that for non-DB2 sqlj, this is true: sqlj
statements are turned into jdbc calls at run time. However, for
sqlj, when you run 'db2profc', a flag is set in the '.ser' file
causes the program to go look for the corresponding db2 package
sql). Yet, even if your on DB2 for os390, if this flag is not
then it will do run-time jdbc calls. I think this is a
portability/compatibility thing. The ability to do 'real' static
via sqlj is one of the advantages to using DB2 as your dbms behind
java apps. I dont have the book you referenced, but it sounds like
is in error or at least needs clarification in this area.
DB2 Systems Programmer
From: [login to unmask email] [mailto:[login to unmask email]On Behalf
Sent: Wednesday, December 19, 2001 21:25
To: [login to unmask email]
Subject: [DB2-L] Does SQLJ provide a static SQL interface ?
Till now I'm under the impression that SQLJ is a static SQL
no statement preparation occurs at run time. But the following
the book "DB2 High Performance Design and Tuning by Yevich &
doubt on this impression. The text is on page 580 :
"But we need to focus on the fact that SQLJ really is JDBC. DB2
provide statement caching to help with all this dynamic SQL that
frequently called and executes in a very short time; it
static performance. It allows the reuse of dynamically prepared
plan, reducing dynamic PREPARE overhead."
Would anyone please clarify this.
DB2-L webpage at http://www.ryci.com/db2-l.
owners of the list
visit the DB2-L webpage at http://www.ryci.com/db2-l.
the list can