|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
This interface defines the Oracle extensions to the standard JDBC interface
java.sql.Connection
. You can use
java.sql.Connection
in your application where you do not make
use of the Oracle extensions. However, when your application uses the Oracle
extensions to java.sql.Connection
you must use
oracle.jdbc.OracleConnection
.
OracleConnection
extends standard JDBC connection
functionality to create and return Oracle statement objects, set flags and
options for Oracle performance extensions, and support type maps for Oracle
objects.
Basic example : Once you connect to the database and, in the process,
create your Connection
object (see OracleDriver), the next step is to create a
Statement
object. The createStatement
method of
your JDBC Connection
object returns an object of the JDBC
Statement type.
Here is an example of how to create the
Statement
object (conn
being your connection
object):
Statement stmt = conn.createStatement();
Note that there is nothing Oracle-specific about this statement; it follows standard JDBC syntax.
Field Summary | |
static int |
CACHE_SIZE_NOT_SET
|
static int |
DATABASE_CLOSED
|
static int |
DATABASE_NOTOK
|
static int |
DATABASE_OK
Define return values for pingDatabase api |
static int |
DATABASE_TIMEOUT
|
static java.lang.String |
dataSizeBytes
|
static java.lang.String |
dataSizeChars
|
static java.lang.String |
dataSizeUnitsPropertyName
|
Fields inherited from class java.sql.Connection |
TRANSACTION_NONE,
TRANSACTION_READ_COMMITTED,
TRANSACTION_READ_UNCOMMITTED,
TRANSACTION_REPEATABLE_READ,
TRANSACTION_SERIALIZABLE |
Method Summary | |
java.sql.Connection |
_getPC()
Return the underlying physical connection if this is a logical connection. |
void |
archive(int mode,
int aseq,
java.lang.String acstext)
Deprecated. This method will be removed in a future version. |
void |
assertComplete()
Deprecated. Ultra is not supported anymore. This method will be removed in a future version. |
boolean |
getAutoClose()
The driver is always in auto-close mode. |
java.sql.CallableStatement |
getCallWithKey(java.lang.String key)
getCallWithKey Searches the explicit cache for a match on key. |
boolean |
getCreateStatementAsRefCursor()
Retrieves the current setting of the createStatementAsRefCursor flag which you can set with the
setCreateStatementAsRefCursor method. |
int |
getDefaultExecuteBatch()
Retrieves the overall connection batch value of this connection. |
int |
getDefaultRowPrefetch()
Retrieves the value of row prefetch for all statements associated with this connection and created after this value was set. |
java.lang.Object |
getDescriptor(java.lang.String sql_name)
Gets a Descriptor object corresponding to a sql type. |
boolean |
getExplicitCachingEnabled()
getExplicitCachingEnabled Returns true if the explicit cache is currently enabled, false otherwise. |
boolean |
getImplicitCachingEnabled()
getImplicitCachingEnabled Returns true if the implicit cache is currently enabled, false otherwise. |
boolean |
getIncludeSynonyms()
Checks whether or not synonyms information is included in DatabaseMetaData.getColumns . |
java.lang.Object |
getJavaObject(java.lang.String sql_name)
Deprecated. |
java.util.Properties |
getProperties()
Determines the connection properties. |
boolean |
getRemarksReporting()
Checks whether or not a call of getTables or
getColumns of the DatabaseMetaData interface will
report the REMARKS column. |
boolean |
getRestrictGetTables()
Gets the restriction status of the returned data in DatabaseMetaData.getTables . |
java.lang.String |
getSessionTimeZone()
Obtain Oracle session time zone region name. |
java.lang.String |
getSQLType(java.lang.Object obj)
Deprecated. |
int |
getStatementCacheSize()
getStatementCacheSize Returns the current size of the application cache. |
java.sql.PreparedStatement |
getStatementWithKey(java.lang.String key)
getStatementWithKey Searches the explicit cache for a match on key. |
int |
getStmtCacheSize()
Deprecated. Use getStatementCacheSize() instead. |
short |
getStructAttrCsId()
Obtain the Oracle identifier of the character set used in STRUCT attributes. |
boolean |
getSynchronousMode()
Deprecated. Ultra is not supported anymore. This method will be removed in a future version. |
java.lang.String |
getUserName()
Gets the user name of the current connection. |
boolean |
getUsingXAFlag()
Deprecated. |
boolean |
getXAErrorFlag()
Deprecated. |
boolean |
isLogicalConnection()
Method that returns a boolean indicating whether its a logical connection or not. |
java.lang.Object |
openJoltConnection(java.lang.String apiName,
short major,
short minor)
Deprecated. Ultra is not supported anymore. This method will be removed in a future version. |
void |
oracleReleaseSavepoint(OracleSavepoint savepoint)
Removes the given OracleSavepoint object from the current
transaction. |
void |
oracleRollback(OracleSavepoint savepoint)
Undoes all changes made after the given OracleSavepoint
object was set. |
OracleSavepoint |
oracleSetSavepoint()
Creates an unnamed savepoint in the current transaction and returns the new OracleSavepoint object that
represents it. |
OracleSavepoint |
oracleSetSavepoint(java.lang.String name)
Creates a savepoint with the given name in the current transaction and returns the new OracleSavepoint object that
represents it. |
int |
pingDatabase(int timeOut)
ping Database |
java.sql.CallableStatement |
prepareCallWithKey(java.lang.String key)
Deprecated. This is same as prepareCall, except if a Callable Statement with the given KEY exists in the Cache, then the statement is returned AS IT IS when it was closed and cached with this KEY. An object returned from the Cache based on Key will have its state set to "KEYED". If no such Callable Statement is found, then null is returned. Key cannot be null. |
java.sql.PreparedStatement |
prepareStatementWithKey(java.lang.String key)
Deprecated. This is same as prepareStatement, except if a Prepared Statement with the given KEY exists in the Cache, then the statement is returned AS IT IS when it was closed and cached with this KEY. An object returned from the Cache based on Key will have its state set to "KEYED". If no such Prepared Statement is found, a null is returned. Key cannot be null. |
void |
purgeExplicitCache()
purgeExplicitCache Removes all existing statements from the explicit cache, after which it will be empty. |
void |
purgeImplicitCache()
purgeImplicitCache Removes all existing statements from the implicit cache, after which it will be empty. |
void |
putDescriptor(java.lang.String sql_name,
java.lang.Object desc)
Store the Object Descriptor for later usage. |
void |
registerApiDescription(java.lang.String apiName,
short major,
short minor,
java.lang.String className)
Deprecated. Ultra is not supported anymore. This method will be removed in a future version. |
void |
registerSQLType(java.lang.String sql_name,
java.lang.Class java_class)
Deprecated. |
void |
registerSQLType(java.lang.String sql_name,
java.lang.String java_class_name)
Deprecated. |
void |
registerTAFCallback(OracleOCIFailover cbk,
java.lang.Object obj)
Register an application TAF Callback instance that will be called when an application failover occurs. |
void |
setAutoClose(boolean autoClose)
We are always in auto-close mode. |
void |
setCreateStatementAsRefCursor(boolean value)
When this is set to true , any new statements created from this
connection will be created as a REF CURSOR . |
void |
setDefaultExecuteBatch(int batch)
Sets a default batch value for the Oracle update batching model (the default value is 1). |
void |
setDefaultRowPrefetch(int value)
Sets the value of row prefetch for all statements associated with this connection and created after this value was set. The row-prefetching feature associates an integer row-prefetch setting with a given statement object. |
void |
setExplicitCachingEnabled(boolean cache)
setExplicitCachingEnabled Enables or disables the explicit cache. |
void |
setImplicitCachingEnabled(boolean cache)
setImplicitCachingEnabled Enables or disables the implicit cache. |
void |
setIncludeSynonyms(boolean synonyms)
Turns on or off retrieval of synonym information in DatabaseMetaData. |
void |
setRemarksReporting(boolean reportRemarks)
Turns on or off the reporting of the REMARKS columns by the getTables and getColumns calls of the
DatabaseMetaData interface.
The DatabaseMetaData calls getTables and getColumns
are extremely slow if the REMARKS column has to be reported as this
necessitates an expensive outer join so by default the JDBC driver does not report
the REMARKS columns.
You can turn the reporting of REMARKS on by passing a true argument
to this method. |
void |
setRestrictGetTables(boolean restrict)
Turns on or off the restriction of the returned data in DatabaseMetaData.getTables.
DatabaseMetaData.getTables will return information about
all accessible tables, views, and synonyms. |
void |
setSessionTimeZone(java.lang.String regionName)
Set the session time zone. |
void |
setStatementCacheSize(int size)
setStatementCacheSize Specifies the size of the size of the application cache (which will be used by both implicit and explicit caching). |
void |
setStmtCacheSize(int size)
Deprecated. Use setStatementCacheSize() instead. |
void |
setStmtCacheSize(int size,
boolean clearMetaData)
Deprecated. Use setStatementCacheSize() instead. |
void |
setSynchronousMode(boolean isSynchronous)
Deprecated. Ultra is not supported anymore. This method will be removed in a future version. |
void |
setUsingXAFlag(boolean value)
Deprecated. |
void |
setWrapper(OracleConnection wrapper)
Set the wrapping object |
void |
setXAErrorFlag(boolean value)
Deprecated. |
void |
shutdown(int mode)
Deprecated. This method will be removed in a future version. |
void |
startup(java.lang.String startup_str,
int mode)
Deprecated. This method will be removed in a future version. |
OracleConnection |
unwrap()
Return the wrapping object if any else null |
Methods inherited from interface java.sql.Connection |
clearWarnings,
close,
commit,
createStatement,
createStatement,
getAutoCommit,
getCatalog,
getMetaData,
getTransactionIsolation,
getTypeMap,
getWarnings,
isClosed,
isReadOnly,
nativeSQL,
prepareCall,
prepareCall,
prepareStatement,
prepareStatement,
rollback,
setAutoCommit,
setCatalog,
setReadOnly,
setTransactionIsolation,
setTypeMap |
Field Detail |
public static final int DATABASE_OK
public static final int DATABASE_CLOSED
public static final int DATABASE_NOTOK
public static final int DATABASE_TIMEOUT
public static final java.lang.String dataSizeUnitsPropertyName
public static final java.lang.String dataSizeBytes
public static final java.lang.String dataSizeChars
public static final int CACHE_SIZE_NOT_SET
Method Detail |
public void archive(int mode, int aseq, java.lang.String acstext) throws java.sql.SQLException
public boolean getAutoClose() throws java.sql.SQLException
public int getDefaultExecuteBatch()
The batch value from the connection is used for all prepared statements
associated with this connection. A different batch value can also be
defined for individual prepared statements. This can be done by using
OraclePreparedStatement.setExecuteBatch
, which will override
the default value provided from the connection. Therefore, the batch value
returned by this getDefaultExecuteBatch
entrypoint is valid
for prepared statements for which you have not defined a different batch
value.
The following code retrieves the default batch value of the connection
conn
.
Integer batch_val = ((OracleConnection)conn).getDefaultExecuteBatch();
public int getDefaultRowPrefetch()
The row-prefetching feature associates an integer row-prefetch setting
with a given statement object. JDBC fetches that number of rows at a time
from the database during the query. That is, JDBC will fetch N rows that
match the query criteria and bring them all back to the client at once,
where N is the prefetch setting. Then, once your next
calls
have run through those N rows, JDBC will go back to fetch the next N rows
that match the criteria.
You can set the number of rows to prefetch for a particular Oracle
statement (any type of statement). You can also reset the default number of
rows that will be prefetched for all statements in your connection with the
setDefaultRowPrefetch
method. Therefore, the row prefetch
value returned by this getDefaultRowPrefetch
entrypoint is
valid for statements for which you have not defined a different row
prefetch value.
The default number of rows to prefetch to the client is 10.
Example where conn
is your connection object:
//Get the default row-prefetch setting for this connection
int defRowPref = ((OracleConnection)conn).getDefaultRowPrefetch();
public java.lang.Object getDescriptor(java.lang.String sql_name)
sql_name
- the sql typepublic boolean getIncludeSynonyms()
DatabaseMetaData.getColumns
.
By default and for performance reasons it won't but you can change this with the
setIncludeSynonyms
method.DatabaseMetaData.getColumns
will report
information if a table synonym is passed in, and false otherwisepublic boolean getRestrictGetTables()
DatabaseMetaData.getTables
.
The default behavior is to return information about all synonyms,
including those which do not point to accessible tables or views. But you
can change this with the setRestrictGetTables
method.
DatabaseMetaData.getTables
is restricted, and false otherwisepublic java.lang.Object getJavaObject(java.lang.String sql_name) throws java.sql.SQLException
public boolean getRemarksReporting()
getTables
or
getColumns
of the DatabaseMetaData
interface will
report the REMARKS
column.
By default and for performance reasons it won't (it will return
null
) but you can change this with the
setRemarksReporting
method.
DatabaseMetaData
calls getTables
and getColumns
will report the REMARKS column and false otherwisepublic java.lang.String getSQLType(java.lang.Object obj) throws java.sql.SQLException
public int getStmtCacheSize()
public short getStructAttrCsId() throws java.sql.SQLException
public java.lang.String getUserName() throws java.sql.SQLException
Example where conn
is your connection object:
String UserName = ((OracleConnection)conn).getUserName();
public boolean getUsingXAFlag()
UsingXA
flag which the driver sets to
true
when using XA to manage distributed transactions. If you
are not using distributed transactions with the XA library, the value of
the UsingXA
flag will be false
.true
when using XA to manage distributed transactions
and false
otherwise.public boolean getXAErrorFlag()
XAError
flag which is used with
distributed transactions.
When using distributed transactions with an XA library, you can ask the
driver to raise exception when doing anything that might require a
transaction. To do so, set the value of the XAError
flag to
true
with the method setXAErrorFlag
.
The default value is false
.
public int pingDatabase(int timeOut) throws java.sql.SQLException
public void putDescriptor(java.lang.String sql_name, java.lang.Object desc) throws java.sql.SQLException
sql_name
- the sql typedesc
- the Object Descriptor associatedpublic void registerSQLType(java.lang.String sql_name, java.lang.Class java_class) throws java.sql.SQLException
public void registerSQLType(java.lang.String sql_name, java.lang.String java_class_name) throws java.sql.SQLException
public void setAutoClose(boolean autoClose) throws java.sql.SQLException
autoClose
- the boolean valuepublic void setDefaultExecuteBatch(int batch) throws java.sql.SQLException
You can reduce the number of round trips to the database, thereby
improving application performance, by grouping multiple
UPDATE
, DELETE
, or INSERT
statements
into a single "batch" and having the whole batch sent to the database and
processed in one trip. To do this, you can either use the Oracle update
batching model or the batch updates of the Sun Microsystems JDBC 2.0
specification. The standard model is a manual, explicit model (there is no
batch value) whereas the Oracle model is an implicit model.
Note: It is important to be aware that you cannot mix theses models. In any single application, you can use the syntax of one model or the other, but not both. The Oracle JDBC driver will throw exceptions when you mix these syntaxes.
The Oracle update batching feature associates a batch value (limit) with
each prepared statement object (this way the driver knows in advance how
many operations will be batched). With Oracle update batching, instead of
the JDBC driver executing a prepared statement each time its
executeUpdate
method is called, the driver adds the statement
to a batch of accumulated execution requests. The driver will pass all the
operations to the database for execution once the batch value is
reached. For example, if the batch value is 10, then each batch of 10
operations will be sent to the database and processed in one trip.
The following code sets the default batch value to 20 for
all prepared statement objects associated with the conn
connection object:
((OracleConnection)conn).setDefaultExecuteBatch(20);
Even though this sets the default batch value for all the prepared
statements of the connection, you can override it by calling
setDefaultBatch
on individual Oracle prepared statements.
The connection batch value will apply to statement objects created after
this batch value was set.
Note that instead of calling setDefaultExecuteBatch
, you
can set the defaultBatchValue
Java property if you use a Java
Properties
object in establishing the connection.
Types of Statements Supported. As implemented by Oracle, update batching is intended for use with prepared statements, when you are repeating the same statement with different bind variables. Be aware of the following:
Note
that because Oracle update batching is vendor-specific, you must actually
use (or cast to) OraclePreparedStatement
objects, not general
PreparedStatement
objects.
UPDATE
, INSERT
, or
DELETE
operations. Executing a batch that includes an
operation that attempts to return a result set will cause an exception.
Note that with standard update batching model, you can use either
standard PreparedStatement
, CallableStatement
,
and Statement
objects, or Oracle-specific
OraclePreparedStatement
, OracleCallableStatement
,
and OracleStatement
objects.
Oracle Update Batching Characteristics and Limitations
sendBatch
method of an Oracle prepared statement in any of the
following circumstances: 1) the connection receives a COMMIT
request, either as a result of invoking the commit
method or
as a result of auto-commit mode; 2) the statement receives a
close
request; or 3) the connection receives a
close
request.
COMMIT
request, statement close, or
connection close has no effect on a pending batch if you use standard
update batching--only if you use Oracle update batching.
batch
- your default batch value (default is 1)public void setDefaultRowPrefetch(int value) throws java.sql.SQLException
The row-prefetching feature associates an integer row-prefetch setting with
a given statement object. JDBC fetches that number of rows at a time from
the database during the query. That is, JDBC will fetch N rows that match
the query criteria and bring them all back to the client at once, where N
is the prefetch setting. Then, once your next
calls have run
through those N rows, JDBC will go back to fetch the next N rows that match
the criteria.
You can set the number of rows to prefetch for a particular Oracle statement (any type of statement) but this method allows you to reset the default number of rows that will be prefetched for all statements in your connection. The default number of rows to prefetch to the client is 10.
Use the setDefaultRowPrefetch
method to set the default number of
rows to prefetch, passing in an integer that specifies the desired default. If you
want to check the current setting of the default, then use the
getDefaultRowPrefetch
method. This method returns an integer.
Example where conn
is your connection object:
//Set the default row-prefetch setting for this connection to 7
((OracleConnection)conn).setDefaultRowPrefetch(7);
Note 1 : A statement object receives the default row-prefetch setting from the associated connection at the time the statement object is created. Subsequent changes to the connection's default row-prefetch setting have no effect on the statement's row-prefetch setting.
Note 2 : If a column of a result set is of datatype LONG or LONG RAW (that is, the streaming types), JDBC changes the statement's row-prefetch setting to 1, even if you never actually read a value of either of those types.
Note 3 : Do not mix the JDBC 2.0 fetch size API and the Oracle row-prefetching API in your application. You can use one or the other but not both.
value
- the number of rows to prefetchpublic void setIncludeSynonyms(boolean synonyms)
Similar to setRemarksReporting
, getColumns
performs extremely slow if information about synonyms has to be included,
because it neccessitates an outer join so, by default, the JDBC driver will
not report information about synonyms.
You can get synonym information by passing true to this method, and turn it off by passing false. You can also control this behavior by passing a property named "includeSynonyms" as "true" to DriverManager.getConnection.
synonyms
- true if you want to retrieve synonym information
in DatabaseMetaData.getColumns and false otherwise.public void setRemarksReporting(boolean reportRemarks)
getTables
and getColumns
calls of the
DatabaseMetaData
interface.
The DatabaseMetaData
calls getTables
and getColumns
are extremely slow if the REMARKS column has to be reported as this
necessitates an expensive outer join so by default the JDBC driver does not report
the REMARKS columns.
You can turn the reporting of REMARKS on by passing a true
argument
to this method. You turn it back off by passing a false
argument.
Example where conn
is your connection object:
((OracleConnection)conn).setRemarksReporting(true);
You can also control the reporting of REMARKS by passing a property
named remarksReporting
as true
to the
DriverManager.getConnection
call.
reportRemarks
- true if you want to turn on the reporting of
the REMARKS columns and false otherwise.public void setRestrictGetTables(boolean restrict)
DatabaseMetaData.getTables.
DatabaseMetaData.getTables
will return information about
all accessible tables, views, and synonyms. There are two issues relating
to synonyms which can affect the quality of the returned data:
getTables
can return rows
containing objects that are not describable with getColumns
,
either because they are not accessible (issue 1) or because they are not
tables or views (issue 2).
To remedy this, you can restrict the results of getTables
to only those tables and views to which you have access. This is done by
either passing true
to this method, or by passing the
restrictGetTables
property as true
to the
DriverManager.getConnection
call. The default behavior is to
return information about all synonyms, including those which do not point
to accessible tables or views.
Note that getTables
can return more than one row for the
same object, one for the object itself, and additional rows for any
synonyms defined for that object. This is the case regardless of the
setting for restrictGetTables.
The following code turns on the restriction:
((OracleConnection)conn).setRestrictGetTables(true);
restrict
- true to turn on the restriction and false
otherwise.
public void setStmtCacheSize(int size) throws java.sql.SQLException
public void setStmtCacheSize(int size, boolean clearMetaData) throws java.sql.SQLException
public void setStatementCacheSize(int size) throws java.sql.SQLException
size
- Requested size of the cache. If the existing cache size
is less than size, statements will be purged to reduce the
size.public int getStatementCacheSize() throws java.sql.SQLException
public void setImplicitCachingEnabled(boolean cache) throws java.sql.SQLException
cache
- If true, then implicit caching will be enabled. If false,
then any existing statements will be purged and the implicit
cache will be disabled.public boolean getImplicitCachingEnabled() throws java.sql.SQLException
public void setExplicitCachingEnabled(boolean cache) throws java.sql.SQLException
cache
- If true, then explicit caching will be enabled. If false,
then any existing statements will be purged and the explicit
cache will be disabled.public boolean getExplicitCachingEnabled() throws java.sql.SQLException
public void purgeImplicitCache() throws java.sql.SQLException
public void purgeExplicitCache() throws java.sql.SQLException
public java.sql.PreparedStatement getStatementWithKey(java.lang.String key) throws java.sql.SQLException
key
- Specified key to search forpublic java.sql.CallableStatement getCallWithKey(java.lang.String key) throws java.sql.SQLException
key
- Specified key to search forpublic void setUsingXAFlag(boolean value)
UsingXA
flag.
XA is a general standard (not specific to Java) for distributed transactions. You should use this method only when using XA.
By default, when using distributed transactions with XA, the driver will
set the UsingXA
flag to true
and exceptions will
be raised when you want to do anything with your logical connection that
might require a transaction. Otherwise the flag UsingXA
is
always false
.
If you are actually using distributed transactions with XA and you dislike the
default behavior, you can set the flag back to false
.
value
- the value of the UsingXA
flagpublic void setXAErrorFlag(boolean value)
XAError
flag which is used with
distributed transactions. When coexisting with an XA library, you can set
the XAError
flag to true
and the driver will then
raise an exception when doing anything that might require a transaction.value
- the value of the XAError
flagpublic void shutdown(int mode) throws java.sql.SQLException
public void startup(java.lang.String startup_str, int mode) throws java.sql.SQLException
public java.sql.PreparedStatement prepareStatementWithKey(java.lang.String key) throws java.sql.SQLException
key
- the key with which it was closedpublic java.sql.CallableStatement prepareCallWithKey(java.lang.String key) throws java.sql.SQLException
key
- the key with which it was closedpublic void setCreateStatementAsRefCursor(boolean value)
true
, any new statements created from this
connection will be created as a REF CURSOR
. Only resultsets
obtained from statements that are created as REF CURSORS
can
be returned from a Java Stored Procedure. This feature is supported by the
server-side internal driver only, and is no-op in all other JDBC drivers.
Default value is false
.
To use the setCreateStatementAsRefCursor
entrypoint you
have to cast the Connection object to the type
oracle.jdbc.OracleConnection
.
value
- true
if new statements should be created as
REF CURSORS
, false
otherwisepublic boolean getCreateStatementAsRefCursor()
createStatementAsRefCursor
flag which you can set with the
setCreateStatementAsRefCursor
method.
To use the getCreateStatementAsRefCursor
entrypoint you
have to cast the Connection object to the type
oracle.jdbc.OracleConnection
.
public void setSessionTimeZone(java.lang.String regionName) throws java.sql.SQLException
This method is used to set the session time zone. This method must be invoked before accessing any TIMESTAMP WITH LOCAL TIME ZONE data. Upon invocation of this method, the Jdbc driver sets the session timezone of the connection adnd saves the session timezone so that any TSLTZ data accessed via Jdbc are adjusted using the session timezone.
regionName
- Oracle session time zone region name.public java.lang.String getSessionTimeZone()
public java.util.Properties getProperties()
public void assertComplete() throws java.sql.SQLException
public boolean getSynchronousMode()
public void setSynchronousMode(boolean isSynchronous)
isSynchronous
- true if should run synchronously, false if asynchronously.public void registerApiDescription(java.lang.String apiName, short major, short minor, java.lang.String className)
apiName
- a String that names the generic api that this ApiDescription supportsmajor
- a short that specifies the major version number that this ApiDescription supportsminor
- a short that specifies the minor version number that this ApiDescription supportsclassName
- a String that is the fully qualified class name of the ApiDescription classpublic java.lang.Object openJoltConnection(java.lang.String apiName, short major, short minor)
apiName
- a String that names the generic api to be usedmajor
- the major version number of the highest version to be usedminor
- the minor version number of the highest version to be usedpublic java.sql.Connection _getPC()
public boolean isLogicalConnection()
public void registerTAFCallback(OracleOCIFailover cbk, java.lang.Object obj) throws java.sql.SQLException
cbk
- Callback instance.obj
- Context object in which any client's state can be
stored and provided when the callback method is
invoked.public OracleConnection unwrap()
public void setWrapper(OracleConnection wrapper)
wrapper
- An object which implements oracle.jdbc.OracleConnection and
which can act as a wrapper for this object
# @since 9iR2public OracleSavepoint oracleSetSavepoint() throws java.sql.SQLException
OracleSavepoint
object that
represents it.OracleSavepoint
objectConnection
object is currently in
auto-commit modeOracleSavepoint
public OracleSavepoint oracleSetSavepoint(java.lang.String name) throws java.sql.SQLException
OracleSavepoint
object that
represents it.name
- a String
containing the name of the savepointOracleSavepoint
objectConnection
object is currently in
auto-commit modeOracleSavepoint
public void oracleRollback(OracleSavepoint savepoint) throws java.sql.SQLException
OracleSavepoint
object was set.
This method should be used only when auto-commit has been disabled.
savepoint
- the OracleSavepoint
object to roll back toOracleSavepoint
object is no longer valid,
or this Connection
object is currently in
auto-commit modeOracleSavepoint
public void oracleReleaseSavepoint(OracleSavepoint savepoint) throws java.sql.SQLException
OracleSavepoint
object from the current
transaction. Any reference to the savepoint after it have been removed
will cause an SQLException
to be thrown.savepoint
- the OracleSavepoint
object to be removedOracleSavepoint
object is not a valid
savepoint in the current transactionOracleSavepoint
|
|||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |