<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<!-- NewPage -->
<html lang="en">
<head>
<!-- Generated by javadoc (1.8.0_181) on Thu Sep 20 00:34:33 UTC 2018 -->
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>JDBCConnection (HSQLDB 2.4.0 API)</title>
<meta name="date" content="2018-09-20">
<link rel="stylesheet" type="text/css" href="../../../stylesheet.css" title="Style">
<script type="text/javascript" src="../../../script.js"></script>
</head>
<body>
<script type="text/javascript"><!--
try {
if (location.href.indexOf('is-external=true') == -1) {
parent.document.title="JDBCConnection (HSQLDB 2.4.0 API)";
}
}
catch(err) {
}
//-->
var methods = {"i0":10,"i1":10,"i2":10,"i3":10,"i4":10,"i5":10,"i6":10,"i7":10,"i8":10,"i9":10,"i10":10,"i11":10,"i12":10,"i13":10,"i14":10,"i15":10,"i16":10,"i17":10,"i18":10,"i19":10,"i20":10,"i21":10,"i22":10,"i23":10,"i24":10,"i25":10,"i26":10,"i27":10,"i28":10,"i29":10,"i30":10,"i31":10,"i32":10,"i33":10,"i34":10,"i35":10,"i36":10,"i37":10,"i38":10,"i39":10,"i40":10,"i41":10,"i42":10,"i43":10,"i44":10,"i45":10,"i46":10,"i47":10,"i48":10,"i49":10,"i50":10,"i51":10,"i52":10,"i53":10,"i54":10,"i55":10,"i56":10};
var tabs = {65535:["t0","All Methods"],2:["t2","Instance Methods"],8:["t4","Concrete Methods"]};
var altColor = "altColor";
var rowColor = "rowColor";
var tableTab = "tableTab";
var activeTableTab = "activeTableTab";
</script>
<noscript>
<div>JavaScript is disabled on your browser.</div>
</noscript>
<!-- ========= START OF TOP NAVBAR ======= -->
<div class="topNav"><a name="navbar.top">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.top" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.top.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/JDBCConnection.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../index-all.html">Index</a></li>
<li><a href="../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../org/hsqldb/jdbc/JDBCCommonDataSource.html" title="class in org.hsqldb.jdbc"><span class="typeNameLink">Prev Class</span></a></li>
<li><a href="../../../org/hsqldb/jdbc/JDBCConnectionEventListener.html" title="interface in org.hsqldb.jdbc"><span class="typeNameLink">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../index.html?org/hsqldb/jdbc/JDBCConnection.html" target="_top">Frames</a></li>
<li><a href="JDBCConnection.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_top">
<li><a href="../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_top");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor.summary">Constr</a> | </li>
<li><a href="#method.summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor.detail">Constr</a> | </li>
<li><a href="#method.detail">Method</a></li>
</ul>
</div>
<a name="skip.navbar.top">
<!-- -->
</a></div>
<!-- ========= END OF TOP NAVBAR ========= -->
<!-- ======== START OF CLASS DATA ======== -->
<div class="header">
<div class="subTitle">org.hsqldb.jdbc</div>
<h2 title="Class JDBCConnection" class="title">Class JDBCConnection</h2>
</div>
<div class="contentContainer">
<ul class="inheritance">
<li>java.lang.Object</li>
<li>
<ul class="inheritance">
<li>org.hsqldb.jdbc.JDBCConnection</li>
</ul>
</li>
</ul>
<div class="description">
<ul class="blockList">
<li class="blockList">
<dl>
<dt>All Implemented Interfaces:</dt>
<dd>java.lang.AutoCloseable, java.sql.Connection, java.sql.Wrapper</dd>
</dl>
<dl>
<dt>Direct Known Subclasses:</dt>
<dd><a href="../../../org/hsqldb/jdbc/pool/JDBCXAConnectionWrapper.html" title="class in org.hsqldb.jdbc.pool">JDBCXAConnectionWrapper</a></dd>
</dl>
<hr>
<br>
<pre>public class <span class="typeNameLabel">JDBCConnection</span>
extends java.lang.Object
implements java.sql.Connection</pre>
<div class="block"><!-- start generic documentation -->
<P>A connection (session) with a specific
database. SQL statements are executed and results are returned
within the context of a connection.
<P>
A <code>Connection</code> object's database is able to provide information
describing its tables, its supported SQL grammar, its stored
procedures, the capabilities of this connection, and so on. This
information is obtained with the <code>getMetaData</code> method.
<P>(JDBC4 clarification:)
<P><B>Note:</B> When configuring a <code>Connection</code>, JDBC applications
should use the appropriate <code>Connection</code> method such as
<code>setAutoCommit</code> or <code>setTransactionIsolation</code>.
Applications should not invoke SQL commands directly to change the connection's
configuration when there is a JDBC method available. By default a <code>Connection</code> object is in
auto-commit mode, which means that it automatically commits changes
after executing each statement. If auto-commit mode has been
disabled, the method <code>commit</code> must be called explicitly in
order to commit changes; otherwise, database changes will not be saved.
<P>
A new <code>Connection</code> object created using the JDBC 2.1 core API
has an initially empty type map associated with it. A user may enter a
custom mapping for a UDT in this type map.
When a UDT is retrieved from a data source with the
method <code>ResultSet.getObject</code>, the <code>getObject</code> method
will check the connection's type map to see if there is an entry for that
UDT. If so, the <code>getObject</code> method will map the UDT to the
class indicated. If there is no entry, the UDT will be mapped using the
standard mapping.
<p>
A user may create a new type map, which is a <code>java.util.Map</code>
object, make an entry in it, and pass it to the <code>java.sql</code>
methods that can perform custom mapping. In this case, the method
will use the given type map instead of the one associated with
the connection.
<p>
For example, the following code fragment specifies that the SQL
type <code>ATHLETES</code> will be mapped to the class
<code>Athletes</code> in the Java programming language.
The code fragment retrieves the type map for the <code>Connection
</code> object <code>con</code>, inserts the entry into it, and then sets
the type map with the new entry as the connection's type map.
<pre>
java.util.Map map = con.getTypeMap();
map.put("mySchemaName.ATHLETES", Class.forName("Athletes"));
con.setTypeMap(map);
</pre>
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
To get a <code>Connection</code> to an HSQLDB database, the
following code may be used (updated to reflect the most recent
recommendations):
<hr>
When using HSQLDB, the database connection <b><url></b> must start with
<b>'jdbc:hsqldb:'</b><p>
Since 1.7.2, connection properties (<key-value-pairs>) may be appended
to the database connection <b><url></b>, using the form:
<blockquote>
<b>'<url>[;key=value]*'</b>
</blockquote> <p>
Also since 1.7.2, the allowable forms of the HSQLDB database connection
<b><url></b> have been extended. However, all legacy forms continue
to work, with unchanged semantics. The extensions are as described in the
following material.
<hr>
<b>Network Server Database Connections:</b> <p>
The <a href="../../../org/hsqldb/server/Server.html" title="class in org.hsqldb.server"><code>Server</code></a> database connection <b><url></b>
takes one of the two following forms:
<div class="GeneralExample">
<ol>
<li> <b>'jdbc:hsqldb:hsql://host[:port][/<alias>][<key-value-pairs>]'</b>
<li> <b>'jdbc:hsqldb:hsqls://host[:port][/<alias>][<key-value-pairs>]'</b>
(with TLS).
</ol>
</div> <p>
The <a href="../../../org/hsqldb/server/WebServer.html" title="class in org.hsqldb.server"><code>WebServer</code></a> database connection <b><url></b>
takes one of two following forms:
<div class="GeneralExample">
<ol>
<li> <b>'jdbc:hsqldb:http://host[:port][/<alias>][<key-value-pairs>]'</b>
<li> <b>'jdbc:hsqldb:https://host[:port][/<alias>][<key-value-pairs>]'</b>
(with TLS).
</ol>
</div><p>
In both network server database connection <b><url></b> forms, the
optional <b><alias></b> component is used to identify one of possibly
several database instances available at the indicated host and port. If the
<b><alias></b> component is omitted, then a connection is made to the
network server's default database instance, if such an instance is
available. <p>
For more information on server configuration regarding mounting multiple
databases and assigning them <b><alias></b> values, please read the
Java API documentation for <a href="../../../org/hsqldb/server/Server.html" title="class in org.hsqldb.server"><code>Server</code></a> and related
chapters in the general documentation, especially the <em>Advanced Users
Guide</em>.
<hr>
<b>Transient, In-Process Database Connections:</b> <p>
The 100% in-memory (transient, in-process) database connection
<b><url></b> takes one of the two following forms:
<div class="GeneralExample">
<ol>
<li> <b>'jdbc:hsqldb:.[<key-value-pairs>]'</b>
(the legacy form, extended)
<li> <b>'jdbc:hsqldb:mem:<alias>[<key-value-pairs>]'</b>
(the new form)
</ol>
</div> <p>
The driver converts the supplied <b><alias></b> component to
Local.ENGLISH lower case and uses the resulting character sequence as the
key used to look up a <b>mem:</b> protocol database instance amongst the
collection of all such instances already in existence within the current
class loading context in the current JVM. If no such instance exists, one
<em>may</em> be automatically created and mapped to the <b><alias></b>,
as governed by the <b>'ifexists=true|false'</b> connection property. <p>
The rationale for converting the supplied <b><alias></b> component to
lower case is to provide consistency with the behavior of <b>res:</b>
protocol database connection <b><url></b>s, explained further on in
this overview.
<hr>
<b>Persistent, In-Process Database Connections:</b> <p>
The standalone (persistent, in-process) database connection
<b><url></b> takes one of the three following forms:
<div class="GeneralExample">
<ol>
<li> <b>'jdbc:hsqldb:<path>[<key-value-pairs>]'</b>
(the legacy form, extended)
<li> <b>'jdbc:hsqldb:file:<path>[<key-value-pairs>]'</b>
(same semantics as the legacy form)
<li> <b>'jdbc:hsqldb:res:<path>[<key-value-pairs>]'</b>
(new form with 'files_in_jar' semantics)
</ol>
</div> <p>
For the persistent, in-process database connection <b><url></b>,
the <b><path></b> component is the path prefix common to all of
the files that compose the database. <p>
From 1.7.2, although other files may be involved (such as transient working
files and/or TEXT table CSV data source files), the essential set that may,
at any particular point in time, compose an HSQLDB database is:
<div class="GeneralExample">
<ul>
<li><path>.properties
<li><path>.script
<li><path>.log
<li><path>.data
<li><path>.backup
<li><path>.lck
</ul>
</div> <p>
For example: <b>'jdbc:hsqldb:file:test'</b> connects to a database
composed of some subset of the files listed above, where the expansion
of <b><path></b> is <b>'test'</b> prefixed with the canonical path of
the JVM's effective working directory at the time the designated database
is first opened in-process. <p>
Be careful to note that this canonical expansion of <b><path></b> is
cached by the driver until JVM exit. So, although legacy JVMs tend to fix
the reported effective working directory at the one noted upon JVM startup,
there is no guarantee that modern JVMs will continue to uphold this
behaviour. What this means is there is effectively no guarantee into the
future that a relative <b>file:</b> protocol database connection
<b><url></b> will connect to the same database instance for the life
of the JVM. To avoid any future ambiguity issues, it is probably a best
practice for clients to attempt to pre-canonicalize the <b><path></b>
component of <b>file:</b> protocol database connection* <b><url></b>s.
<p>
Under <em>Windows</em>,
<b>'jdbc:hsqldb:file:c:\databases\test'</b> connects to a database located
on drive <b>'C:'</b> in the directory <b>'databases'</b>, composed
of some subset of the files:
<pre class="GeneralExample">
C:\
+--databases\
+--test.properties
+--test.script
+--test.log
+--test.data
+--test.backup
+--test.lck
</pre>
Under most variations of UNIX, <b>'jdbc:hsqldb:file:/databases/test'</b>
connects to a database located in the directory <b>'databases'</b> directly
under root, once again composed of some subset of the files:
<pre class="GeneralExample">
+--databases
+--test.properties
+--test.script
+--test.log
+--test.data
+--test.backup
+--test.lck
</pre>
<b>Some Guidelines:</b>
<ol>
<li> Both relative and absolute database file paths are supported.
<li> Relative database file paths can be specified in a platform independent
manner as: <b>'[dir1/dir2/.../dirn/]<file-name-prefix>'</b>.
<li> Specification of absolute file paths is operating-system specific.<br>
Please read your OS file system documentation.
<li> Specification of network mounts may be operating-system specific.<br>
Please read your OS file system documentation.
<li> Special care may be needed w.r.t. file path specifications
containing whitespace, mixed-case, special characters and/or
reserved file names.<br>
Please read your OS file system documentation.
</ol> <p>
<b>Note:</b> Versions of HSQLDB previous to 1.7.0 did not support creating
directories along the file path specified in the persistent, in-process mode
database connection <b><url></b> form, in the case that they did
not already exist. Starting with HSQLDB 1.7.0, directories <i>will</i>
be created if they do not already exist., but only if HSQLDB is built under
a version of the compiler greater than JDK 1.1.x.
<hr>
<b>res: protocol Connections:</b><p>
The <b>'jdbc:hsqldb:res:<path>'</b> database connection
<b><url></b> has different semantics than the
<b>'jdbc:hsqldb:file:<path>'</b> form. The semantics are similar to
those of a <b>'files_readonly'</b> database, but with some additional
points to consider. <p>
Specifically, the <b>'<path>'</b> component of a <b>res:</b> protocol
database connection <b><url></b> is first converted to lower case
with <tt>Locale.ENGLISH</tt> and only then used to obtain resource URL
objects, which in turn are used to read the database files as resources on
the class path. <p>
Due to lower case conversion by the driver, <b>res:</b> <b>'<path>'</b>
components <em>never</em> find jar resources stored with
<tt>Locale.ENGLISH</tt> mixed case paths. The rationale for converting to
lower case is that not all pkzip implementations guarantee path case is
preserved when archiving resources, and conversion to lower case seems to
be the most common occurrence (although there is also no actual guarantee
that the conversion is <tt>Locale.ENGLISH</tt>).<p>
More importantly, <b>res:</b> <b>'<path>'</b> components <em>must</em>
point only to resources contained in one or more jars on the class
path. That is, only resources having the jar sub-protocol are considered
valid. <p>
This restriction is enforced to avoid the unfortunate situation in which,
because <b>res:</b> database instances do not create a <b><path></b>.lck
file (they are strictly files-read-only) and because the <b><path></b>
components of <b>res:</b> and <b>file:</b> database <tt>URI</tt>s are not
checked for file system equivalence, it is possible for the same database
files to be accessed concurrently by both <b>file:</b> and <b>res:</b>
database instances. That is, without this restriction, it is possible that
<b><path></b>.data and <b><path></b>.properties file content may
be written by a <b>file:</b> database instance without the knowledge or
cooperation of a <b>res:</b> database instance open on the same files,
potentially resulting in unexpected database errors, inconsistent operation
and/or data corruption. <p>
In short, a <b>res:</b> type database connection <b><url></b> is
designed specifically to connect to a <b>'files_in_jar'</b> mode database
instance, which in turn is designed specifically to operate under
<em>Java WebStart</em> and
<em>Java Applet</em> configurations,
where co-locating the database files in the jars that make up the
<em>WebStart</em> application or Applet avoids the need for special security
configuration or code signing. <p>
<b>Note:</b> Since it is difficult and often nearly impossible to determine
or control at runtime from where all classes are being loaded or which class
loader is doing the loading (and hence how relative path specifications
are resolved) under <b>'files_in_jar'</b> semantics, the <b><path></b>
component of the <b>res:</b> database connection <b><url></b> is always
taken to be relative to the default package and resource URL resolution is
always performed using the ClassLoader that loads the
org.hsqldb.persist.Logger class. That is, if the <b><path></b>
component does not start with '/', then'/' is prepended when obtaining the
resource URLs used to read the database files, and only the effective class
path of org.hsqldb.persist.Logger's ClassLoader is searched.
<hr>
For more information about HSQLDB file structure, various database modes
and other attributes such as those controlled through the HSQLDB properties
files, please read the general documentation, especially the Advanced Users
Guide. <p>
<b>JDBC 4.0 Notes:</b><p>
Starting with JDBC 4.0 (JDK 1.6), the <code>DriverManager</code> methods
<code>getConnection</code> and <code>getDrivers</code> have been
enhanced to support the Java Standard Edition Service Provider mechanism.
When built under a Java runtime that supports JDBC 4.0, HSQLDB distribution
jars containing the Driver implementation also include the file
<code>META-INF/services/java.sql.Driver</code>. This file contains the fully
qualified class name ('org.hsqldb.jdbc.JDBCDriver') of the HSQLDB implementation
of <code>java.sql.Driver</code>. <p>
Hence, under JDBC 4.0 or greater, applications no longer need to explicitly
load the HSQLDB JDBC driver using <code>Class.forName()</code>. Of course,
existing programs which do load JDBC drivers using
<code>Class.forName()</code> will continue to work without modification.
<hr>
(fredt@users)<br>
(campbell-burnet@users)<p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>HSQLDB 1.9.0</dd>
<dt><span class="simpleTagLabel">Author:</span></dt>
<dd>Campbell Burnet (campbell-burnet@users dot sourceforge.net), Fred Toussi (fredt@users dot sourceforge.net)</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCDriver.html" title="class in org.hsqldb.jdbc"><code>JDBCDriver</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCStatement.html" title="class in org.hsqldb.jdbc"><code>JDBCStatement</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCParameterMetaData.html" title="class in org.hsqldb.jdbc"><code>JDBCParameterMetaData</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCCallableStatement.html" title="class in org.hsqldb.jdbc"><code>JDBCCallableStatement</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCDatabaseMetaData.html" title="class in org.hsqldb.jdbc"><code>JDBCDatabaseMetaData</code></a>,
<code>DriverManager.getConnection(java.lang.String, java.util.Properties)</code>,
<code>Statement</code>,
<code>ResultSet</code>,
<code>DatabaseMetaData</code></dd>
</dl>
</li>
</ul>
</div>
<div class="summary">
<ul class="blockList">
<li class="blockList">
<!-- =========== FIELD SUMMARY =========== -->
<ul class="blockList">
<li class="blockList"><a name="field.summary">
<!-- -->
</a>
<h3>Field Summary</h3>
<ul class="blockList">
<li class="blockList"><a name="fields.inherited.from.class.java.sql.Connection">
<!-- -->
</a>
<h3>Fields inherited from interface java.sql.Connection</h3>
<code>TRANSACTION_NONE, TRANSACTION_READ_COMMITTED, TRANSACTION_READ_UNCOMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE</code></li>
</ul>
</li>
</ul>
<!-- ======== CONSTRUCTOR SUMMARY ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor.summary">
<!-- -->
</a>
<h3>Constructor Summary</h3>
<table class="memberSummary" border="0" cellpadding="3" cellspacing="0" summary="Constructor Summary table, listing constructors, and an explanation">
<caption><span>Constructors</span><span class="tabEnd"> </span></caption>
<tr>
<th class="colOne" scope="col">Constructor and Description</th>
</tr>
<tr class="altColor">
<td class="colOne"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#JDBCConnection-org.hsqldb.persist.HsqlProperties-">JDBCConnection</a></span>(org.hsqldb.persist.HsqlProperties props)</code>
<div class="block">Constructs a new external <code>Connection</code> to an HSQLDB
<code>Database</code>.</div>
</td>
</tr>
<tr class="rowColor">
<td class="colOne"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#JDBCConnection-org.hsqldb.jdbc.JDBCConnection-org.hsqldb.jdbc.JDBCConnectionEventListener-">JDBCConnection</a></span>(<a href="../../../org/hsqldb/jdbc/JDBCConnection.html" title="class in org.hsqldb.jdbc">JDBCConnection</a> c,
<a href="../../../org/hsqldb/jdbc/JDBCConnectionEventListener.html" title="interface in org.hsqldb.jdbc">JDBCConnectionEventListener</a> eventListener)</code>
<div class="block">Constructor for use with connection pooling and XA.</div>
</td>
</tr>
<tr class="altColor">
<td class="colOne"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#JDBCConnection-org.hsqldb.SessionInterface-">JDBCConnection</a></span>(org.hsqldb.SessionInterface c)</code>
<div class="block">Constructs an <code>INTERNAL</code> <code>Connection</code>,
using the specified <code>SessionInterface</code>.</div>
</td>
</tr>
</table>
</li>
</ul>
<!-- ========== METHOD SUMMARY =========== -->
<ul class="blockList">
<li class="blockList"><a name="method.summary">
<!-- -->
</a>
<h3>Method Summary</h3>
<table class="memberSummary" border="0" cellpadding="3" cellspacing="0" summary="Method Summary table, listing methods, and an explanation">
<caption><span id="t0" class="activeTableTab"><span>All Methods</span><span class="tabEnd"> </span></span><span id="t2" class="tableTab"><span><a href="javascript:show(2);">Instance Methods</a></span><span class="tabEnd"> </span></span><span id="t4" class="tableTab"><span><a href="javascript:show(8);">Concrete Methods</a></span><span class="tabEnd"> </span></span></caption>
<tr>
<th class="colFirst" scope="col">Modifier and Type</th>
<th class="colLast" scope="col">Method and Description</th>
</tr>
<tr id="i0" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#abort-java.util.concurrent.Executor-">abort</a></span>(java.util.concurrent.Executor executor)</code>
<div class="block">Terminates an open connection.</div>
</td>
</tr>
<tr id="i1" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#clearWarnings--">clearWarnings</a></span>()</code>
<div class="block">Clears all warnings reported for this <code>Connection</code> object.</div>
</td>
</tr>
<tr id="i2" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#close--">close</a></span>()</code>
<div class="block">Releases this <code>Connection</code> object's database and JDBC resources
immediately instead of waiting for them to be automatically released.</div>
</td>
</tr>
<tr id="i3" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#closeFully--">closeFully</a></span>()</code>
<div class="block">Completely closes a pooled connection</div>
</td>
</tr>
<tr id="i4" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#commit--">commit</a></span>()</code>
<div class="block">Makes all changes made since the previous
commit/rollback permanent and releases any database locks
currently held by this <code>Connection</code> object.</div>
</td>
</tr>
<tr id="i5" class="rowColor">
<td class="colFirst"><code>java.sql.Array</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createArrayOf-java.lang.String-java.lang.Object:A-">createArrayOf</a></span>(java.lang.String typeName,
java.lang.Object[] elements)</code>
<div class="block">Factory method for creating Array objects.</div>
</td>
</tr>
<tr id="i6" class="altColor">
<td class="colFirst"><code>java.sql.Blob</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createBlob--">createBlob</a></span>()</code>
<div class="block">Constructs an object that implements the <code>Blob</code> interface.</div>
</td>
</tr>
<tr id="i7" class="rowColor">
<td class="colFirst"><code>java.sql.Clob</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createClob--">createClob</a></span>()</code>
<div class="block">Constructs an object that implements the <code>Clob</code> interface.</div>
</td>
</tr>
<tr id="i8" class="altColor">
<td class="colFirst"><code>java.sql.NClob</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createNClob--">createNClob</a></span>()</code>
<div class="block">Constructs an object that implements the <code>NClob</code> interface.</div>
</td>
</tr>
<tr id="i9" class="rowColor">
<td class="colFirst"><code>java.sql.SQLXML</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createSQLXML--">createSQLXML</a></span>()</code>
<div class="block">Constructs an object that implements the <code>SQLXML</code> interface.</div>
</td>
</tr>
<tr id="i10" class="altColor">
<td class="colFirst"><code>java.sql.Statement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStatement--">createStatement</a></span>()</code>
<div class="block">Creates a <code>Statement</code> object for sending
SQL statements to the database.</div>
</td>
</tr>
<tr id="i11" class="rowColor">
<td class="colFirst"><code>java.sql.Statement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStatement-int-int-">createStatement</a></span>(int resultSetType,
int resultSetConcurrency)</code>
<div class="block">Creates a <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.</div>
</td>
</tr>
<tr id="i12" class="altColor">
<td class="colFirst"><code>java.sql.Statement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStatement-int-int-int-">createStatement</a></span>(int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)</code>
<div class="block">Creates a <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type, concurrency,
and holdability.</div>
</td>
</tr>
<tr id="i13" class="rowColor">
<td class="colFirst"><code>java.sql.Struct</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStruct-java.lang.String-java.lang.Object:A-">createStruct</a></span>(java.lang.String typeName,
java.lang.Object[] attributes)</code>
<div class="block">Factory method for creating Struct objects.</div>
</td>
</tr>
<tr id="i14" class="altColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getAutoCommit--">getAutoCommit</a></span>()</code>
<div class="block">Retrieves the current auto-commit mode for this <code>Connection</code>
object.</div>
</td>
</tr>
<tr id="i15" class="rowColor">
<td class="colFirst"><code>java.lang.String</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getCatalog--">getCatalog</a></span>()</code>
<div class="block">Retrieves this <code>Connection</code> object's current catalog name.</div>
</td>
</tr>
<tr id="i16" class="altColor">
<td class="colFirst"><code>java.util.Properties</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getClientInfo--">getClientInfo</a></span>()</code>
<div class="block">Returns a list containing the name and current value of each client info
property supported by the driver.</div>
</td>
</tr>
<tr id="i17" class="rowColor">
<td class="colFirst"><code>java.lang.String</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getClientInfo-java.lang.String-">getClientInfo</a></span>(java.lang.String name)</code>
<div class="block">Returns the value of the client info property specified by name.</div>
</td>
</tr>
<tr id="i18" class="altColor">
<td class="colFirst"><code>int</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--">getHoldability</a></span>()</code>
<div class="block">Retrieves the current holdability of <code>ResultSet</code> objects
created using this <code>Connection</code> object.</div>
</td>
</tr>
<tr id="i19" class="rowColor">
<td class="colFirst"><code>java.sql.DatabaseMetaData</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getMetaData--">getMetaData</a></span>()</code>
<div class="block">Retrieves a <code>DatabaseMetaData</code> object that contains
metadata about the database to which this
<code>Connection</code> object represents a connection.</div>
</td>
</tr>
<tr id="i20" class="altColor">
<td class="colFirst"><code>int</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getNetworkTimeout--">getNetworkTimeout</a></span>()</code>
<div class="block">Retrieves the number of milliseconds the driver will
wait for a database request to complete.</div>
</td>
</tr>
<tr id="i21" class="rowColor">
<td class="colFirst"><code>java.lang.String</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getSchema--">getSchema</a></span>()</code>
<div class="block">Retrieves this <code>Connection</code> object's current schema name.</div>
</td>
</tr>
<tr id="i22" class="altColor">
<td class="colFirst"><code>org.hsqldb.SessionInterface</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getSession--">getSession</a></span>()</code>
<div class="block">provides cross-package access to the proprietary (i.e.</div>
</td>
</tr>
<tr id="i23" class="rowColor">
<td class="colFirst"><code>int</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getTransactionIsolation--">getTransactionIsolation</a></span>()</code>
<div class="block">Retrieves this <code>Connection</code> object's current
transaction isolation level.</div>
</td>
</tr>
<tr id="i24" class="altColor">
<td class="colFirst"><code>java.util.Map<java.lang.String,java.lang.Class<?>></code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getTypeMap--">getTypeMap</a></span>()</code>
<div class="block">Retrieves the <code>Map</code> object associated with this
<code>Connection</code> object.</div>
</td>
</tr>
<tr id="i25" class="rowColor">
<td class="colFirst"><code>java.sql.SQLWarning</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getWarnings--">getWarnings</a></span>()</code>
<div class="block">Retrieves the first warning reported by calls on this
<code>Connection</code> object.</div>
</td>
</tr>
<tr id="i26" class="altColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#isClosed--">isClosed</a></span>()</code>
<div class="block">Retrieves whether this <code>Connection</code> object has been
closed.</div>
</td>
</tr>
<tr id="i27" class="rowColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#isReadOnly--">isReadOnly</a></span>()</code>
<div class="block">Retrieves whether this <code>Connection</code>
object is in read-only mode.</div>
</td>
</tr>
<tr id="i28" class="altColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#isValid-int-">isValid</a></span>(int timeout)</code>
<div class="block">Returns true if the connection has not been closed and is still valid.</div>
</td>
</tr>
<tr id="i29" class="rowColor">
<td class="colFirst"><code>boolean</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#isWrapperFor-java.lang.Class-">isWrapperFor</a></span>(java.lang.Class<?> iface)</code>
<div class="block">Returns true if this either implements the interface argument or is directly or indirectly a wrapper
for an object that does.</div>
</td>
</tr>
<tr id="i30" class="altColor">
<td class="colFirst"><code>java.lang.String</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#nativeSQL-java.lang.String-">nativeSQL</a></span>(java.lang.String sql)</code>
<div class="block">Converts the given SQL statement into the system's native SQL grammar.</div>
</td>
</tr>
<tr id="i31" class="rowColor">
<td class="colFirst"><code>java.sql.CallableStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareCall-java.lang.String-">prepareCall</a></span>(java.lang.String sql)</code>
<div class="block">Creates a <code>CallableStatement</code> object for calling
database stored procedures.</div>
</td>
</tr>
<tr id="i32" class="altColor">
<td class="colFirst"><code>java.sql.CallableStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareCall-java.lang.String-int-int-">prepareCall</a></span>(java.lang.String sql,
int resultSetType,
int resultSetConcurrency)</code>
<div class="block">Creates a <code>CallableStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.</div>
</td>
</tr>
<tr id="i33" class="rowColor">
<td class="colFirst"><code>java.sql.CallableStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareCall-java.lang.String-int-int-int-">prepareCall</a></span>(java.lang.String sql,
int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)</code>
<div class="block">Creates a <code>CallableStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.</div>
</td>
</tr>
<tr id="i34" class="altColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-">prepareStatement</a></span>(java.lang.String sql)</code>
<div class="block">Creates a <code>PreparedStatement</code> object for sending
parameterized SQL statements to the database.</div>
</td>
</tr>
<tr id="i35" class="rowColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-int-">prepareStatement</a></span>(java.lang.String sql,
int autoGeneratedKeys)</code>
<div class="block">Creates a default <code>PreparedStatement</code> object that has
the capability to retrieve auto-generated keys.</div>
</td>
</tr>
<tr id="i36" class="altColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-int:A-">prepareStatement</a></span>(java.lang.String sql,
int[] columnIndexes)</code>
<div class="block">Creates a default <code>PreparedStatement</code> object capable
of returning the auto-generated keys designated by the given array.</div>
</td>
</tr>
<tr id="i37" class="rowColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-int-int-">prepareStatement</a></span>(java.lang.String sql,
int resultSetType,
int resultSetConcurrency)</code>
<div class="block">Creates a <code>PreparedStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.</div>
</td>
</tr>
<tr id="i38" class="altColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-int-int-int-">prepareStatement</a></span>(java.lang.String sql,
int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)</code>
<div class="block">Creates a <code>PreparedStatement</code> object that will generate
<code>ResultSet</code> objects with the given type, concurrency,
and holdability.</div>
</td>
</tr>
<tr id="i39" class="rowColor">
<td class="colFirst"><code>java.sql.PreparedStatement</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-java.lang.String:A-">prepareStatement</a></span>(java.lang.String sql,
java.lang.String[] columnNames)</code>
<div class="block">Creates a default <code>PreparedStatement</code> object capable
of returning the auto-generated keys designated by the given array.</div>
</td>
</tr>
<tr id="i40" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#releaseSavepoint-java.sql.Savepoint-">releaseSavepoint</a></span>(java.sql.Savepoint savepoint)</code>
<div class="block">Removes the specified <code>Savepoint</code> (JDBC4 Clarification:) and subsequent <code>Savepoint</code> objects from the current
transaction.</div>
</td>
</tr>
<tr id="i41" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#reset--">reset</a></span>()</code>
<div class="block">Resets this connection so it can be used again.</div>
</td>
</tr>
<tr id="i42" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#rollback--">rollback</a></span>()</code>
<div class="block">Undoes all changes made in the current transaction
and releases any database locks currently held
by this <code>Connection</code> object.</div>
</td>
</tr>
<tr id="i43" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#rollback-java.sql.Savepoint-">rollback</a></span>(java.sql.Savepoint savepoint)</code>
<div class="block">Undoes all changes made after the given <code>Savepoint</code> object
was set.</div>
</td>
</tr>
<tr id="i44" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setAutoCommit-boolean-">setAutoCommit</a></span>(boolean autoCommit)</code>
<div class="block">Sets this connection's auto-commit mode to the given state.</div>
</td>
</tr>
<tr id="i45" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setCatalog-java.lang.String-">setCatalog</a></span>(java.lang.String catalog)</code>
<div class="block">Sets the given catalog name in order to select
a subspace of this <code>Connection</code> object's database
in which to work.</div>
</td>
</tr>
<tr id="i46" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setClientInfo-java.util.Properties-">setClientInfo</a></span>(java.util.Properties properties)</code>
<div class="block">Sets the value of the connection's client info properties.</div>
</td>
</tr>
<tr id="i47" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setClientInfo-java.lang.String-java.lang.String-">setClientInfo</a></span>(java.lang.String name,
java.lang.String value)</code>
<div class="block">Sets the value of the client info property specified by name to the
value specified by value.</div>
</td>
</tr>
<tr id="i48" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setHoldability-int-">setHoldability</a></span>(int holdability)</code>
<div class="block">(JDBC4 Clarification:)
Changes the default holdability of <code>ResultSet</code> objects
created using this <code>Connection</code> object to the given
holdability.</div>
</td>
</tr>
<tr id="i49" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setNetworkTimeout-java.util.concurrent.Executor-int-">setNetworkTimeout</a></span>(java.util.concurrent.Executor executor,
int milliseconds)</code>
<div class="block">Sets the maximum period a <code>Connection</code> or
objects created from the <code>Connection</code>
will wait for the database to reply to any one request.</div>
</td>
</tr>
<tr id="i50" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setReadOnly-boolean-">setReadOnly</a></span>(boolean readOnly)</code>
<div class="block">Puts this connection in read-only mode as a hint to the driver to enable
database optimizations.</div>
</td>
</tr>
<tr id="i51" class="rowColor">
<td class="colFirst"><code>java.sql.Savepoint</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setSavepoint--">setSavepoint</a></span>()</code>
<div class="block">Creates an unnamed savepoint in the current transaction and
returns the new <code>Savepoint</code> object that represents it.</div>
</td>
</tr>
<tr id="i52" class="altColor">
<td class="colFirst"><code>java.sql.Savepoint</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setSavepoint-java.lang.String-">setSavepoint</a></span>(java.lang.String name)</code>
<div class="block">Creates a savepoint with the given name in the current transaction
and returns the new <code>Savepoint</code> object that represents it.</div>
</td>
</tr>
<tr id="i53" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setSchema-java.lang.String-">setSchema</a></span>(java.lang.String schema)</code>
<div class="block">Sets the given schema name to access.</div>
</td>
</tr>
<tr id="i54" class="altColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setTransactionIsolation-int-">setTransactionIsolation</a></span>(int level)</code>
<div class="block">Attempts to change the transaction isolation level for this
<code>Connection</code> object to the one given.</div>
</td>
</tr>
<tr id="i55" class="rowColor">
<td class="colFirst"><code>void</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setTypeMap-java.util.Map-">setTypeMap</a></span>(java.util.Map<java.lang.String,java.lang.Class<?>> map)</code>
<div class="block">Installs the given <code>TypeMap</code> object as the type map for
this <code>Connection</code> object.</div>
</td>
</tr>
<tr id="i56" class="altColor">
<td class="colFirst"><code><T> T</code></td>
<td class="colLast"><code><span class="memberNameLink"><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#unwrap-java.lang.Class-">unwrap</a></span>(java.lang.Class<T> iface)</code>
<div class="block">Returns an object that implements the given interface to allow access to
non-standard methods, or standard methods not exposed by the proxy.</div>
</td>
</tr>
</table>
<ul class="blockList">
<li class="blockList"><a name="methods.inherited.from.class.java.lang.Object">
<!-- -->
</a>
<h3>Methods inherited from class java.lang.Object</h3>
<code>equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait</code></li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
<div class="details">
<ul class="blockList">
<li class="blockList">
<!-- ========= CONSTRUCTOR DETAIL ======== -->
<ul class="blockList">
<li class="blockList"><a name="constructor.detail">
<!-- -->
</a>
<h3>Constructor Detail</h3>
<a name="JDBCConnection-org.hsqldb.persist.HsqlProperties-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>JDBCConnection</h4>
<pre>public JDBCConnection(org.hsqldb.persist.HsqlProperties props)
throws java.sql.SQLException</pre>
<div class="block">Constructs a new external <code>Connection</code> to an HSQLDB
<code>Database</code>. <p>
This constructor is called on behalf of the
<code>java.sql.DriverManager</code> when getting a
<code>Connection</code> for use in normal (external)
client code. <p>
Internal client code, that being code located in HSQLDB SQL
functions and stored procedures, receives an INTERNAL
connection constructed by the <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#JDBCConnection-org.hsqldb.SessionInterface-"><code>JDBCConnection(SessionInterface)</code></a> constructor. <p></div>
<dl>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>props</code> - A <code>Properties</code> object containing the connection
properties</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - when the user/password combination is
invalid, the connection url is invalid, or the
<code>Database</code> is unavailable. <p>
The <code>Database</code> may be unavailable for a number
of reasons, including network problems or the fact that it
may already be in use by another process.</dd>
</dl>
</li>
</ul>
<a name="JDBCConnection-org.hsqldb.SessionInterface-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>JDBCConnection</h4>
<pre>public JDBCConnection(org.hsqldb.SessionInterface c)</pre>
<div class="block">Constructs an <code>INTERNAL</code> <code>Connection</code>,
using the specified <code>SessionInterface</code>. <p>
This constructor is called only on behalf of an existing
<code>Session</code> (the internal parallel of a
<code>Connection</code>), to be used as a parameter to a SQL
function or stored procedure that needs to execute in the context
of that <code>Session</code>. <p>
When a Java SQL function or stored procedure is called and its
first parameter is of type <code>Connection</code>, HSQLDB
automatically notices this and constructs an <code>INTERNAL</code>
<code>Connection</code> using the current <code>Session</code>.
HSQLDB then passes this <code>Connection</code> in the first
parameter position, moving any other parameter values
specified in the SQL statement to the right by one position.
<p>
To read more about this, see
<code>Routine</code>. <p>
<B>Notes:</B> <p>
Starting with HSQLDB 1.7.2, <code>INTERNAL</code> connections are not
closed by a call to close() or by a SQL DISCONNECT.
For HSQLDB developers not involved with writing database
internals, this change only applies to connections obtained
automatically from the database as the first parameter to
Java stored procedures and functions. This is mainly an issue
to developers writing custom SQL function and stored procedure
libraries for HSQLDB. Presently, it is recommended that SQL function and
stored procedure code avoid depending on closing or issuing a
DISCONNECT on a connection obtained in this manner. <p></div>
<dl>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>c</code> - the Session requesting the construction of this
Connection</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>org.hsqldb.HsqlException</code> - never (reserved for future use);</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>Routine</code></dd>
</dl>
</li>
</ul>
<a name="JDBCConnection-org.hsqldb.jdbc.JDBCConnection-org.hsqldb.jdbc.JDBCConnectionEventListener-">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>JDBCConnection</h4>
<pre>public JDBCConnection(<a href="../../../org/hsqldb/jdbc/JDBCConnection.html" title="class in org.hsqldb.jdbc">JDBCConnection</a> c,
<a href="../../../org/hsqldb/jdbc/JDBCConnectionEventListener.html" title="interface in org.hsqldb.jdbc">JDBCConnectionEventListener</a> eventListener)</pre>
<div class="block">Constructor for use with connection pooling and XA.</div>
<dl>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>c</code> - the connection</dd>
<dd><code>eventListener</code> - the listener</dd>
</dl>
</li>
</ul>
</li>
</ul>
<!-- ============ METHOD DETAIL ========== -->
<ul class="blockList">
<li class="blockList"><a name="method.detail">
<!-- -->
</a>
<h3>Method Detail</h3>
<a name="createStatement--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createStatement</h4>
<pre>public java.sql.Statement createStatement()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>Statement</code> object for sending
SQL statements to the database.
SQL statements without parameters are normally
executed using <code>Statement</code> objects. If the same SQL statement
is executed many times, it may be more efficient to use a
<code>PreparedStatement</code> object.
<P>
Result sets created using the returned <code>Statement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with HSQLDB 1.7.2, support for precompilation at the engine level
has been implemented, so it is now much more efficient and performant
to use a <code>PreparedStatement</code> object if the same short-running
SQL statement is to be executed many times. <p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code> and <code>CONCUR_READ_ONLY</code>
results. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new default <code>Statement</code> object</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStatement-int-int-"><code>createStatement(int,int)</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#createStatement-int-int-int-"><code>createStatement(int,int,int)</code></a></dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>PreparedStatement</code> object for sending
parameterized SQL statements to the database.
<P>
A SQL statement with or without IN parameters can be
pre-compiled and stored in a <code>PreparedStatement</code> object. This
object can then be used to efficiently execute this statement
multiple times.
<P><B>Note:</B> This method is optimized for handling
parametric SQL statements that benefit from precompilation. If
the driver supports precompilation,
the method <code>prepareStatement</code> will send
the statement to the database for precompilation. Some drivers
may not support precompilation. In this case, the statement may
not be sent to the database until the <code>PreparedStatement</code>
object is executed. This has no direct effect on users; however, it does
affect which methods throw certain <code>SQLException</code> objects.
<P>
Result sets created using the returned <code>PreparedStatement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with HSQLDB 1.7.2, support for precompilation at the engine level
has been implemented, so it is now much more efficient and performant
to use a <code>PreparedStatement</code> object if the same short-running
SQL statement is to be executed many times. <p>
The support for and behaviour of PreparedStatement complies with SQL and
JDBC standards. Please read the introductory section
of the documentation for ${link JDBCParameterMetaData}. <P>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?' IN
parameter placeholders</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new default <code>PreparedStatement</code> object containing the
pre-compiled SQL statement</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareStatement-java.lang.String-int-int-"><code>prepareStatement(String,int,int)</code></a></dd>
</dl>
</li>
</ul>
<a name="prepareCall-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareCall</h4>
<pre>public java.sql.CallableStatement prepareCall(java.lang.String sql)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>CallableStatement</code> object for calling
database stored procedures.
The <code>CallableStatement</code> object provides
methods for setting up its IN and OUT parameters, and
methods for executing the call to a stored procedure.
<P><B>Note:</B> This method is optimized for handling stored
procedure call statements. Some drivers may send the call
statement to the database when the method <code>prepareCall</code>
is done; others
may wait until the <code>CallableStatement</code> object
is executed. This has no
direct effect on users; however, it does affect which method
throws certain SQLExceptions.
<P>
Result sets created using the returned <code>CallableStatement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with 1.7.2, the support for and behaviour of
CallableStatement has changed. Please read the introductory section
of the documentation for org.hsqldb.jdbc.JDBCCallableStatement.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareCall</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?'
parameter placeholders. (JDBC4 clarification:) Typically this statement is specified using JDBC
call escape syntax.</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new default <code>CallableStatement</code> object containing the
pre-compiled SQL statement</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#prepareCall-java.lang.String-int-int-"><code>prepareCall(String,int,int)</code></a></dd>
</dl>
</li>
</ul>
<a name="nativeSQL-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>nativeSQL</h4>
<pre>public java.lang.String nativeSQL(java.lang.String sql)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Converts the given SQL statement into the system's native SQL grammar.
A driver may convert the JDBC SQL grammar into its system's
native SQL grammar prior to sending it. This method returns the
native form of the statement that the driver would have sent.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB converts the JDBC SQL
grammar into the system's native SQL grammar prior to sending
it, if escape processing is set true; this method returns the
native form of the statement that the driver would send in place
of client-specified JDBC SQL grammar. <p>
Before 1.7.2, escape processing was incomplete and
also broken in terms of support for nested escapes. <p>
Starting with 1.7.2, escape processing is complete and handles nesting
to arbitrary depth, but enforces a very strict interpretation of the
syntax and does not detect or process SQL comments. <p>
In essence, the HSQLDB engine directly handles the prescribed syntax
and date / time formats specified internal to the JDBC escapes.
It also directly offers the XOpen / ODBC extended scalar
functions specified available internal to the {fn ...} JDBC escape.
As such, the driver simply removes the curly braces and JDBC escape
codes in the simplest and fastest fashion possible, by replacing them
with whitespace.
But to avoid a great deal of complexity, certain forms of input
whitespace are currently not recognised. For instance,
the driver handles "{?= call ...}" but not "{ ?= call ...} or
"{? = call ...}" <p>
Also, comments embedded in SQL are currently not detected or
processed and thus may have unexpected effects on the output
of this method, for instance causing otherwise valid SQL to become
invalid. It is especially important to be aware of this because escape
processing is set true by default for Statement objects and is always
set true when producing a PreparedStatement from prepareStatement()
or CallableStatement from prepareCall(). Currently, it is simply
recommended to avoid submitting SQL having comments containing JDBC
escape sequence patterns and/or single or double quotation marks,
as this will avoid any potential problems.
It is intended to implement a less strict handling of whitespace and
proper processing of SQL comments at some point in the near future.
In any event, 1.7.2 now correctly processes the following JDBC escape
forms to arbitrary nesting depth, but only if the exact whitespace
layout described below is used:
<ol>
<li>{call ...}
<li>{?= call ...}
<li>{fn ...}
<li>{oj ...}
<li>{d ...}
<li>{t ...}
<li>{ts ...}
</ol> <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>nativeSQL</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?'
parameter placeholders</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the native form of this statement</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 clarification:)
or this method is called on a closed connection</dd>
</dl>
</li>
</ul>
<a name="setAutoCommit-boolean-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setAutoCommit</h4>
<pre>public void setAutoCommit(boolean autoCommit)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Sets this connection's auto-commit mode to the given state.
If a connection is in auto-commit mode, then all its SQL
statements will be executed and committed as individual
transactions. Otherwise, its SQL statements are grouped into
transactions that are terminated by a call to either
the method <code>commit</code> or the method <code>rollback</code>.
By default, new connections are in auto-commit
mode.
<P>
The commit occurs when the statement completes. The time when the statement
completes depends on the type of SQL Statement:
<ul>
<li>For DML statements, such as Insert, Update or Delete, and DDL statements,
the statement is complete as soon as it has finished executing.
<li>For Select statements, the statement is complete when the associated result
set is closed.
<li>For <code>CallableStatement</code> objects or for statements that return
multiple results, the statement is complete
when all of the associated result sets have been closed, and all update
counts and output parameters have been retrieved.
</ul>
<P>
<B>NOTE:</B> If this method is called during a transaction and the
auto-commit mode is changed, the transaction is committed. If
<code>setAutoCommit</code> is called and the auto-commit mode is
not changed, the call is a no-op.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Up to and including HSQLDB 2.0,
<ol>
<li> All rows of a result set are retrieved internally <em>
before</em> the first row can actually be fetched.<br>
Therefore, a statement can be considered complete as soon as
any XXXStatement.executeXXX method returns. </li>
</ol>
<p>
Starting with 2.0, HSQLDB may not return a result set to the network
client as a whole; the generic documentation will apply. The fetch
size is taken into account
(campbell-burnet@users) </div> <!-- end release-specific
documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setAutoCommit</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>autoCommit</code> - <code>true</code> to enable auto-commit mode;
<code>false</code> to disable it</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
(JDBC4 Clarification:)
setAutoCommit(true) is called while participating in a distributed transaction,
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getAutoCommit--"><code>getAutoCommit()</code></a></dd>
</dl>
</li>
</ul>
<a name="getAutoCommit--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getAutoCommit</h4>
<pre>public boolean getAutoCommit()
throws java.sql.SQLException</pre>
<div class="block">Retrieves the current auto-commit mode for this <code>Connection</code>
object.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getAutoCommit</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the current state of this <code>Connection</code> object's
auto-commit mode</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setAutoCommit-boolean-"><code>setAutoCommit(boolean)</code></a></dd>
</dl>
</li>
</ul>
<a name="commit--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>commit</h4>
<pre>public void commit()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Makes all changes made since the previous
commit/rollback permanent and releases any database locks
currently held by this <code>Connection</code> object.
This method should be
used only when auto-commit mode has been disabled.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
</div><!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>commit</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
(JDBC4 Clarification:)
this method is called while participating in a distributed transaction,
if this method is called on a closed connection or this
<code>Connection</code> object is in auto-commit mode</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setAutoCommit-boolean-"><code>setAutoCommit(boolean)</code></a></dd>
</dl>
</li>
</ul>
<a name="rollback--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>rollback</h4>
<pre>public void rollback()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Undoes all changes made in the current transaction
and releases any database locks currently held
by this <code>Connection</code> object. This method should be
used only when auto-commit mode has been disabled.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with HSQLDB 1.7.2, savepoints are fully supported both
in SQL and via the JDBC interface. <p>
Using SQL, savepoints may be set, released and used in rollback
as follows:
<pre>
SAVEPOINT <savepoint-name>
RELEASE SAVEPOINT <savepoint-name>
ROLLBACK TO SAVEPOINT <savepoint-name>
</pre>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>rollback</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
(JDBC4 Clarification:)
this method is called while participating in a distributed transaction,
this method is called on a closed connection or this
<code>Connection</code> object is in auto-commit mode</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setAutoCommit-boolean-"><code>setAutoCommit(boolean)</code></a></dd>
</dl>
</li>
</ul>
<a name="close--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>close</h4>
<pre>public void close()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Releases this <code>Connection</code> object's database and JDBC resources
immediately instead of waiting for them to be automatically released.
<P>
Calling the method <code>close</code> on a <code>Connection</code>
object that is already closed is a no-op.
<P>
It is <b>strongly recommended</b> that an application explicitly
commits or rolls back an active transaction prior to calling the
<code>close</code> method. If the <code>close</code> method is called
and there is an active transaction, the results are implementation-defined.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
From 1.7.2, HSQLDB <code>INTERNAL</code> <code>Connection</code>
objects are not closable from JDBC client code. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>close</code> in interface <code>java.lang.AutoCloseable</code></dd>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>close</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - SQLException if a database access error occurs</dd>
</dl>
</li>
</ul>
<a name="isClosed--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>isClosed</h4>
<pre>public boolean isClosed()
throws java.sql.SQLException</pre>
<div class="block">Retrieves whether this <code>Connection</code> object has been
closed. A connection is closed if the method <code>close</code>
has been called on it or if certain fatal errors have occurred.
This method is guaranteed to return <code>true</code> only when
it is called after the method <code>Connection.close</code> has
been called.
<P>
This method generally cannot be called to determine whether a
connection to a database is valid or invalid. A typical client
can determine that a connection is invalid by catching any
exceptions that might be thrown when an operation is attempted.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>isClosed</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd><code>true</code> if this <code>Connection</code> object
is closed; <code>false</code> if it is still open</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs</dd>
</dl>
</li>
</ul>
<a name="getMetaData--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getMetaData</h4>
<pre>public java.sql.DatabaseMetaData getMetaData()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves a <code>DatabaseMetaData</code> object that contains
metadata about the database to which this
<code>Connection</code> object represents a connection.
The metadata includes information about the database's
tables, its supported SQL grammar, its stored
procedures, the capabilities of this connection, and so on.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 essentially supports full database metadata. <p>
For discussion in greater detail, please follow the link to the
overview for JDBCDatabaseMetaData, below.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getMetaData</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a <code>DatabaseMetaData</code> object for this
<code>Connection</code> object</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCDatabaseMetaData.html" title="class in org.hsqldb.jdbc"><code>JDBCDatabaseMetaData</code></a></dd>
</dl>
</li>
</ul>
<a name="setReadOnly-boolean-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setReadOnly</h4>
<pre>public void setReadOnly(boolean readOnly)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Puts this connection in read-only mode as a hint to the driver to enable
database optimizations.
<P><B>Note:</B> This method cannot be called during a transaction.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 supports the SQL standard, which will not allow calls to
this method to succeed during a transaction.<p>
Additionally, HSQLDB provides a way to put a whole database in
read-only mode. This is done by manually adding the line
'readonly=true' to the database's .properties file while the
database is offline. Upon restart, all connections will be
readonly, since the entire database will be readonly. To take
a database out of readonly mode, simply take the database
offline and remove the line 'readonly=true' from the
database's .properties file. Upon restart, the database will
be in regular (read-write) mode. <p>
When a database is put in readonly mode, its files are opened
in readonly mode, making it possible to create CD-based
readonly databases. To create a CD-based readonly database
that has CACHED tables and whose .data file is suspected of
being highly fragmented, it is recommended that the database
first be SHUTDOWN COMPACTed before copying the database
files to CD. This will reduce the space required and may
improve access times against the .data file which holds the
CACHED table data. <p>
Starting with 1.7.2, an alternate approach to opimizing the
.data file before creating a CD-based readonly database is to issue
the CHECKPOINT DEFRAG command followed by SHUTDOWN to take the
database offline in preparation to burn the database files to CD. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setReadOnly</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>readOnly</code> - <code>true</code> enables read-only mode;
<code>false</code> disables it</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection or this
method is called during a transaction</dd>
</dl>
</li>
</ul>
<a name="isReadOnly--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>isReadOnly</h4>
<pre>public boolean isReadOnly()
throws java.sql.SQLException</pre>
<div class="block">Retrieves whether this <code>Connection</code>
object is in read-only mode.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>isReadOnly</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd><code>true</code> if this <code>Connection</code> object
is read-only; <code>false</code> otherwise</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - SQLException if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
</dl>
</li>
</ul>
<a name="setCatalog-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setCatalog</h4>
<pre>public void setCatalog(java.lang.String catalog)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Sets the given catalog name in order to select
a subspace of this <code>Connection</code> object's database
in which to work.
<P>
(JDBC4 Clarification:)<p>
If the driver does not support catalogs, it will
silently ignore this request.
JDBC 4.1[<p>
Calling <code>setCatalog</code> has no effect on previously created or prepared
<code>Statement</code> objects. It is implementation defined whether a DBMS
prepare operation takes place immediately when the <code>Connection</code>
method <code>prepareStatement</code> or <code>prepareCall</code> is invoked.
For maximum portability, <code>setCatalog</code> should be called before a
<code>Statement</code> is created or prepared.]
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB supports a single catalog per database. If the given catalog name
is not the same as the database catalog name, this method throws an
error. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setCatalog</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>catalog</code> - the name of a catalog (subspace in this
<code>Connection</code> object's database) in which to work</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getCatalog--"><code>getCatalog()</code></a></dd>
</dl>
</li>
</ul>
<a name="getCatalog--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getCatalog</h4>
<pre>public java.lang.String getCatalog()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves this <code>Connection</code> object's current catalog name.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB supports a single catalog per database. This method
returns the catalog name for the current database
error. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getCatalog</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the current catalog name or <code>null</code> if there is none</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setCatalog-java.lang.String-"><code>setCatalog(java.lang.String)</code></a></dd>
</dl>
</li>
</ul>
<a name="setTransactionIsolation-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setTransactionIsolation</h4>
<pre>public void setTransactionIsolation(int level)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Attempts to change the transaction isolation level for this
<code>Connection</code> object to the one given.
The constants defined in the interface <code>Connection</code>
are the possible transaction isolation levels.
<P>
<B>Note:</B> If this method is called during a transaction, the result
is implementation-defined.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 accepts all isolation levels. <code>Connection.TRANSACTION_READ_UNCOMMITED</code>
is promoted to <code>Connection.TRANSACTION_READ_COMMITED, but the transactions become read only</code>.
Calling this method during a transaction always succeeds and the selected
isolation level is used from the next transaction.<p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setTransactionIsolation</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>level</code> - one of the following <code>Connection</code> constants:
<code>Connection.TRANSACTION_READ_UNCOMMITTED</code>,
<code>Connection.TRANSACTION_READ_COMMITTED</code>,
<code>Connection.TRANSACTION_REPEATABLE_READ</code>, or
<code>Connection.TRANSACTION_SERIALIZABLE</code>.
(Note that <code>Connection.TRANSACTION_NONE</code> cannot be used
because it specifies that transactions are not supported.)</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 End Clarification)
or the given parameter is not one of the <code>Connection</code>
constants</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCDatabaseMetaData.html#supportsTransactionIsolationLevel-int-"><code>JDBCDatabaseMetaData.supportsTransactionIsolationLevel(int)</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getTransactionIsolation--"><code>getTransactionIsolation()</code></a></dd>
</dl>
</li>
</ul>
<a name="getTransactionIsolation--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getTransactionIsolation</h4>
<pre>public int getTransactionIsolation()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves this <code>Connection</code> object's current
transaction isolation level.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 supports all isolation levels. <code>Connection.TRANSACTION_READ_UNCOMMITED</code>
is promoted to <code>Connection.TRANSACTION_READ_COMMITED</code>.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getTransactionIsolation</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the current transaction isolation level, which will be one
of the following constants:
<code>Connection.TRANSACTION_READ_UNCOMMITTED</code>,
<code>Connection.TRANSACTION_READ_COMMITTED</code>,
<code>Connection.TRANSACTION_REPEATABLE_READ</code>,
<code>Connection.TRANSACTION_SERIALIZABLE</code>, or
<code>Connection.TRANSACTION_NONE</code>.</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCDatabaseMetaData.html#supportsTransactionIsolationLevel-int-"><code>JDBCDatabaseMetaData.supportsTransactionIsolationLevel(int)</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setTransactionIsolation-int-"><code>setTransactionIsolation(int)</code></a></dd>
</dl>
</li>
</ul>
<a name="getWarnings--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getWarnings</h4>
<pre>public java.sql.SQLWarning getWarnings()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves the first warning reported by calls on this
<code>Connection</code> object. If there is more than one
warning, subsequent warnings will be chained to the first one
and can be retrieved by calling the method
<code>SQLWarning.getNextWarning</code> on the warning
that was retrieved previously.
<P>
This method may not be
called on a closed connection; doing so will cause an
<code>SQLException</code> to be thrown.
<P><B>Note:</B> Subsequent warnings will be chained to this
SQLWarning.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB produces warnings whenever a createStatement(),
prepareStatement() or prepareCall() invocation requests an unsupported
but defined combination of result set type, concurrency and holdability,
such that another set is substituted.<p>
Other warnings are typically raised during the execution of data change
and query statements.<p>
Only the warnings caused by the last operation on this connection are
returned by this method. A single operation may return up to 10 chained
warnings.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getWarnings</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the first <code>SQLWarning</code> object or <code>null</code>
if there are none</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs or
this method is called on a closed connection</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>SQLWarning</code></dd>
</dl>
</li>
</ul>
<a name="clearWarnings--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>clearWarnings</h4>
<pre>public void clearWarnings()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Clears all warnings reported for this <code>Connection</code> object.
After a call to this method, the method <code>getWarnings</code>
returns <code>null</code> until a new warning is
reported for this <code>Connection</code> object.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
The standard behaviour is implemented. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>clearWarnings</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - SQLException if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
</dl>
</li>
</ul>
<a name="createStatement-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createStatement</h4>
<pre>public java.sql.Statement createStatement(int resultSetType,
int resultSetConcurrency)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.
This method is the same as the <code>createStatement</code> method
above, but it allows the default result set
type and concurrency to be overridden.
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results. <p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>resultSetType</code> - a result set type; one of
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - a concurrency type; one of
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type and
concurrency</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type and concurrency</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.2</dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
int resultSetType,
int resultSetConcurrency)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>PreparedStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.
This method is the same as the <code>prepareStatement</code> method
above, but it allows the default result set
type and concurrency to be overridden.
(JDBC4 Clarification:)
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results. <p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - a <code>String</code> object that is the SQL statement to
be sent to the database; may contain one or more '?' IN
parameters</dd>
<dd><code>resultSetType</code> - a result set type; one of
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - a concurrency type; one of
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new PreparedStatement object containing the
pre-compiled SQL statement that will produce <code>ResultSet</code>
objects with the given type and concurrency</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type and concurrency</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.2</dd>
</dl>
</li>
</ul>
<a name="prepareCall-java.lang.String-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareCall</h4>
<pre>public java.sql.CallableStatement prepareCall(java.lang.String sql,
int resultSetType,
int resultSetConcurrency)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>CallableStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.
This method is the same as the <code>prepareCall</code> method
above, but it allows the default result set
type and concurrency to be overridden.
(JDBC4 Clarification:)
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results. <p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareCall</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - a <code>String</code> object that is the SQL statement to
be sent to the database; may contain on or more '?' parameters</dd>
<dd><code>resultSetType</code> - a result set type; one of
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - a concurrency type; one of
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>CallableStatement</code> object containing the
pre-compiled SQL statement that will produce <code>ResultSet</code>
objects with the given type and concurrency</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this method
(JDBC4 Clarification:)
is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type and concurrency</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.2</dd>
</dl>
</li>
</ul>
<a name="getTypeMap--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getTypeMap</h4>
<pre>public java.util.Map<java.lang.String,java.lang.Class<?>> getTypeMap()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves the <code>Map</code> object associated with this
<code>Connection</code> object.
Unless the application has added an entry, the type map returned
will be empty.
JDBC 4.1[<p>
You must invoke <code>setTypeMap</code> after making changes to the
<code>Map</code> object returned from
<code>getTypeMap</code> as a JDBC driver may create an internal
copy of the <code>Map</code> object passed to <code>setTypeMap</code>:
<pre>
Map<String,Class<?>> myMap = con.getTypeMap();
myMap.put("mySchemaName.ATHLETES", Athletes.class);
con.setTypeMap(myMap);
</pre>]
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
For compatibility, HSQLDB returns an empty map. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getTypeMap</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the <code>java.util.Map</code> object associated
with this <code>Connection</code> object</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setTypeMap-java.util.Map-"><code>setTypeMap(java.util.Map<java.lang.String, java.lang.Class<?>>)</code></a></dd>
</dl>
</li>
</ul>
<a name="setTypeMap-java.util.Map-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setTypeMap</h4>
<pre>public void setTypeMap(java.util.Map<java.lang.String,java.lang.Class<?>> map)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Installs the given <code>TypeMap</code> object as the type map for
this <code>Connection</code> object. The type map will be used for the
custom mapping of SQL structured types and distinct types.
JDBC4.1[<p>
You must set the the values for the <code>TypeMap</code> prior to
calling <code>setMap</code> as a JDBC driver may create an internal copy
of the <code>TypeMap</code>:
<pre>
Map myMap<String,Class<?>> = new HashMap<String,Class<?>>();
myMap.put("mySchemaName.ATHLETES", Athletes.class);
con.setTypeMap(myMap);
</pre>]
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB does not yet support this feature. Calling this
method always throws a <code>SQLException</code>, stating that
the function is not supported. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setTypeMap</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>map</code> - the <code>java.util.Map</code> object to install
as the replacement for this <code>Connection</code>
object's default type map</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection or
(:JDBC4 Clarification)
the given parameter is not a <code>java.util.Map</code>
object</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getTypeMap--"><code>getTypeMap()</code></a></dd>
</dl>
</li>
</ul>
<a name="setHoldability-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setHoldability</h4>
<pre>public void setHoldability(int holdability)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
(JDBC4 Clarification:)
Changes the default holdability of <code>ResultSet</code> objects
created using this <code>Connection</code> object to the given
holdability. The default holdability of <code>ResultSet</code> objects
can be be determined by invoking
<code>DatabaseMetaData.getResultSetHoldability()</code>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB supports this feature. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setHoldability</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>holdability</code> - a <code>ResultSet</code> holdability constant; one of
<code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> or
<code>ResultSet.CLOSE_CURSORS_AT_COMMIT</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access occurs, this method is called
(JDBC4 Clarification:)
on a closed connection, or the given parameter
(JDBC4 Clarification:)
is not a <code>ResultSet</code> constant indicating holdability</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the given holdability is not supported</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>,
<code>DatabaseMetaData.getResultSetHoldability()</code>,
<a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a></dd>
</dl>
</li>
</ul>
<a name="getHoldability--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getHoldability</h4>
<pre>public int getHoldability()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Retrieves the current holdability of <code>ResultSet</code> objects
created using this <code>Connection</code> object.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB returns the current holdability.<p>
The default is HOLD_CURSORS_OVER_COMMIT. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getHoldability</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the holdability, one of
<code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> or
<code>ResultSet.CLOSE_CURSORS_AT_COMMIT</code></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setHoldability-int-"><code>setHoldability(int)</code></a>,
<code>DatabaseMetaData.getResultSetHoldability()</code>,
<a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a></dd>
</dl>
</li>
</ul>
<a name="setSavepoint--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setSavepoint</h4>
<pre>public java.sql.Savepoint setSavepoint()
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates an unnamed savepoint in the current transaction and
returns the new <code>Savepoint</code> object that represents it.
<p> (JDBC4 clarification:) if setSavepoint is invoked outside of an active transaction, a transaction will be started at this newly created
savepoint.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
From 2.0, HSQLDB supports this feature. <p>
Note: Unnamed savepoints are not part of the SQL:2003 standard.
Use setSavepoint(String name) instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setSavepoint</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the new <code>Savepoint</code> object</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
(JDBC4 Clarification:)
this method is called while participating in a distributed transaction,
this method is called on a closed connection
or this <code>Connection</code> object is currently in
auto-commit mode</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCSavepoint.html" title="class in org.hsqldb.jdbc"><code>JDBCSavepoint</code></a>,
<code>Savepoint</code></dd>
</dl>
</li>
</ul>
<a name="setSavepoint-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setSavepoint</h4>
<pre>public java.sql.Savepoint setSavepoint(java.lang.String name)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a savepoint with the given name in the current transaction
and returns the new <code>Savepoint</code> object that represents it.
<p> if setSavepoint is invoked outside of an active transaction, a transaction will be started at this newly created
savepoint.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Previous to JDBC 4, if the connection is autoCommit,
setting a savepoint has no effect, as it is cleared upon the execution
of the next transactional statement. When built for JDBC 4, this method
throws an SQLException when this <tt>Connection</tt> object is currently
in auto-commit mode, as per the JDBC 4 standard.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setSavepoint</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>name</code> - a <code>String</code> containing the name of the savepoint</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the new <code>Savepoint</code> object</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
(JDBC4 Clarification:)
this method is called while participating in a distributed transaction,
this method is called on a closed connection
or this <code>Connection</code> object is currently in
auto-commit mode</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCSavepoint.html" title="class in org.hsqldb.jdbc"><code>JDBCSavepoint</code></a>,
<code>Savepoint</code></dd>
</dl>
</li>
</ul>
<a name="rollback-java.sql.Savepoint-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>rollback</h4>
<pre>public void rollback(java.sql.Savepoint savepoint)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Undoes all changes made after the given <code>Savepoint</code> object
was set.
<P>
This method should be used only when auto-commit has been disabled.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Previous to JDBC 4, <tt>JDBCSavepoint</tt> objects are valid for the life of
the originating <tt>Connection</tt> object and hence can be used
interchangeably, as long as they have equal savepoint names. <p>
When built for JDBC 4, <tt>JDBCConnection</tt> objects invalidate
<tt>JDBCSavepoint</tt> objects when auto-commit mode is entered as well
as when they are used to successfully release or roll back to a named SQL
savepoint. As per the JDBC 4 standard, when built for JDBC 4, this
method throws an <tt>SQLException</tt> when this <tt>Connection</tt>
object is currently in auto-commit mode and an invalidated
<tt>JDBCSavepoint</tt> is specified.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>rollback</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>savepoint</code> - the <code>Savepoint</code> object to roll back to</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs,
this method is called while participating in a distributed transaction,
this method is called on a closed connection,
the <code>Savepoint</code> object is no longer valid,
or this <code>Connection</code> object is currently in
auto-commit mode</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCSavepoint.html" title="class in org.hsqldb.jdbc"><code>JDBCSavepoint</code></a>,
<code>Savepoint</code>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#rollback--"><code>rollback()</code></a></dd>
</dl>
</li>
</ul>
<a name="releaseSavepoint-java.sql.Savepoint-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>releaseSavepoint</h4>
<pre>public void releaseSavepoint(java.sql.Savepoint savepoint)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Removes the specified <code>Savepoint</code> (JDBC4 Clarification:) and subsequent <code>Savepoint</code> objects from the current
transaction. Any reference to the savepoint after it have been removed
will cause an <code>SQLException</code> to be thrown.
<!-- end generic documentation -->
<b>HSLQDB Note:</b><p>
Previous to JDBC 4, <tt>JDBCSavepoint</tt> objects are valid for the life of
the originating <tt>Connection</tt> object and hence can be used
interchangeably, as long as they have equal savepoint names. <p>
When built for JDBC 4, <tt>JDBCConnection</tt> objects invalidate
<tt>JDBCSavepoint</tt> objects when auto-commit mode is entered as well
as when they are used to successfully release or roll back to a named SQL
savepoint. As per the JDBC 4 standard, when built for JDBC 4, this
method throws an <tt>SQLException</tt> when this <tt>Connection</tt>
object is currently in auto-commit mode and when an invalidated
<tt>JDBCSavepoint</tt> is specified. <p></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>releaseSavepoint</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>savepoint</code> - the <code>Savepoint</code> object to be removed</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection or
the given <code>Savepoint</code> object is not a valid
savepoint in the current transaction</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCSavepoint.html" title="class in org.hsqldb.jdbc"><code>JDBCSavepoint</code></a>,
<code>Savepoint</code></dd>
</dl>
</li>
</ul>
<a name="createStatement-int-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createStatement</h4>
<pre>public java.sql.Statement createStatement(int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type, concurrency,
and holdability.
This method is the same as the <code>createStatement</code> method
above, but it allows the default result set
type, concurrency, and holdability to be overridden.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results. <p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>resultSetType</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dd><code>resultSetHoldability</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> or
<code>ResultSet.CLOSE_CURSORS_AT_COMMIT</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>Statement</code> object that will generate
<code>ResultSet</code> objects with the given type,
concurrency, and holdability</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type, concurrency, and holdability</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type, result set holdability and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a></dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-int-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>PreparedStatement</code> object that will generate
<code>ResultSet</code> objects with the given type, concurrency,
and holdability.
<P>
This method is the same as the <code>prepareStatement</code> method
above, but it allows the default result set
type, concurrency, and holdability to be overridden.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results.<p>
<code>HOLD_CURSORS_OVER_COMMIT</code> is supported only when
<code>CONCUR_READ_ONLY</code> is requested.<p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - a <code>String</code> object that is the SQL statement to
be sent to the database; may contain one or more '?' IN
parameters</dd>
<dd><code>resultSetType</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dd><code>resultSetHoldability</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> or
<code>ResultSet.CLOSE_CURSORS_AT_COMMIT</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>PreparedStatement</code> object, containing the
pre-compiled SQL statement, that will generate
<code>ResultSet</code> objects with the given type,
concurrency, and holdability</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type, concurrency, and holdability</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type, result set holdability and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a></dd>
</dl>
</li>
</ul>
<a name="prepareCall-java.lang.String-int-int-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareCall</h4>
<pre>public java.sql.CallableStatement prepareCall(java.lang.String sql,
int resultSetType,
int resultSetConcurrency,
int resultSetHoldability)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a <code>CallableStatement</code> object that will generate
<code>ResultSet</code> objects with the given type and concurrency.
This method is the same as the <code>prepareCall</code> method
above, but it allows the default result set
type, result set concurrency type and holdability to be overridden.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0 adheres closely to SQL and JDBC standards. The
interpretation of of resultSetType and resultSetConcurrency has
changed in this version.<p>
HSQLDB supports <code>TYPE_FORWARD_ONLY</code>,
<code>TYPE_SCROLL_INSENSITIVE</code>,
<code>CONCUR_READ_ONLY</code>,
<code>CONCUR_UPDATABLE</code>
results. <p>
If an unsupported combination is requested, a SQLWarning is issued on
this Connection and the closest supported combination is used instead. <p>
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareCall</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - a <code>String</code> object that is the SQL statement to
be sent to the database; may contain on or more '?' parameters</dd>
<dd><code>resultSetType</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.TYPE_FORWARD_ONLY</code>,
<code>ResultSet.TYPE_SCROLL_INSENSITIVE</code>, or
<code>ResultSet.TYPE_SCROLL_SENSITIVE</code></dd>
<dd><code>resultSetConcurrency</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.CONCUR_READ_ONLY</code> or
<code>ResultSet.CONCUR_UPDATABLE</code></dd>
<dd><code>resultSetHoldability</code> - one of the following <code>ResultSet</code>
constants:
<code>ResultSet.HOLD_CURSORS_OVER_COMMIT</code> or
<code>ResultSet.CLOSE_CURSORS_AT_COMMIT</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>CallableStatement</code> object, containing the
pre-compiled SQL statement, that will generate
<code>ResultSet</code> objects with the given type,
concurrency, and holdability</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameters are not <code>ResultSet</code>
constants indicating type, concurrency, and holdability</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method or this method is not supported for the specified result
set type, result set holdability and result set concurrency.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCResultSet.html" title="class in org.hsqldb.jdbc"><code>JDBCResultSet</code></a></dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
int autoGeneratedKeys)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a default <code>PreparedStatement</code> object that has
the capability to retrieve auto-generated keys. The given constant
tells the driver whether it should make auto-generated keys
available for retrieval. This parameter is ignored if the SQL statement
is not an <code>INSERT</code> statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
<P>
<B>Note:</B> This method is optimized for handling
parametric SQL statements that benefit from pre-compilation. If
the driver supports pre-compilation,
the method <code>prepareStatement</code> will send
the statement to the database for pre-compilation. Some drivers
may not support pre-compilation. In this case, the statement may
not be sent to the database until the <code>PreparedStatement</code>
object is executed. This has no direct effect on users; however, it does
affect which methods throw certain SQLExceptions.
<P>
Result sets created using the returned <code>PreparedStatement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
(JDBC4 Clarification:)
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with version 2.0, HSQLDB supports returning generated columns
with single-row and multi-row INSERT, UPDATE and MERGE statements. <p>
If the table has an IDENTITY or GENERATED column(s) the values for these
columns are returned in the next call to getGeneratedKeys() after each
execution of the PreparedStatement.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?' IN
parameter placeholders</dd>
<dd><code>autoGeneratedKeys</code> - a flag indicating whether auto-generated keys
should be returned; one of
<code>Statement.RETURN_GENERATED_KEYS</code> or
<code>Statement.NO_GENERATED_KEYS</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>PreparedStatement</code> object, containing the
pre-compiled SQL statement, that will have the capability of
returning auto-generated keys</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
(JDBC4 Clarification:)
method is called on a closed connection
(:JDBC4 Clarification)
or the given parameter is not a <code>Statement</code>
constant indicating whether auto-generated keys should be
returned</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method with a constant of Statement.RETURN_GENERATED_KEYS</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-int:A-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
int[] columnIndexes)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a default <code>PreparedStatement</code> object capable
of returning the auto-generated keys designated by the given array.
This array contains the indexes of the columns in the target
table that contain the auto-generated keys that should be made
available. The driver will ignore the array if the SQL statement
is not an <code>INSERT</code> statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
<p>
An SQL statement with or without IN parameters can be
pre-compiled and stored in a <code>PreparedStatement</code> object. This
object can then be used to efficiently execute this statement
multiple times.
<P>
<B>Note:</B> This method is optimized for handling
parametric SQL statements that benefit from pre-compilation. If
the driver supports pre-compilation,
the method <code>prepareStatement</code> will send
the statement to the database for pre-compilation. Some drivers
may not support pre-compilation. In this case, the statement may
not be sent to the database until the <code>PreparedStatement</code>
object is executed. This has no direct effect on users; however, it does
affect which methods throw certain SQLExceptions.
<P>
Result sets created using the returned <code>PreparedStatement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
(JDBC4 Clarification:)
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with version 2.0, HSQLDB supports returning generated columns
with single-row and multi-row INSERT, UPDATE and MERGE statements. <p>
The columnIndexes may specify any set of columns of the table.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?' IN
parameter placeholders</dd>
<dd><code>columnIndexes</code> - an array of column indexes indicating the columns
that should be returned from the inserted row or rows</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>PreparedStatement</code> object, containing the
pre-compiled statement, that is capable of returning the
auto-generated keys designated by the given array of column
indexes</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
</dl>
</li>
</ul>
<a name="prepareStatement-java.lang.String-java.lang.String:A-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>prepareStatement</h4>
<pre>public java.sql.PreparedStatement prepareStatement(java.lang.String sql,
java.lang.String[] columnNames)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Creates a default <code>PreparedStatement</code> object capable
of returning the auto-generated keys designated by the given array.
This array contains the names of the columns in the target
table that contain the auto-generated keys that should be returned.
The driver will ignore the array if the SQL statement
is not an <code>INSERT</code> statement, or an SQL statement able to return
auto-generated keys (the list of such statements is vendor-specific).
<P>
An SQL statement with or without IN parameters can be
pre-compiled and stored in a <code>PreparedStatement</code> object. This
object can then be used to efficiently execute this statement
multiple times.
<P>
<B>Note:</B> This method is optimized for handling
parametric SQL statements that benefit from pre-compilation. If
the driver supports pre-compilation,
the method <code>prepareStatement</code> will send
the statement to the database for pre-compilation. Some drivers
may not support pre-compilation. In this case, the statement may
not be sent to the database until the <code>PreparedStatement</code>
object is executed. This has no direct effect on users; however, it does
affect which methods throw certain SQLExceptions.
<P>
Result sets created using the returned <code>PreparedStatement</code>
object will by default be type <code>TYPE_FORWARD_ONLY</code>
and have a concurrency level of <code>CONCUR_READ_ONLY</code>.
(JDBC4 Clarification:)
The holdability of the created result sets can be determined by
calling <a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getHoldability--"><code>getHoldability()</code></a>.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
Starting with version 2.0, HSQLDB supports returning generated columns
with single-row and multi-row INSERT, UPDATE and MERGE statements. <p>
The columnNames may specify any set of columns of the table. The names
are case-sensitive, unlike column names in ResultSet methods.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>prepareStatement</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>sql</code> - an SQL statement that may contain one or more '?' IN
parameter placeholders</dd>
<dd><code>columnNames</code> - an array of column names indicating the columns
that should be returned from the inserted row or rows</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a new <code>PreparedStatement</code> object, containing the
pre-compiled statement, that is capable of returning the
auto-generated keys designated by the given array of column
names</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
(JDBC4 Clarification:)
or this method is called on a closed connection</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.4, HSQLDB 1.7.2</dd>
</dl>
</li>
</ul>
<a name="createClob--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createClob</h4>
<pre>public java.sql.Clob createClob()
throws java.sql.SQLException</pre>
<div class="block">Constructs an object that implements the <code>Clob</code> interface. The object
returned initially contains no data. The <code>setAsciiStream</code>,
<code>setCharacterStream</code> and <code>setString</code> methods of
the <code>Clob</code> interface may be used to add data to the <code>Clob</code>.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createClob</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>An object that implements the <code>Clob</code> interface</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if an object that implements the
<code>Clob</code> interface can not be constructed, this method is
called on a closed connection or a database access error occurs.</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="createBlob--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createBlob</h4>
<pre>public java.sql.Blob createBlob()
throws java.sql.SQLException</pre>
<div class="block">Constructs an object that implements the <code>Blob</code> interface. The object
returned initially contains no data. The <code>setBinaryStream</code> and
<code>setBytes</code> methods of the <code>Blob</code> interface may be used to add data to
the <code>Blob</code>.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createBlob</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>An object that implements the <code>Blob</code> interface</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if an object that implements the
<code>Blob</code> interface can not be constructed, this method is
called on a closed connection or a database access error occurs.</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="createNClob--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createNClob</h4>
<pre>public java.sql.NClob createNClob()
throws java.sql.SQLException</pre>
<div class="block">Constructs an object that implements the <code>NClob</code> interface. The object
returned initially contains no data. The <code>setAsciiStream</code>,
<code>setCharacterStream</code> and <code>setString</code> methods of the <code>NClob</code> interface may
be used to add data to the <code>NClob</code>.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createNClob</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>An object that implements the <code>NClob</code> interface</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if an object that implements the
<code>NClob</code> interface can not be constructed, this method is
called on a closed connection or a database access error occurs.</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="createSQLXML--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createSQLXML</h4>
<pre>public java.sql.SQLXML createSQLXML()
throws java.sql.SQLException</pre>
<div class="block">Constructs an object that implements the <code>SQLXML</code> interface. The object
returned initially contains no data. The <code>createXmlStreamWriter</code> object and
<code>setString</code> method of the <code>SQLXML</code> interface may be used to add data to the <code>SQLXML</code>
object.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createSQLXML</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>An object that implements the <code>SQLXML</code> interface</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if an object that implements the <code>SQLXML</code> interface can not
be constructed, this method is
called on a closed connection or a database access error occurs.</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="isValid-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>isValid</h4>
<pre>public boolean isValid(int timeout)
throws java.sql.SQLException</pre>
<div class="block"><!-- start generic documentation -->
Returns true if the connection has not been closed and is still valid.
The driver shall submit a query on the connection or use some other
mechanism that positively verifies the connection is still valid when
this method is called.
<p>
The query submitted by the driver to validate the connection shall be
executed in the context of the current transaction.
<!-- end generic documentation -->
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB uses a maximum timeout of 60 seconds if timeout has be specified
as zero.
</div> <!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>isValid</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>timeout</code> - - The time in seconds to wait for the database operation
used to validate the connection to complete. If
the timeout period expires before the operation
completes, this method returns false. A value of
0 indicates a timeout is not applied to the
database operation.</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>true if the connection is valid, false otherwise</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if the value supplied for <code>timeout</code>
is less then 0</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCDatabaseMetaData.html#getClientInfoProperties--"><code>JDBCDatabaseMetaData.getClientInfoProperties()</code></a></dd>
</dl>
</li>
</ul>
<a name="setClientInfo-java.lang.String-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setClientInfo</h4>
<pre>public void setClientInfo(java.lang.String name,
java.lang.String value)
throws java.sql.SQLClientInfoException</pre>
<div class="block">Sets the value of the client info property specified by name to the
value specified by value.
<p>
Applications may use the <code>DatabaseMetaData.getClientInfoProperties</code>
method to determine the client info properties supported by the driver
and the maximum length that may be specified for each property.
<p>
The driver stores the value specified in a suitable location in the
database. For example in a special register, session parameter, or
system table column. For efficiency the driver may defer setting the
value in the database until the next time a statement is executed or
prepared. Other than storing the client information in the appropriate
place in the database, these methods shall not alter the behavior of
the connection in anyway. The values supplied to these methods are
used for accounting, diagnostics and debugging purposes only.
<p>
The driver shall generate a warning if the client info name specified
is not recognized by the driver.
<p>
If the value specified to this method is greater than the maximum
length for the property the driver may either truncate the value and
generate a warning or generate a <code>SQLClientInfoException</code>. If the driver
generates a <code>SQLClientInfoException</code>, the value specified was not set on the
connection.
<p>
The following are standard client info properties. Drivers are not
required to support these properties however if the driver supports a
client info property that can be described by one of the standard
properties, the standard property name should be used.
<ul>
<li>ApplicationName - The name of the application currently utilizing
the connection</li>
<li>ClientUser - The name of the user that the application using
the connection is performing work for. This may
not be the same as the user name that was used
in establishing the connection.</li>
<li>ClientHostname - The host name of the computer the application
using the connection is running on.</li>
</ul>
<!-- start release-specific documentation -->
<div class="ReleaseSpecificDocumentation">
<h3>HSQLDB-Specific Information:</h3> <p>
HSQLDB 2.0, throws an SQLClientInfoException when this method is
called.
</div>
<!-- end release-specific documentation --></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setClientInfo</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>name</code> - The name of the client info property to set</dd>
<dd><code>value</code> - The value to set the client info property to. If the
value is null, the current value of the specified
property is cleared.
<p></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLClientInfoException</code> - if the database server returns an error while
setting the client info value on the database server or this method
is called on a closed connection
<p></dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="setClientInfo-java.util.Properties-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setClientInfo</h4>
<pre>public void setClientInfo(java.util.Properties properties)
throws java.sql.SQLClientInfoException</pre>
<div class="block">Sets the value of the connection's client info properties. The
<code>Properties</code> object contains the names and values of the client info
properties to be set. The set of client info properties contained in
the properties list replaces the current set of client info properties
on the connection. If a property that is currently set on the
connection is not present in the properties list, that property is
cleared. Specifying an empty properties list will clear all of the
properties on the connection. See <code>setClientInfo (String, String)</code> for
more information.
<p>
If an error occurs in setting any of the client info properties, a
<code>SQLClientInfoException</code> is thrown. The <code>SQLClientInfoException</code>
contains information indicating which client info properties were not set.
The state of the client information is unknown because
some databases do not allow multiple client info properties to be set
atomically. For those databases, one or more properties may have been
set before the error occurred.
<p></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setClientInfo</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>properties</code> - the list of client info properties to set
<p></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLClientInfoException</code> - if the database server returns an error while
setting the clientInfo values on the database server or this method
is called on a closed connection</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0
<p></dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>setClientInfo(String, String)</code></dd>
</dl>
</li>
</ul>
<a name="getClientInfo-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getClientInfo</h4>
<pre>public java.lang.String getClientInfo(java.lang.String name)
throws java.sql.SQLException</pre>
<div class="block">Returns the value of the client info property specified by name. This
method may return null if the specified client info property has not
been set and does not have a default value. This method will also
return null if the specified client info property name is not supported
by the driver.
<p>
Applications may use the <code>DatabaseMetaData.getClientInfoProperties</code>
method to determine the client info properties supported by the driver.
<p></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getClientInfo</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>name</code> - The name of the client info property to retrieve
<p></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>The value of the client info property specified
<p></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if the database server returns an error when
fetching the client info value from the database
or this method is called on a closed connection
<p></dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>DatabaseMetaData.getClientInfoProperties()</code></dd>
</dl>
</li>
</ul>
<a name="getClientInfo--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getClientInfo</h4>
<pre>public java.util.Properties getClientInfo()
throws java.sql.SQLException</pre>
<div class="block">Returns a list containing the name and current value of each client info
property supported by the driver. The value of a client info property
may be null if the property has not been set and does not have a
default value.
<p></div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getClientInfo</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>A <code>Properties</code> object that contains the name and current value of
each of the client info properties supported by the driver.
<p></dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if the database server returns an error when
fetching the client info values from the database
or this method is called on a closed connection
<p></dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="createArrayOf-java.lang.String-java.lang.Object:A-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createArrayOf</h4>
<pre>public java.sql.Array createArrayOf(java.lang.String typeName,
java.lang.Object[] elements)
throws java.sql.SQLException</pre>
<div class="block">Factory method for creating Array objects.
<p>
<b>Note: </b>When <code>createArrayOf</code> is used to create an array object
that maps to a primitive data type, then it is implementation-defined
whether the <code>Array</code> object is an array of that primitive
data type or an array of <code>Object</code>.
<p>
<b>Note: </b>The JDBC driver is responsible for mapping the elements
<code>Object</code> array to the default JDBC SQL type defined in
java.sql.Types for the given class of <code>Object</code>. The default
mapping is specified in Appendix B of the JDBC specification. If the
resulting JDBC type is not the appropriate type for the given typeName then
it is implementation defined whether an <code>SQLException</code> is
thrown or the driver supports the resulting conversion.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createArrayOf</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>typeName</code> - the SQL name of the type the elements of the array map to. The typeName is a
database-specific name which may be the name of a built-in type, a user-defined type or a standard SQL type supported by this database. This
is the value returned by <code>Array.getBaseTypeName</code></dd>
<dd><code>elements</code> - the elements that populate the returned object</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>an Array object whose elements map to the specified SQL type</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database error occurs, the JDBC type is not
appropriate for the typeName and the conversion is not supported, the typeName is null or this method is called on a closed connection</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>1.6</dd>
</dl>
</li>
</ul>
<a name="createStruct-java.lang.String-java.lang.Object:A-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>createStruct</h4>
<pre>public java.sql.Struct createStruct(java.lang.String typeName,
java.lang.Object[] attributes)
throws java.sql.SQLException</pre>
<div class="block">Factory method for creating Struct objects.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>createStruct</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>typeName</code> - the SQL type name of the SQL structured type that this <code>Struct</code>
object maps to. The typeName is the name of a user-defined type that
has been defined for this database. It is the value returned by
<code>Struct.getSQLTypeName</code>.</dd>
<dd><code>attributes</code> - the attributes that populate the returned object</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>a Struct object that maps to the given SQL type and is populated with the given attributes</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database error occurs, the typeName is null or this method is called on a closed connection</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support this data type</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6_b80, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="unwrap-java.lang.Class-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>unwrap</h4>
<pre>public <T> T unwrap(java.lang.Class<T> iface)
throws java.sql.SQLException</pre>
<div class="block">Returns an object that implements the given interface to allow access to
non-standard methods, or standard methods not exposed by the proxy.
If the receiver implements the interface then the result is the receiver
or a proxy for the receiver. If the receiver is a wrapper
and the wrapped object implements the interface then the result is the
wrapped object or a proxy for the wrapped object. Otherwise return the
the result of calling <code>unwrap</code> recursively on the wrapped object
or a proxy for that result. If the receiver is not a
wrapper and does not implement the interface, then an <code>SQLException</code> is thrown.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>unwrap</code> in interface <code>java.sql.Wrapper</code></dd>
<dt><span class="paramLabel">Type Parameters:</span></dt>
<dd><code>T</code> - by which the return type is inferred from input parameter.</dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>iface</code> - A Class defining an interface that the result must implement.</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>an object that implements the interface. May be a proxy for the actual implementing object.</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - If no object found that implements the interface</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="isWrapperFor-java.lang.Class-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>isWrapperFor</h4>
<pre>public boolean isWrapperFor(java.lang.Class<?> iface)
throws java.sql.SQLException</pre>
<div class="block">Returns true if this either implements the interface argument or is directly or indirectly a wrapper
for an object that does. Returns false otherwise. If this implements the interface then return true,
else if this is a wrapper then return the result of recursively calling <code>isWrapperFor</code> on the wrapped
object. If this does not implement the interface and is not a wrapper, return false.
This method should be implemented as a low-cost operation compared to <code>unwrap</code> so that
callers can use this method to avoid expensive <code>unwrap</code> calls that may fail. If this method
returns true then calling <code>unwrap</code> with the same argument should succeed.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>isWrapperFor</code> in interface <code>java.sql.Wrapper</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>iface</code> - a Class defining an interface.</dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>true if this implements the interface or directly or indirectly wraps an object that does.</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if an error occurs while determining whether this is a wrapper
for an object with the given interface.</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.6, HSQLDB 2.0</dd>
</dl>
</li>
</ul>
<a name="setSchema-java.lang.String-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setSchema</h4>
<pre>public void setSchema(java.lang.String schema)
throws java.sql.SQLException</pre>
<div class="block">Sets the given schema name to access.
<P>
If the driver does not support schemas, it will
silently ignore this request.
<p>
Calling <code>setSchema</code> has no effect on previously created or prepared
<code>Statement</code> objects. It is implementation defined whether a DBMS
prepare operation takes place immediately when the <code>Connection</code>
method <code>prepareStatement</code> or <code>prepareCall</code> is invoked.
For maximum portability, <code>setSchema</code> should be called before a
<code>Statement</code> is created or prepared.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setSchema</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>schema</code> - the name of a schema in which to work</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
or this method is called on a closed connection</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.7, HSQLDB 2.0.1</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getSchema--"><code>getSchema()</code></a></dd>
</dl>
</li>
</ul>
<a name="getSchema--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getSchema</h4>
<pre>public java.lang.String getSchema()
throws java.sql.SQLException</pre>
<div class="block">Retrieves this <code>Connection</code> object's current schema name.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getSchema</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the current schema name or <code>null</code> if there is none</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs
or this method is called on a closed connection</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.7 M11 2010/09/10 (b123), HSQLDB 2.0.1</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setSchema-java.lang.String-"><code>setSchema(java.lang.String)</code></a></dd>
</dl>
</li>
</ul>
<a name="abort-java.util.concurrent.Executor-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>abort</h4>
<pre>public void abort(java.util.concurrent.Executor executor)
throws java.sql.SQLException</pre>
<div class="block">Terminates an open connection. Calling <code>abort</code> results in:
<ul>
<li>The connection marked as closed
<li>Closes any physical connection to the database
<li>Releases resources used by the connection
<li>Insures that any thread that is currently accessing the connection
will either progress to completion or throw an <code>SQLException</code>.
</ul>
<p>
Calling <code>abort</code> marks the connection closed and releases any
resources. Calling <code>abort</code> on a closed connection is a
no-op.
<p>
It is possible that the aborting and releasing of the resources that are
held by the connection can take an extended period of time. When the
<code>abort</code> method returns, the connection will have been marked as
closed and the <code>Executor</code> that was passed as a parameter to abort
may still be executing tasks to release resources.
<p>
This method checks to see that there is an <code>SQLPermission</code>
object before allowing the method to proceed. If a
<code>SecurityManager</code> exists and its
<code>checkPermission</code> method denies calling <code>abort</code>,
this method throws a
<code>java.lang.SecurityException</code>.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>abort</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>executor</code> - The <code>Executor</code> implementation which will
be used by <code>abort</code>.</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs or
the <code>executor</code> is <code>null</code>,</dd>
<dd><code>java.lang.SecurityException</code> - if a security manager exists and its
<code>checkPermission</code> method denies calling <code>abort</code></dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.7, HSQLDB 2.0.1</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>SecurityManager.checkPermission(java.security.Permission)</code>,
<code>Executor</code></dd>
</dl>
</li>
</ul>
<a name="setNetworkTimeout-java.util.concurrent.Executor-int-">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>setNetworkTimeout</h4>
<pre>public void setNetworkTimeout(java.util.concurrent.Executor executor,
int milliseconds)
throws java.sql.SQLException</pre>
<div class="block">Sets the maximum period a <code>Connection</code> or
objects created from the <code>Connection</code>
will wait for the database to reply to any one request. If any
request remains unanswered, the waiting method will
return with a <code>SQLException</code>, and the <code>Connection</code>
or objects created from the <code>Connection</code> will be marked as
closed. Any subsequent use of
the objects, with the exception of the <code>close</code>,
<code>isClosed</code> or <code>Connection.isValid</code>
methods, will result in a <code>SQLException</code>.
<p>
<b>Note</b>: This method is intended to address a rare but serious
condition where network partitions can cause threads issuing JDBC calls
to hang uninterruptedly in socket reads, until the OS TCP-TIMEOUT
(typically 10 minutes). This method is related to the
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#abort-java.util.concurrent.Executor-"><code>abort() </code></a> method which provides an administrator
thread a means to free any such threads in cases where the
JDBC connection is accessible to the administrator thread.
The <code>setNetworkTimeout</code> method will cover cases where
there is no administrator thread, or it has no access to the
connection. This method is severe in it's effects, and should be
given a high enough value so it is never triggered before any more
normal timeouts, such as transaction timeouts.
<p>
JDBC driver implementations may also choose to support the
<code>setNetworkTimeout</code> method to impose a limit on database
response time, in environments where no network is present.
<p>
Drivers may internally implement some or all of their API calls with
multiple internal driver-database transmissions, and it is left to the
driver implementation to determine whether the limit will be
applied always to the response to the API call, or to any
single request made during the API call.
<p>
This method can be invoked more than once, such as to set a limit for an
area of JDBC code, and to reset to the default on exit from this area.
Invocation of this method has no impact on already outstanding
requests.
<p>
The <code>Statement.setQueryTimeout()</code> timeout value is independent of the
timeout value specified in <code>setNetworkTimeout</code>. If the query timeout
expires before the network timeout then the
statement execution will be canceled. If the network is still
active the result will be that both the statement and connection
are still usable. However if the network timeout expires before
the query timeout or if the statement timeout fails due to network
problems, the connection will be marked as closed, any resources held by
the connection will be released and both the connection and
statement will be unusable.
<p>
When the driver determines that the <code>setNetworkTimeout</code> timeout
value has expired, the JDBC driver marks the connection
closed and releases any resources held by the connection.
<p>
This method checks to see that there is an <code>SQLPermission</code>
object before allowing the method to proceed. If a
<code>SecurityManager</code> exists and its
<code>checkPermission</code> method denies calling
<code>setNetworkTimeout</code>, this method throws a
<code>java.lang.SecurityException</code>.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>setNetworkTimeout</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="paramLabel">Parameters:</span></dt>
<dd><code>executor</code> - The <code>Executor</code> implementation which will
be used by <code>setNetworkTimeout</code>.</dd>
<dd><code>milliseconds</code> - The time in milliseconds to wait for the database
operation
to complete. If the JDBC driver does not support milliseconds, the
JDBC driver will round the value up to the nearest second. If the
timeout period expires before the operation
completes, a SQLException will be thrown.
A value of 0 indicates that there is not timeout for database operations.</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs, this
method is called on a closed connection,
the <code>executor</code> is <code>null</code>,
or the value specified for <code>seconds</code> is less than 0.</dd>
<dd><code>java.lang.SecurityException</code> - if a security manager exists and its
<code>checkPermission</code> method denies calling
<code>setNetworkTimeout</code>.</dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.7 M11 2010/09/10 (b123), HSQLDB 2.0.1</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><code>SecurityManager.checkPermission(java.security.Permission)</code>,
<code>Statement.setQueryTimeout(int)</code>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#getNetworkTimeout--"><code>getNetworkTimeout()</code></a>,
<a href="../../../org/hsqldb/jdbc/JDBCConnection.html#abort-java.util.concurrent.Executor-"><code>abort(java.util.concurrent.Executor)</code></a>,
<code>Executor</code></dd>
</dl>
</li>
</ul>
<a name="getNetworkTimeout--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>getNetworkTimeout</h4>
<pre>public int getNetworkTimeout()
throws java.sql.SQLException</pre>
<div class="block">Retrieves the number of milliseconds the driver will
wait for a database request to complete.
If the limit is exceeded, a
<code>SQLException</code> is thrown.</div>
<dl>
<dt><span class="overrideSpecifyLabel">Specified by:</span></dt>
<dd><code>getNetworkTimeout</code> in interface <code>java.sql.Connection</code></dd>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the current timeout limit in milliseconds; zero means there is
no limit</dd>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs or
this method is called on a closed <code>Connection</code></dd>
<dd><code>java.sql.SQLFeatureNotSupportedException</code> - if the JDBC driver does not support
this method</dd>
<dt><span class="simpleTagLabel">Since:</span></dt>
<dd>JDK 1.7 M11 2010/09/10 (b123), HSQLDB 2.0.1</dd>
<dt><span class="seeLabel">See Also:</span></dt>
<dd><a href="../../../org/hsqldb/jdbc/JDBCConnection.html#setNetworkTimeout-java.util.concurrent.Executor-int-"><code>setNetworkTimeout(java.util.concurrent.Executor, int)</code></a></dd>
</dl>
</li>
</ul>
<a name="reset--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>reset</h4>
<pre>public void reset()
throws java.sql.SQLException</pre>
<div class="block">Resets this connection so it can be used again. Used when connections are
returned to a connection pool.</div>
<dl>
<dt><span class="throwsLabel">Throws:</span></dt>
<dd><code>java.sql.SQLException</code> - if a database access error occurs</dd>
</dl>
</li>
</ul>
<a name="closeFully--">
<!-- -->
</a>
<ul class="blockList">
<li class="blockList">
<h4>closeFully</h4>
<pre>public void closeFully()</pre>
<div class="block">Completely closes a pooled connection</div>
</li>
</ul>
<a name="getSession--">
<!-- -->
</a>
<ul class="blockListLast">
<li class="blockList">
<h4>getSession</h4>
<pre>public org.hsqldb.SessionInterface getSession()</pre>
<div class="block">provides cross-package access to the proprietary (i.e. non-JDBC)
HSQLDB session interface. <P></div>
<dl>
<dt><span class="returnLabel">Returns:</span></dt>
<dd>the underlying sessionProxy for this connection</dd>
</dl>
</li>
</ul>
</li>
</ul>
</li>
</ul>
</div>
</div>
<!-- ========= END OF CLASS DATA ========= -->
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<div class="bottomNav"><a name="navbar.bottom">
<!-- -->
</a>
<div class="skipNav"><a href="#skip.navbar.bottom" title="Skip navigation links">Skip navigation links</a></div>
<a name="navbar.bottom.firstrow">
<!-- -->
</a>
<ul class="navList" title="Navigation">
<li><a href="../../../overview-summary.html">Overview</a></li>
<li><a href="package-summary.html">Package</a></li>
<li class="navBarCell1Rev">Class</li>
<li><a href="class-use/JDBCConnection.html">Use</a></li>
<li><a href="package-tree.html">Tree</a></li>
<li><a href="../../../deprecated-list.html">Deprecated</a></li>
<li><a href="../../../index-all.html">Index</a></li>
<li><a href="../../../help-doc.html">Help</a></li>
</ul>
</div>
<div class="subNav">
<ul class="navList">
<li><a href="../../../org/hsqldb/jdbc/JDBCCommonDataSource.html" title="class in org.hsqldb.jdbc"><span class="typeNameLink">Prev Class</span></a></li>
<li><a href="../../../org/hsqldb/jdbc/JDBCConnectionEventListener.html" title="interface in org.hsqldb.jdbc"><span class="typeNameLink">Next Class</span></a></li>
</ul>
<ul class="navList">
<li><a href="../../../index.html?org/hsqldb/jdbc/JDBCConnection.html" target="_top">Frames</a></li>
<li><a href="JDBCConnection.html" target="_top">No Frames</a></li>
</ul>
<ul class="navList" id="allclasses_navbar_bottom">
<li><a href="../../../allclasses-noframe.html">All Classes</a></li>
</ul>
<div>
<script type="text/javascript"><!--
allClassesLink = document.getElementById("allclasses_navbar_bottom");
if(window==top) {
allClassesLink.style.display = "block";
}
else {
allClassesLink.style.display = "none";
}
//-->
</script>
</div>
<div>
<ul class="subNavList">
<li>Summary: </li>
<li>Nested | </li>
<li>Field | </li>
<li><a href="#constructor.summary">Constr</a> | </li>
<li><a href="#method.summary">Method</a></li>
</ul>
<ul class="subNavList">
<li>Detail: </li>
<li>Field | </li>
<li><a href="#constructor.detail">Constr</a> | </li>
<li><a href="#method.detail">Method</a></li>
</ul>
</div>
<a name="skip.navbar.bottom">
<!-- -->
</a></div>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
<p class="legalCopy"><small><i>Copyright �� 2001 - 2017 HSQL Development Group.</i></small></p>
</body>
</html>
