MX 2.x)

Stmt1 = Prepare("select * from testing")

Success Success

Compiled plan is retrieved from MFC,

which is not correct because the table

datatype is changed when the MFC plan is

created.

Stmt1.execute()

Success Failure

MXOSRVR turned the SQL/MX CQD

recompilation_warnings ON. SQL/MX

throws SQL exception upon similarity

check failure and MXOSRVR drops the

invalid module file from the

/usr/tandem/sqlmx/USERMODULES

location.

Stmt1 = Prepare("select * from testing")

Success Success A new plan is created in the MFC location.

Stmt1.execute()

Success Success MFC statement works as expected.

When performing the above operations, the execute() call fails when an invalid module file is found in the MFC.

However, subsequent prepare() calls create a new module file. This open issue is similar to the driver side cache

present in the JDBC/MX T2 driver.

Scenario 2

When scalar functions such as, Sum(), Avg(), ABS(), Count() appear in the selected columns, the list of the SQL query

is not cached as MFC. For example,

SELECT sum(col1 + col2) from TAB WHERE col3 = ?

The scalar functions are supported in the INSERT, UPDATE, and DELETE queries and in the WHERE clause. For

example:

SELECT col1 from TAB WHERE sum(col2 + col3) = ?

Home

HP JDBC/MX 5.0 Driver for SQL/MX Programmer's Reference (540388-006)