public class ConnectJDBCDataStoreHelper
extends com.ibm.websphere.rsadapter.DataDirectDataStoreHelper
ConnectJDBCDataStoreHelper is a DataStoreHelper implementation
customized for the DataDirect Technologies Connect JDBC driver.
SQLException mappings specific to the ConnectJDBCDataStoreHelper
are the following:
| Error Code | SQL State | PortableSQLException subclass |
|---|---|---|
| 230 | StaleConnectionException.class | |
| 2627 | DuplicateKeyException.class | |
| 2217 | StaleConnectionException.class | |
| 2251 | StaleConnectionException.class | |
| 2306 | StaleConnectionException.class | |
| 2310 | StaleConnectionException.class | |
| 2311 | StaleConnectionException.class | |
| 08000 | StaleConnectionException.class | |
| 08002 | StaleConnectionException.class | |
| 08004 | StaleConnectionException.class | |
| 08007 | StaleConnectionException.class | |
| 40003 | Void.class | |
| S1000 | Void.class |
customDefinedWasDefaultIsoLevel, defaultQueryTimeout, EOLN, genErrorMap, resBundle, tranErrorListCLOUDSCAPE_HELPER, CLOUDSCAPE_NETWORK_SERVER_HELPER, CONNECTJDBC_HELPER, CUSTOM_HELPER, DATADIRECT_HELPER, DB2_390_HELPER, DB2_390_LOCAL_HELPER, DB2_400_HELPER, DB2_HELPER, DB2_UNIVERSAL_HELPER, DERBY_HELPER, DERBY_NETWORK_SERVER_HELPER, FIRST_TIME_CALLED, GENERIC_HELPER, INFORMIX_HELPER, INFORMIX_JCC_HELPER, MSSQL_HELPER, ORACLE_10G_HELPER, ORACLE_11G_HELPER, ORACLE_HELPER, POTENTIAL_DEADLOCK, POTENTIAL_LOST_UPDATE, PROXY_DS_HELPER, SEQUELINK_HELPER, SUBJECT, SYBASE_HELPER, SYBASE11_HELPER, TX_REPEATABLE_READ_FORUPDATE, TX_SERIALIZABLE_FORUPDATE, UNDEFINED_HELPER, UNDEFINED_ISOLATOIN_LEVEL, UPDATE_ON_READONLY| Constructor and Description |
|---|
ConnectJDBCDataStoreHelper(java.util.Properties props)
This
ConnectJDBCDataStoreHelper constructor creates a new
ConnectJDBCDataStoreHelper based on the DataStoreHelper
properties provided. |
| Modifier and Type | Method and Description |
|---|---|
boolean |
doConnectionCleanup(java.sql.Connection conn)
This method is used to clean up a connection before it is returned to the connection
pool for later reuse.
|
void |
doStatementCleanup(java.sql.PreparedStatement stmt)
This method cleans up a statement before the statement is returned to the statement
cache.
|
int |
getIsolationLevel(AccessIntent intent)
This method determines the transaction isolation level based on the specified
AccessIntent. |
int |
getResultSetConcurrency(AccessIntent intent)
This method determines the result set concurrency based on the specified
AccessIntent. |
boolean |
isDuplicateKey(java.sql.SQLException sqlX)
The application server invokes this method to determine whether or not the specified
error indicates a duplicate key violation.
|
java.lang.String |
showLockInfo(java.util.Properties props)
This method returns lock information for Microsoft SQL Server.
|
doConnectionSetup, findMappingClass, getPrintWriter, isDataDirectExp, setUserDefinedMapcalcPartitionNumber, doConnectionCleanupPerCloseConnection, doConnectionCleanupWithValidCheck, doConnectionSetupPerGetConnection, doConnectionSetupPerTransaction, getLockType, getMetaData, getPasswordForUseWithTrustedContextWithAuthentication, getResultSetType, getXAExceptionContents, hasLostUpdateOrDeadLockOccurred, isBatchUpdateSupportedWithAccessIntent, isConnectionError, isTransientConnectionError, mapException, modifyXAFlag, setConfigpublic ConnectJDBCDataStoreHelper(java.util.Properties props)
ConnectJDBCDataStoreHelper constructor creates a new
ConnectJDBCDataStoreHelper based on the DataStoreHelper
properties provided. All implementations inheriting from a data store helper
must supply this same list of properties to their super class by invoking the
constructor of their super class with the list of properties.props - DataStoreHelper properties.public boolean doConnectionCleanup(java.sql.Connection conn)
throws java.sql.SQLException
This method is used to clean up a connection before it is returned to the connection
pool for later reuse. WebSphere automatically resets all standard connection
properties (fields for which getters and setters are defined on
java.sql.Connection).
This method may be used to reset other properties proprietary to a specific
JDBC driver/database and do whatever else is necessary to prepare the connection for
reuse.
A DataStoreHelper is permitted to use the provided connection to create
and execute statements for the purpose of cleaning up the connection. Any statements
created within the doConnectionCleanup method must be explicitly closed
within the doConnectionCleanup method. The
doConnectionCleanup method must never close the
connection being cleaned up.
If any standard connection properties are modified in this method, a value of true must be returned, indicating to WebSphere that at least one standard connection property was modified. A value of false is returned only if no standard connection properties were modified.
ConnectJDBCDataStoreHelper resets the network timeout to 0.
doConnectionCleanup in interface DataStoreHelperdoConnectionCleanup in class GenericDataStoreHelperconn - the connection to attempt to clean up.java.sql.SQLException - If an error occurs while cleaning up the connection.public void doStatementCleanup(java.sql.PreparedStatement stmt)
throws java.sql.SQLException
This method cleans up a statement before the statement is returned to the statement cache. This method is called only for statements that will be cached. It is called only if at least one of the following statement properties has changed,
ConnectJDBCDataStoreHelper resets all of the statement properties listed above
except for the cursorName property.
The following operations do not need to be included in the statement cleanup since they are automatically performed by WebSphere when caching statements,
setFetchSize(0)clearParameters()clearWarnings()A helper class implementing this method may choose to do additional cleanup for the statement. However, this should never include closing the statement, since the statement is intended to be cached.
doStatementCleanup in interface DataStoreHelperdoStatementCleanup in class GenericDataStoreHelperstmt - the PreparedStatement.java.sql.SQLException - if an error occurs cleaning up the statement.public int getResultSetConcurrency(AccessIntent intent) throws javax.resource.ResourceException
AccessIntent.
ConnectJDBCDataStoreHelper returns
java.sql.ResultSet.CONCUR_UPDATABLE if the access type of the
AccessIntent is AccessIntent.ACCESS_TYPE_UPDATE and the
concurrency control is AccessIntent.CONCURRENCY_CONTROL_PESSIMISTIC and
the update lock hint is either
AccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE or
AccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_NONE. In all other cases,
java.sql.ResultSet.CONCUR_UPDATABLE is returned.getResultSetConcurrency in interface DataStoreHelpergetResultSetConcurrency in class com.ibm.websphere.rsadapter.DataDirectDataStoreHelperintent - An AccessIntent.java.sql.ResultSet.javax.resource.ResourceException - If a result set concurrency cannot be determined
from the AccessIntent.AccessIntent,
ResultSetpublic int getIsolationLevel(AccessIntent intent) throws javax.resource.ResourceException
AccessIntent.
If the AccessIntent parameter is null, a default value is returned
that is appropriate for the database backend. The default transaction isolation level
for ConnectJDBCDataStoreHelper is
Connection.TRANSACTION_REPEATABLE_READ.
In the case where an AccessIntent is specified,
ConnectJDBCDataStoreHelper computes the transaction isolation level as follows:
If the concurrency control is
AccessIntent.CONCURRENCY_CONTROL_OPTIMISTIC then a transaction isolation
level of Connection.TRANSACTION_READ_COMMITTED is returned.
If the concurrency control is
AccessIntent.CONCURRENCY_CONTROL_PESSIMISTIC and the access type is
AccessIntent.ACCESS_TYPE_READ then a transaction isolation level of
Connection.TRANSACTION_REPEATABLE_READ is returned.
If the concurrency control is
AccessIntent.CONCURRENCY_CONTROL_PESSIMISTIC and the access type is
AccessIntent.ACCESS_TYPE_UPDATE then the transation isolation level is
determined from the following table based on the pessimistic update lock hint.
| pessimistic update lock hint | transaction isolation level |
|---|---|
AccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_NONEAccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_WEAKEST_LOCK_AT_LOAD |
Connection.TRANSACTION_REPEATABLE_READ |
AccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_NOCOLLISION |
Connection.TRANSACTION_READ_COMMITTED |
AccessIntent.PESSIMISTIC_UPDATE_LOCK_HINT_EXCLUSIVE |
Connection.TRANSACTION_SERIALIZABLE |
getIsolationLevel in interface DataStoreHelpergetIsolationLevel in class com.ibm.websphere.rsadapter.DataDirectDataStoreHelperintent - An AccessIntentAccessIntent.javax.resource.ResourceException - If a transaction isolation level cannot be determined
from the AccessIntent.AccessIntent,
Connectionpublic boolean isDuplicateKey(java.sql.SQLException sqlX)
The application server invokes this method to determine whether or not the specified error indicates a duplicate key violation. The method is invoked regardless of the data source's error detection model.
isDuplicateKey in interface DataStoreHelperisDuplicateKey in class GenericDataStoreHelpersqlX - the error.public java.lang.String showLockInfo(java.util.Properties props)
throws java.lang.Exception
This method returns lock information for Microsoft SQL Server. The
props parameter can include the following properties:
showLockInfo in class com.ibm.websphere.rsadapter.DataDirectDataStoreHelperprops - properties containing information needed to connect to the database.java.lang.Exception - if an error occurs while collecting the lock information.