SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide (H06.22+, J06.11+)

Considerations for upgrading to SQL/MX Release
3.0
HP NonStop SQL/MX 2.3.x to SQL/MX 3.0 Database and Application Migration Guide—666210-002
2-13
Recommendations for Migrating to SQL/MX Release
3.x
The following is an application code sample:
conn.setReadOnly(true);
String sql = "select ORDER_AMT from ORDERTBL where ORDER_QTY
> 100 ";
stmt=conn.createStatement();
ResultSet rss = stmt.executeQuery(sql);
conn.setReadOnly(false);
stmt.executeUpdate("delete from ORDERTBL");
Set the transaction access mode to read-only.
Executing the SELECT statement starts a read-only transaction.
Change the transaction access mode to read-write.
Subsequently, executing a DELETE operation (WRITE operation) returns SQL error
8551 and file system error 757.
These errors are not returned in SQL/MX Release 2.x.
Recommendations for Migrating to SQL/MX Release 3.x

While migrating applications from SQL/MX Release 2.x to 3.x, ensure that the
applications do not perform WRITE operations in read-only transactions. If you are
migrating from other databases to SQL/MX Release 3.x, you must ensure that the
new applications do not contain any of the scenarios described in Example1 and
Example2.

For JDBC T4 applications, use JDBC T4 3.x driver version T1249V326^AMU or
later.

For ODBC and JDBC T4 applications, HP recommends that you do not use the
connection attribute
setReadOnly. If this attribute is used, set it to FALSE. If set
to TRUE, follow these guidelines: