- All Implemented Interfaces:
DatabaseMetaData
,Wrapper
This interface is implemented by driver vendors to let users know the capabilities of a Database Management System (DBMS) in combination with the driver based on JDBC technology ("JDBC driver") that is used with it. Different relational DBMSs often support different features, implement features in different ways, and use different data types. In addition, a driver may implement a feature on top of what the DBMS offers. Information returned by methods in this interface applies to the capabilities of a particular driver and a particular DBMS working together. Note that as used in this documentation, the term "database" is used generically to refer to both the driver and DBMS.
A user for this interface is commonly a tool that needs to discover how to
deal with the underlying DBMS. This is especially true for applications
that are intended to be used with more than one DBMS. For example, a tool might use the method
getTypeInfo
to find out what data types can be used in a
CREATE TABLE
statement. Or a user might call the method
supportsCorrelatedSubqueries
to see if it is possible to use
a correlated subquery or supportsBatchUpdates
to see if it is
possible to use batch updates.
Some DatabaseMetaData
methods return lists of information
in the form of ResultSet
objects.
Regular ResultSet
methods, such as
getString
and getInt
, can be used
to retrieve the data from these ResultSet
objects. If
a given form of metadata is not available, an empty ResultSet
will be returned. Additional columns beyond the columns defined to be
returned by the ResultSet
object for a given method
can be defined by the JDBC driver vendor and must be accessed
by their column label.
Some DatabaseMetaData
methods take arguments that are
String patterns. These arguments all have names such as fooPattern.
Within a pattern String, "%" means match any substring of 0 or more
characters, and "_" means match any one character. Only metadata
entries matching the search pattern are returned. If a search pattern
argument is set to null
, that argument's criterion will
be dropped from the search.
A method that gets information about a feature that the driver does not
support will throw an SQLException
.
In the case of methods that return a ResultSet
object, either a ResultSet
object (which may be empty) is
returned or an SQLException
is thrown.
HSQLDB-Specific Information:
Metadata Table Production
Starting with HSQLDB 1.7.2, the metadata table (a.k.a system table) production implementation provided in the default build filters metadata based on each SQL session user's access rights which in turn lifts the pre-HSQLDB 1.7.2 restriction that only users with the DBA role ('admin' users in older HSQLDB parlance) could expect trouble-free access to all metadata.
Also starting with HSQLDB 1.7.2, the metadata table production implementation
classes are loaded dynamically, using a precedence policy to find and load
the richest producer available at runtime. In the event that no better
alternative is found, the default minimal (completely restricted) provider
is selected. Under this scheme, it is possible for third party packagers to
create custom distributions targeted at supporting full (design-time),
custom-written (proprietary / micro environment), minimal (production-time)
or completely-restricted (space-constrained | device embedded | real-time |
hostile environment) metadata table production scenarios. To learn more
about this option, interested parties can review the documentation and source
code for the org.hsqldb.dbinfo.DatabaseInformation class
.
Please also note that in addition to the metadata tables produced to directly support this class, starting with HSQLDB 1.7.2, the default build provides many additional tables covering all or most HSQLDB features, such as descriptions of the triggers and aliases defined in the database.
For instance, in the default build, a fairly comprehensive description of
each INFORMATION_SCHEMA table and each INFORMATION_SCHEMA table
column is included in the REMARKS column of the getTables(...)
and getColumns(...)
results, which derive
from INFORMATION_SCHEMA.SYSTEM_TABLES and INFORMATION_SCHEMA.SYSTEM_COLUMNS,
respectively.
Since HSQLDB 2.0 the INFORMATION_SCHEMA views have been vastly expanded in compliance with the SQL:2011 Standard and report the properties of all database objects.
Schema Metadata
The SQL SCHEMA concept became fully supported in the HSQLDB 1.8.x series and this fact is reflected in the all subsequent versions of this class.Catalog Metadata
Starting with HSQLDB 2.0, SQL standards compliance up to SQL:2008 and beyond is a major theme which is reflected in the provision of the majority of the standard-defined full-name INFORMATION_SCHEMA views.However, just as CATALOG semantics and handling are still considered to be implementation defined by the most recent SQL standard (SQL:2011), so is the HSQLDB CATALOG concept still in the process of being defined and refined in HSQLDB 2.x. and beyond.
Similarly, starting with HSQLDB 2.x, from the perspective of SQL identification, an HSQLDB JDBC URL connects to a single HSQLDB database instance which consists of a single, default CATALOG named PUBLIC in which each SCHEMA instance of the database resides. The name of this catalog can be changed with the ALTER CATALOG <name> RENAME TO statement. As of version 2.1.0, HSQLDB supports qualification by the containing CATALOG of database objects at the syntactic level, but does not yet support operations such as opening, manipulating or querying against multiple database catalogs within a single session, not even in a one-at-a-time fashion.
Index Metadata
It must still be noted that as of the most recent release, HSQLDB continues to ignore theapproximate
argument of getIndexInfo()
as no data is returned for CARDINALITY and PAGES coloumns.
Notes for developers extending metadata table production
Note that in the absence of an ORDER BY clause, queries against the metadata tables that directly support this class are expected to return rows in JDBC contract order. The reason for this is that results typically come back much faster when no "ORDER BY" clause is used.As such, when adding, extending or replacing a JDBC database metadata table production routine, developers need to be aware of this fact and either add the contract "ORDER BY" clause to the driving SQL or, when possible, preferably maintain rows in the contract order by correctly coding the primary index definition in the table producer class.
(fredt@users)
(campbell-burnet@users)
- Since:
- HSQLDB 1.9.0
- Author:
- Campbell Burnet (campbell-burnet@users dot sourceforge.net), Fred Toussi (fredt@users dot sourceforge.net)
- See Also:
-
Field Summary
FieldsFields inherited from interface java.sql.DatabaseMetaData
attributeNoNulls, attributeNullable, attributeNullableUnknown, bestRowNotPseudo, bestRowPseudo, bestRowSession, bestRowTemporary, bestRowTransaction, bestRowUnknown, columnNoNulls, columnNullable, columnNullableUnknown, functionColumnIn, functionColumnInOut, functionColumnOut, functionColumnResult, functionColumnUnknown, functionNoNulls, functionNoTable, functionNullable, functionNullableUnknown, functionResultUnknown, functionReturn, functionReturnsTable, importedKeyCascade, importedKeyInitiallyDeferred, importedKeyInitiallyImmediate, importedKeyNoAction, importedKeyNotDeferrable, importedKeyRestrict, importedKeySetDefault, importedKeySetNull, procedureColumnIn, procedureColumnInOut, procedureColumnOut, procedureColumnResult, procedureColumnReturn, procedureColumnUnknown, procedureNoNulls, procedureNoResult, procedureNullable, procedureNullableUnknown, procedureResultUnknown, procedureReturnsResult, sqlStateSQL, sqlStateSQL99, sqlStateXOpen, tableIndexClustered, tableIndexHashed, tableIndexOther, tableIndexStatistic, typeNoNulls, typeNullable, typeNullableUnknown, typePredBasic, typePredChar, typePredNone, typeSearchable, versionColumnNotPseudo, versionColumnPseudo, versionColumnUnknown
-
Method Summary
Modifier and TypeMethodDescriptionboolean
Retrieves whether the current user can call all the procedures returned by the methodgetProcedures
.boolean
Retrieves whether the current user can use all the tables returned by the methodgetTables
in aSELECT
statement.boolean
Retrieves whether aSQLException
while autoCommit istrue
indicates that all open ResultSets are closed, even ones that are holdable.boolean
Retrieves whether a data definition statement within a transaction forces the transaction to commit.boolean
Retrieves whether this database ignores a data definition statement within a transaction.boolean
deletesAreDetected
(int type) Retrieves whether or not a visible row delete can be detected by calling the methodResultSet.rowDeleted
.boolean
Retrieves whether the return value for the methodgetMaxRowSize
includes the SQL data typesLONGVARCHAR
andLONGVARBINARY
.boolean
Retrieves whether a generated key will always be returned if the column name(s) or index(es) specified for the auto generated key column(s) are valid and the statement succeeds.getAttributes
(String catalog, String schemaPattern, String typeNamePattern, String attributeNamePattern) Retrieves a description of the given attribute of the given type for a user-defined type (UDT) that is available in the given schema and catalog.getBestRowIdentifier
(String catalog, String schema, String table, int scope, boolean nullable) Retrieves a description of a table's optimal set of columns that uniquely identifies a row.Retrieves the catalog names available in this database.Retrieves theString
that this database uses as the separator between a catalog and table name.Retrieves the database vendor's preferred term for "catalog".Retrieves a list of the client info properties that the driver supports.getColumnPrivileges
(String catalog, String schema, String table, String columnNamePattern) Retrieves a description of the access rights for a table's columns.getColumns
(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) Retrieves a description of table columns available in the specified catalog.Retrieves the connection that produced this metadata object.getCrossReference
(String parentCatalog, String parentSchema, String parentTable, String foreignCatalog, String foreignSchema, String foreignTable) (JDBC4 clarification:) Retrieves a description of the foreign key columns in the given foreign key table that reference the primary key or the columns representing a unique constraint of the parent table (could be the same or a different table).Returns the name of the default collation for database.int
Retrieves the major version number of the underlying database.int
Retrieves the minor version number of the underlying database.Retrieves the name of this database product.Retrieves the version number of this database product.int
Retrieves this database's default transaction isolation level.int
Retrieves this JDBC driver's major version number.int
Retrieves this JDBC driver's minor version number.Retrieves the name of this JDBC driver.Retrieves the version number of this JDBC driver as aString
.getExportedKeys
(String catalog, String schema, String table) Retrieves a description of the foreign key columns that reference the given table's primary key columns (the foreign keys exported by a table).Retrieves all the "extra" characters that can be used in unquoted identifier names (those beyond a-z, A-Z, 0-9 and _).getFunctionColumns
(String catalog, String schemaPattern, String functionNamePattern, String columnNamePattern) Retrieves a description of the given catalog's system or user function parameters and return type.getFunctions
(String catalog, String schemaPattern, String functionNamePattern) Retrieves a description of the JDBC 4.1[ system and ]user functions available in the given catalog.Retrieves the string used to quote SQL identifiers.getImportedKeys
(String catalog, String schema, String table) Retrieves a description of the primary key columns that are referenced by the given table's foreign key columns (the primary keys imported by a table).getIndexInfo
(String catalog, String schema, String table, boolean unique, boolean approximate) Retrieves a description of the given table's indices and statistics.int
Retrieves the major JDBC version number for this driver.int
Retrieves the minor JDBC version number for this driver.int
Retrieves the maximum number of hex characters this database allows in an inline binary literal.int
Retrieves the maximum number of characters that this database allows in a catalog name.int
Retrieves the maximum number of characters this database allows for a character literal.int
Retrieves the maximum number of characters this database allows for a column name.int
Retrieves the maximum number of columns this database allows in aGROUP BY
clause.int
Retrieves the maximum number of columns this database allows in an index.int
Retrieves the maximum number of columns this database allows in anORDER BY
clause.int
Retrieves the maximum number of columns this database allows in aSELECT
list.int
Retrieves the maximum number of columns this database allows in a table.int
Retrieves the maximum number of concurrent connections to this database that are possible.int
Retrieves the maximum number of characters that this database allows in a cursor name.int
Retrieves the maximum number of bytes this database allows for an index, including all of the parts of the index.long
Retrieves the maximum number of bytes this database allows for the logical size for aLOB
.int
Retrieves the maximum number of characters that this database allows in a procedure name.int
Retrieves the maximum number of bytes this database allows in a single row.int
Retrieves the maximum number of characters that this database allows in a schema name.int
Retrieves the maximum number of characters this database allows in an SQL statement.int
Retrieves the maximum number of active statements to this database that can be open at the same time.int
Retrieves the maximum number of characters this database allows in a table name.int
Retrieves the maximum number of tables this database allows in aSELECT
statement.int
Retrieves the maximum number of characters this database allows in a user name.Retrieves a comma-separated list of math functions available with this database.getPrimaryKeys
(String catalog, String schema, String table) Retrieves a description of the given table's primary key columns.getProcedureColumns
(String catalog, String schemaPattern, String procedureNamePattern, String columnNamePattern) Retrieves a description of the given catalog's stored procedure parameter and result columns.getProcedures
(String catalog, String schemaPattern, String procedureNamePattern) Retrieves a description of the stored procedures available in the given catalog.Retrieves the database vendor's preferred term for "procedure".getPseudoColumns
(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) Retrieves a description of the pseudo or hidden columns available in a given table within the specified catalog and schema.int
(JDBC4 clarification:) Retrieves this database's default holdability forResultSet
objects.Indicates whether or not this data source supports the SQLROWID
type, and if so the lifetime for which aRowId
object remains valid.Retrieves the schema names available in this database.getSchemas
(String catalog, String schemaPattern) Retrieves the schema names available in this database.Retrieves the database vendor's preferred term for "schema".Retrieves the string that can be used to escape wildcard characters.Retrieves a comma-separated list of all of this database's SQL keywords that are NOT also SQL:2003 keywords.int
(JDBC4 modified:) Indicates whether the SQLSTATE returned bySQLException.getSQLState
is X/Open (now known as Open Group) SQL CLI or SQL:2003.Retrieves a comma-separated list of string functions available with this database.getSuperTables
(String catalog, String schemaPattern, String tableNamePattern) Retrieves a description of the table hierarchies defined in a particular schema in this database.getSuperTypes
(String catalog, String schemaPattern, String typeNamePattern) Retrieves a description of the user-defined type (UDT) hierarchies defined in a particular schema in this database.Retrieves a comma-separated list of system functions available with this database.getTablePrivileges
(String catalog, String schemaPattern, String tableNamePattern) Retrieves a description of the access rights for each table available in a catalog.Retrieves a description of the tables available in the given catalog.Retrieves the table types available in this database.Retrieves a comma-separated list of the time and date functions available with this database.Retrieves a description of all the (JDBC4 clarification:) data types supported by this database.Retrieves a description of the user-defined types (UDTs) defined in a particular schema.getURL()
Retrieves the URL for this DBMS.Retrieves the user name as known to this database.getVersionColumns
(String catalog, String schema, String table) Retrieves a description of a table's columns that are automatically updated when any value in a row is updated.boolean
insertsAreDetected
(int type) Retrieves whether or not a visible row insert can be detected by calling the methodResultSet.rowInserted
.boolean
Retrieves whether a catalog appears at the start of a fully qualified table name.boolean
Retrieves whether this database is in read-only mode.boolean
isWrapperFor
(Class<?> iface) Returns true if this either implements the interface argument or is directly or indirectly a wrapper for an object that does.boolean
Indicates whether updates made to a LOB are made on a copy or directly to the LOB.boolean
Retrieves whether this database supports concatenations betweenNULL
and non-NULL
values beingNULL
.boolean
Retrieves whetherNULL
values are sorted at the end regardless of sort order.boolean
Retrieves whetherNULL
values are sorted at the start regardless of sort order.boolean
Retrieves whetherNULL
values are sorted high.boolean
Retrieves whetherNULL
values are sorted low.boolean
othersDeletesAreVisible
(int type) Retrieves whether deletes made by others are visible.boolean
othersInsertsAreVisible
(int type) Retrieves whether inserts made by others are visible.boolean
othersUpdatesAreVisible
(int type) Retrieves whether updates made by others are visible.boolean
ownDeletesAreVisible
(int type) Retrieves whether a result set's own deletes are visible.boolean
ownInsertsAreVisible
(int type) Retrieves whether a result set's own inserts are visible.boolean
ownUpdatesAreVisible
(int type) Retrieves whether for the given type ofResultSet
object, the result set's own updates are visible.boolean
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in lower case.boolean
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in lower case.boolean
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in mixed case.boolean
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in mixed case.boolean
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in upper case.boolean
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in upper case.boolean
Retrieves whether this database supportsALTER TABLE
with add column.boolean
Retrieves whether this database supportsALTER TABLE
with drop column.boolean
Retrieves whether this database supports the ANSI92 entry level SQL grammar.boolean
Retrieves whether this database supports the ANSI92 full SQL grammar supported.boolean
Retrieves whether this database supports the ANSI92 intermediate SQL grammar supported.boolean
Retrieves whether this database supports batch updates.boolean
Retrieves whether a catalog name can be used in a data manipulation statement.boolean
Retrieves whether a catalog name can be used in an index definition statement.boolean
Retrieves whether a catalog name can be used in a privilege definition statement.boolean
Retrieves whether a catalog name can be used in a procedure call statement.boolean
Retrieves whether a catalog name can be used in a table definition statement.boolean
Retrieves whether this database supports column aliasing.boolean
(JDBC4 clarification:) Retrieves whether this database supports the JDBC scalar functionCONVERT
for the conversion of one JDBC type to another.boolean
supportsConvert
(int fromType, int toType) (JDBC4 clarification:) Retrieves whether this database supports the JDBC scalar functionCONVERT
for conversions between the JDBC types fromType and toType.boolean
Retrieves whether this database supports the ODBC Core SQL grammar.boolean
Retrieves whether this database supports correlated subqueries.boolean
Retrieves whether this database supports both data definition and data manipulation statements within a transaction.boolean
Retrieves whether this database supports only data manipulation statements within a transaction.boolean
Retrieves whether, when table correlation names are supported, they are restricted to being different from the names of the tables.boolean
Retrieves whether this database supports expressions inORDER BY
lists.boolean
Retrieves whether this database supports the ODBC Extended SQL grammar.boolean
Retrieves whether this database supports full nested outer joins.boolean
Retrieves whether auto-generated keys can be retrieved after a statement has been executedboolean
Retrieves whether this database supports some form ofGROUP BY
clause.boolean
Retrieves whether this database supports using columns not included in theSELECT
statement in aGROUP BY
clause provided that all of the columns in theSELECT
statement are included in theGROUP BY
clause.boolean
Retrieves whether this database supports using a column that is not in theSELECT
statement in aGROUP BY
clause.boolean
Retrieves whether this database supports the SQL Integrity Enhancement Facility.boolean
Retrieves whether this database supports specifying aLIKE
escape clause.boolean
Retrieves whether this database provides limited support for outer joins.boolean
Retrieves whether this database supports the ODBC Minimum SQL grammar.boolean
Retrieves whether this database treats mixed case unquoted SQL identifiers as case sensitive and as a result stores them in mixed case.boolean
Retrieves whether this database treats mixed case quoted SQL identifiers as case sensitive and as a result stores them in mixed case.boolean
Retrieves whether it is possible to have multipleResultSet
objects returned from aCallableStatement
object simultaneously.boolean
Retrieves whether this database supports getting multipleResultSet
objects from a single call to the methodexecute
.boolean
Retrieves whether this database allows having multiple transactions open at once (on different connections).boolean
Retrieves whether this database supports named parameters to callable statements.boolean
Retrieves whether columns in this database may be defined as non-nullable.boolean
Retrieves whether this database supports keeping cursors open across commits.boolean
Retrieves whether this database supports keeping cursors open across rollbacks.boolean
Retrieves whether this database supports keeping statements open across commits.boolean
Retrieves whether this database supports keeping statements open across rollbacks.boolean
Retrieves whether this database supports using a column that is not in theSELECT
statement in anORDER BY
clause.boolean
Retrieves whether this database supports some form of outer join.boolean
Retrieves whether this database supports positionedDELETE
statements.boolean
Retrieves whether this database supports positionedUPDATE
statements.boolean
Retrieves whether this database supports REF CURSOR.boolean
supportsResultSetConcurrency
(int type, int concurrency) Retrieves whether this database supports the given concurrency type in combination with the given result set type.boolean
supportsResultSetHoldability
(int holdability) Retrieves whether this database supports the given result set holdability.boolean
supportsResultSetType
(int type) Retrieves whether this database supports the given result set type.boolean
Retrieves whether this database supports savepoints.boolean
Retrieves whether a schema name can be used in a data manipulation statement.boolean
Retrieves whether a schema name can be used in an index definition statement.boolean
Retrieves whether a schema name can be used in a privilege definition statement.boolean
Retrieves whether a schema name can be used in a procedure call statement.boolean
Retrieves whether a schema name can be used in a table definition statement.boolean
Retrieves whether this database supportsSELECT FOR UPDATE
statements.boolean
Retrieves whether this database supports statement pooling.boolean
Retrieves whether this database supports invoking user-defined or vendor functions using the stored procedure escape syntax.boolean
Retrieves whether this database supports stored procedure calls that use the stored procedure escape syntax.boolean
Retrieves whether this database supports subqueries in comparison expressions.boolean
Retrieves whether this database supports subqueries inEXISTS
expressions.boolean
(JDBC4 correction:) Retrieves whether this database supports subqueries inIN
expressions.boolean
Retrieves whether this database supports subqueries in quantified expressions.boolean
Retrieves whether this database supports table correlation names.boolean
supportsTransactionIsolationLevel
(int level) Retrieves whether this database supports the given transaction isolation level.boolean
Retrieves whether this database supports transactions.boolean
Retrieves whether this database supports SQLUNION
.boolean
Retrieves whether this database supports SQLUNION ALL
.<T> T
Returns an object that implements the given interface to allow access to non-standard methods, or standard methods not exposed by the proxy.boolean
updatesAreDetected
(int type) Retrieves whether or not a visible row update can be detected by calling the methodResultSet.rowUpdated
.boolean
Retrieves whether this database uses a file for each table.boolean
Retrieves whether this database stores tables in a local file.Methods inherited from class java.lang.Object
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
Methods inherited from interface java.sql.DatabaseMetaData
supportsSharding
-
Field Details
-
JDBC_MAJOR
public static final int JDBC_MAJOR- See Also:
-
JDBC_MINOR
public static final int JDBC_MINOR- See Also:
-
THIS_VERSION
- See Also:
-
-
Method Details
-
allProceduresAreCallable
Retrieves whether the current user can call all the procedures returned by the methodgetProcedures
.HSQLDB-Specific Information:
This method always returns
true because the listed procedures are those which the current user can use
.- Specified by:
allProceduresAreCallable
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
allTablesAreSelectable
Retrieves whether the current user can use all the tables returned by the methodgetTables
in aSELECT
statement.HSQLDB-Specific Information:
HSQLDB always reports
true
.The
getTables
call returns the list of tables to which the invoking user has some access rights.- Specified by:
allTablesAreSelectable
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getURL
Retrieves the URL for this DBMS.- Specified by:
getURL
in interfaceDatabaseMetaData
- Returns:
- the URL for this DBMS or
null
if it cannot be generated - Throws:
SQLException
- if a database access error occurs
-
getUserName
Retrieves the user name as known to this database.- Specified by:
getUserName
in interfaceDatabaseMetaData
- Returns:
- the database user name
- Throws:
SQLException
- if a database access error occurs
-
isReadOnly
Retrieves whether this database is in read-only mode.HSQLDB-Specific Information:
This makes an SQL call to the isReadOnlyDatabase function which provides correct determination of the read-only status for both local and remote database instances.
- Specified by:
isReadOnly
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
nullsAreSortedHigh
Retrieves whetherNULL
values are sorted high. Sorted high means thatNULL
values sort higher than any other value in a domain. In an ascending order, if this method returnstrue
,NULL
values will appear at the end. By contrast, the methodnullsAreSortedAtEnd
indicates whetherNULL
values are sorted at the end regardless of sort order.HSQLDB-Specific Information:
By default HSQLDB sorts null at start and this method returns
false
. But a different value is returned ifsql.nulls_first
orsql.nulls_lasst
properties have a non-default value.- Specified by:
nullsAreSortedHigh
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
nullsAreSortedLow
Retrieves whetherNULL
values are sorted low. Sorted low means thatNULL
values sort lower than any other value in a domain. In an ascending order, if this method returnstrue
,NULL
values will appear at the beginning. By contrast, the methodnullsAreSortedAtStart
indicates whetherNULL
values are sorted at the beginning regardless of sort order.HSQLDB-Specific Information:
By default HSQLDB sorts null at start and this method returns
false
. But a different value is returned ifsql.nulls_first
orsql.nulls_lasst
properties have a non-default value.- Specified by:
nullsAreSortedLow
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
nullsAreSortedAtStart
Retrieves whetherNULL
values are sorted at the start regardless of sort order.HSQLDB-Specific Information:
By default HSQLDB sorts null at start and this method returns
true
. But a different value is returned ifsql.nulls_first
orsql.nulls_last
properties have a non-default value.Use NULLS LAST in the ORDER BY clause to sort null at the end.
- Specified by:
nullsAreSortedAtStart
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
nullsAreSortedAtEnd
Retrieves whetherNULL
values are sorted at the end regardless of sort order.HSQLDB-Specific Information:
By default HSQLDB sorts null at start and this method returns
false
. But a different value is returned ifsql.nulls_first
orsql.nulls_last
properties have a non-default value.Use NULLS LAST in the ORDER BY clause to sort null at the end.
- Specified by:
nullsAreSortedAtEnd
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getDatabaseProductName
Retrieves the name of this database product.HSQLDB-Specific Information:
Returns the name of the HSQLDB engine.
- Specified by:
getDatabaseProductName
in interfaceDatabaseMetaData
- Returns:
- database product name
- Throws:
SQLException
- if a database access error occurs
-
getDatabaseProductVersion
Retrieves the version number of this database product.HSQLDB-Specific Information:
Returns the full version string.
- Specified by:
getDatabaseProductVersion
in interfaceDatabaseMetaData
- Returns:
- database version number
- Throws:
SQLException
- if a database access error occurs
-
getDriverName
Retrieves the name of this JDBC driver.- Specified by:
getDriverName
in interfaceDatabaseMetaData
- Returns:
- JDBC driver name
- Throws:
SQLException
- if a database access error occurs
-
getDriverVersion
Retrieves the version number of this JDBC driver as aString
.- Specified by:
getDriverVersion
in interfaceDatabaseMetaData
- Returns:
- JDBC driver version
- Throws:
SQLException
- if a database access error occurs
-
getDriverMajorVersion
public int getDriverMajorVersion()Retrieves this JDBC driver's major version number.- Specified by:
getDriverMajorVersion
in interfaceDatabaseMetaData
- Returns:
- JDBC driver major version
-
getDriverMinorVersion
public int getDriverMinorVersion()Retrieves this JDBC driver's minor version number.- Specified by:
getDriverMinorVersion
in interfaceDatabaseMetaData
- Returns:
- JDBC driver minor version number
-
usesLocalFiles
Retrieves whether this database stores tables in a local file.HSQLDB-Specific Information:
From HSQLDB 1.7.2 it is assumed that this refers to data being stored by the JDBC client. This method always returns false.
- Specified by:
usesLocalFiles
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
usesLocalFilePerTable
Retrieves whether this database uses a file for each table.HSQLDB-Specific Information:
HSQLDB does not use a file for each table. This method always returns
false
.- Specified by:
usesLocalFilePerTable
in interfaceDatabaseMetaData
- Returns:
true
if this database uses a local file for each table;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsMixedCaseIdentifiers
Retrieves whether this database treats mixed case unquoted SQL identifiers as case sensitive and as a result stores them in mixed case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
supportsMixedCaseIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesUpperCaseIdentifiers
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in upper case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
true
.- Specified by:
storesUpperCaseIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesLowerCaseIdentifiers
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in lower case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
storesLowerCaseIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesMixedCaseIdentifiers
Retrieves whether this database treats mixed case unquoted SQL identifiers as case insensitive and stores them in mixed case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
storesMixedCaseIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsMixedCaseQuotedIdentifiers
Retrieves whether this database treats mixed case quoted SQL identifiers as case sensitive and as a result stores them in mixed case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
true
.- Specified by:
supportsMixedCaseQuotedIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesUpperCaseQuotedIdentifiers
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in upper case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
storesUpperCaseQuotedIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesLowerCaseQuotedIdentifiers
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in lower case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
storesLowerCaseQuotedIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
storesMixedCaseQuotedIdentifiers
Retrieves whether this database treats mixed case quoted SQL identifiers as case insensitive and stores them in mixed case.HSQLDB-Specific Information:
HSQLDB treats unquoted identifiers as case insensitive and stores them in upper case. It treats quoted identifiers as case sensitive and stores them verbatim; this method always returns
false
.- Specified by:
storesMixedCaseQuotedIdentifiers
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getIdentifierQuoteString
Retrieves the string used to quote SQL identifiers. This method returns a space " " if identifier quoting is not supported.HSQLDB-Specific Information:
HSQLDB uses the standard SQL identifier quote character (the double quote character); this method always returns ".
- Specified by:
getIdentifierQuoteString
in interfaceDatabaseMetaData
- Returns:
- the quoting string or a space if quoting is not supported
- Throws:
SQLException
- if a database access error occurs
-
getSQLKeywords
Retrieves a comma-separated list of all of this database's SQL keywords that are NOT also SQL:2003 keywords. (JDBC4 modified to SQL:2003)HSQLDB-Specific Information:
The list is empty. However, HSQLDB also supports SQL:2008 keywords and disallows them for database object names without double quoting.
- Specified by:
getSQLKeywords
in interfaceDatabaseMetaData
- Returns:
- the list of this database's keywords that are not also SQL:2003 keywords (JDBC4 modified to SQL:2003)
- Throws:
SQLException
- if a database access error occurs
-
getNumericFunctions
Retrieves a comma-separated list of math functions available with this database. These are the Open /Open CLI math function names used in the JDBC function escape clause.- Specified by:
getNumericFunctions
in interfaceDatabaseMetaData
- Returns:
- the list of math functions supported by this database
- Throws:
SQLException
- if a database access error occurs
-
getStringFunctions
Retrieves a comma-separated list of string functions available with this database. These are the Open Group CLI string function names used in the JDBC function escape clause.- Specified by:
getStringFunctions
in interfaceDatabaseMetaData
- Returns:
- the list of string functions supported by this database
- Throws:
SQLException
- if a database access error occurs
-
getSystemFunctions
Retrieves a comma-separated list of system functions available with this database. These are the Open Group CLI system function names used in the JDBC function escape clause.- Specified by:
getSystemFunctions
in interfaceDatabaseMetaData
- Returns:
- a list of system functions supported by this database
- Throws:
SQLException
- if a database access error occurs
-
getTimeDateFunctions
Retrieves a comma-separated list of the time and date functions available with this database.- Specified by:
getTimeDateFunctions
in interfaceDatabaseMetaData
- Returns:
- the list of time and date functions supported by this database
- Throws:
SQLException
- if a database access error occurs
-
getSearchStringEscape
Retrieves the string that can be used to escape wildcard characters. This is the string that can be used to escape '_' or '%' in the catalog search parameters that are a pattern (and therefore use one of the wildcard characters).The '_' character represents any single character; the '%' character represents any sequence of zero or more characters.
HSQLDB-Specific Information:
HSQLDB uses the "\" character to escape wildcard characters.
- Specified by:
getSearchStringEscape
in interfaceDatabaseMetaData
- Returns:
- the string used to escape wildcard characters
- Throws:
SQLException
- if a database access error occurs
-
getExtraNameCharacters
Retrieves all the "extra" characters that can be used in unquoted identifier names (those beyond a-z, A-Z, 0-9 and _).HSQLDB-Specific Information:
By default HSQLDB does not support using any "extra" characters in unquoted identifier names; this method always returns the empty String.
- Specified by:
getExtraNameCharacters
in interfaceDatabaseMetaData
- Returns:
- the string containing the extra characters
- Throws:
SQLException
- if a database access error occurs
-
supportsAlterTableWithAddColumn
Retrieves whether this database supportsALTER TABLE
with add column.HSQLDB-Specific Information:
HSQLDB supports this type of
ALTER TABLE
statement; this method always returnstrue
.- Specified by:
supportsAlterTableWithAddColumn
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsAlterTableWithDropColumn
Retrieves whether this database supportsALTER TABLE
with drop column.HSQLDB-Specific Information:
HSQLDB supports this type of
ALTER TABLE
statement; this method always returnstrue
.- Specified by:
supportsAlterTableWithDropColumn
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsColumnAliasing
Retrieves whether this database supports column aliasing.If so, the SQL AS clause can be used to provide names for computed columns or to provide alias names for columns as required.
HSQLDB-Specific Information:
HSQLDB supports column aliasing; this method always returns
true
.- Specified by:
supportsColumnAliasing
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
nullPlusNonNullIsNull
Retrieves whether this database supports concatenations betweenNULL
and non-NULL
values beingNULL
.HSQLDB-Specific Information:
By default HSQLDB returns NULL when NULL and non-NULL values are concatenated. By default this method returns
false
. But a different value is returned if thesql.concat_nulls
property has a non-default value.- Specified by:
nullPlusNonNullIsNull
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsConvert
(JDBC4 clarification:) Retrieves whether this database supports the JDBC scalar functionCONVERT
for the conversion of one JDBC type to another. The JDBC types are the generic SQL data types defined injava.sql.Types
.HSQLDB-Specific Information:
HSQLDB supports conversions; this method always returns
true
.- Specified by:
supportsConvert
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsConvert
(JDBC4 clarification:) Retrieves whether this database supports the JDBC scalar functionCONVERT
for conversions between the JDBC types fromType and toType. The JDBC types are the generic SQL data types defined injava.sql.Types
.HSQLDB-Specific Information:
HSQLDB 2.0 supports conversion according to SQL standards. In addition, it supports conversion between values of BOOLEAN and BIT types.
- Specified by:
supportsConvert
in interfaceDatabaseMetaData
- Parameters:
fromType
- the type to convert from; one of the type codes from the classjava.sql.Types
toType
- the type to convert to; one of the type codes from the classjava.sql.Types
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- See Also:
-
supportsTableCorrelationNames
Retrieves whether this database supports table correlation names.HSQLDB-Specific Information:
HSQLDB supports table correlation names; this method always returns
true
.- Specified by:
supportsTableCorrelationNames
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsDifferentTableCorrelationNames
Retrieves whether, when table correlation names are supported, they are restricted to being different from the names of the tables.HSQLDB-Specific Information:
HSQLDB does not require that table correlation names are different from the names of the tables; this method always returns
false
.- Specified by:
supportsDifferentTableCorrelationNames
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsExpressionsInOrderBy
Retrieves whether this database supports expressions inORDER BY
lists.HSQLDB-Specific Information:
HSQLDB supports expressions in
ORDER BY
lists; this method always returnstrue
.- Specified by:
supportsExpressionsInOrderBy
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsGroupBy
Retrieves whether this database supports some form ofGROUP BY
clause.HSQLDB-Specific Information:
HSQLDB supports using the
GROUP BY
clause; this method always returnstrue
.- Specified by:
supportsGroupBy
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsGroupByBeyondSelect
Retrieves whether this database supports using columns not included in theSELECT
statement in aGROUP BY
clause provided that all of the columns in theSELECT
statement are included in theGROUP BY
clause.HSQLDB-Specific Information:
HSQLDB supports using columns not included in the
SELECT
statement in aGROUP BY
clause provided that all of the columns in theSELECT
statement are included in theGROUP BY
clause; this method always returnstrue
.- Specified by:
supportsGroupByBeyondSelect
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsLikeEscapeClause
Retrieves whether this database supports specifying aLIKE
escape clause.HSQLDB-Specific Information:
HSQLDB supports specifying a
LIKE
escape clause; this method always returnstrue
.- Specified by:
supportsLikeEscapeClause
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsMultipleResultSets
Retrieves whether this database supports getting multipleResultSet
objects from a single call to the methodexecute
.HSQLDB-Specific Information:
HSQLDB 2.0 supports getting multiple
ResultSet
objects from a single call to the methodexecute
of the CallableStatement interface; this method returnstrue
.- Specified by:
supportsMultipleResultSets
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsMultipleTransactions
Retrieves whether this database allows having multiple transactions open at once (on different connections).HSQLDB-Specific Information:
HSQLDB allows having multiple transactions open at once (on different connections); this method always returns
true
.- Specified by:
supportsMultipleTransactions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsNonNullableColumns
Retrieves whether columns in this database may be defined as non-nullable.HSQLDB-Specific Information:
HSQLDB supports the specification of non-nullable columns; this method always returns
true
.- Specified by:
supportsNonNullableColumns
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsMinimumSQLGrammar
Retrieves whether this database supports the ODBC Minimum SQL grammar.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ODBC Minimum SQL grammar; this method always returns
true
.- Specified by:
supportsMinimumSQLGrammar
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCoreSQLGrammar
Retrieves whether this database supports the ODBC Core SQL grammar.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ODBC Core SQL grammar; this method always returns
true
.- Specified by:
supportsCoreSQLGrammar
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsExtendedSQLGrammar
Retrieves whether this database supports the ODBC Extended SQL grammar.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ODBC Extended SQL grammar; this method always returns
true
.- Specified by:
supportsExtendedSQLGrammar
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsANSI92EntryLevelSQL
Retrieves whether this database supports the ANSI92 entry level SQL grammar.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ANSI92 entry level SQL grammar; this method always returns
true
.- Specified by:
supportsANSI92EntryLevelSQL
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsANSI92IntermediateSQL
Retrieves whether this database supports the ANSI92 intermediate SQL grammar supported.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ANSI92 intermediate SQL grammar; this method always returns
true
.- Specified by:
supportsANSI92IntermediateSQL
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsANSI92FullSQL
Retrieves whether this database supports the ANSI92 full SQL grammar supported.HSQLDB-Specific Information:
From 2.0, HSQLDB supports the ANSI92 full SQL grammar. The exceptions, such as support for ASSERTION, are not considered grammar issues. This method always returns
true
.- Specified by:
supportsANSI92FullSQL
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsIntegrityEnhancementFacility
Retrieves whether this database supports the SQL Integrity Enhancement Facility.HSQLDB-Specific Information:
This method always returns
true
.- Specified by:
supportsIntegrityEnhancementFacility
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsOuterJoins
Retrieves whether this database supports some form of outer join.HSQLDB-Specific Information:
HSQLDB supports outer joins; this method always returns
true
.- Specified by:
supportsOuterJoins
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsFullOuterJoins
Retrieves whether this database supports full nested outer joins.HSQLDB-Specific Information:
From 2.0, HSQLDB supports full nested outer joins; this method always returns
true
.- Specified by:
supportsFullOuterJoins
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsLimitedOuterJoins
Retrieves whether this database provides limited support for outer joins. (This will betrue
if the methodsupportsFullOuterJoins
returnstrue
).HSQLDB-Specific Information:
HSQLDB supports the LEFT OUTER join syntax; this method always returns
true
.- Specified by:
supportsLimitedOuterJoins
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getSchemaTerm
Retrieves the database vendor's preferred term for "schema".HSQLDB-Specific Information:
Starting with 1.8.0, HSQLDB supports schemas.
- Specified by:
getSchemaTerm
in interfaceDatabaseMetaData
- Returns:
- the vendor term for "schema"
- Throws:
SQLException
- if a database access error occurs
-
getProcedureTerm
Retrieves the database vendor's preferred term for "procedure".HSQLDB-Specific Information:
From 2.0, HSQLDB supports declaration of functions or procedures directly in SQL.
- Specified by:
getProcedureTerm
in interfaceDatabaseMetaData
- Returns:
- the vendor term for "procedure"
- Throws:
SQLException
- if a database access error occurs
-
getCatalogTerm
Retrieves the database vendor's preferred term for "catalog".HSQLDB-Specific Information:
HSQLDB uses the standard name CATALOG.
- Specified by:
getCatalogTerm
in interfaceDatabaseMetaData
- Returns:
- the vendor term for "catalog"
- Throws:
SQLException
- if a database access error occurs
-
isCatalogAtStart
Retrieves whether a catalog appears at the start of a fully qualified table name. If not, the catalog appears at the end.HSQLDB-Specific Information:
When allowed, a catalog appears at the start of a fully qualified table name; this method always returns
true
.- Specified by:
isCatalogAtStart
in interfaceDatabaseMetaData
- Returns:
true
if the catalog name appears at the beginning of a fully qualified table name;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getCatalogSeparator
Retrieves theString
that this database uses as the separator between a catalog and table name.HSQLDB-Specific Information:
When used, a catalog name is separated with period; this method always returns a period
- Specified by:
getCatalogSeparator
in interfaceDatabaseMetaData
- Returns:
- the separator string
- Throws:
SQLException
- if a database access error occurs
-
supportsSchemasInDataManipulation
Retrieves whether a schema name can be used in a data manipulation statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports schemas where allowed by the standard; this method always returns
true
.- Specified by:
supportsSchemasInDataManipulation
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSchemasInProcedureCalls
Retrieves whether a schema name can be used in a procedure call statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports schemas where allowed by the standard; this method always returns
true
.- Specified by:
supportsSchemasInProcedureCalls
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSchemasInTableDefinitions
Retrieves whether a schema name can be used in a table definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports schemas where allowed by the standard; this method always returns
true
.- Specified by:
supportsSchemasInTableDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSchemasInIndexDefinitions
Retrieves whether a schema name can be used in an index definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports schemas where allowed by the standard; this method always returns
true
.- Specified by:
supportsSchemasInIndexDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSchemasInPrivilegeDefinitions
Retrieves whether a schema name can be used in a privilege definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports schemas where allowed by the standard; this method always returns
true
.- Specified by:
supportsSchemasInPrivilegeDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCatalogsInDataManipulation
Retrieves whether a catalog name can be used in a data manipulation statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports catalog names where allowed by the standard; this method always returns
true
.- Specified by:
supportsCatalogsInDataManipulation
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCatalogsInProcedureCalls
Retrieves whether a catalog name can be used in a procedure call statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports catalog names where allowed by the standard; this method always returns
true
.- Specified by:
supportsCatalogsInProcedureCalls
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCatalogsInTableDefinitions
Retrieves whether a catalog name can be used in a table definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports catalog names where allowed by the standard; this method always returns
true
.- Specified by:
supportsCatalogsInTableDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCatalogsInIndexDefinitions
Retrieves whether a catalog name can be used in an index definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports catalog names where allowed by the standard; this method always returns
true
.- Specified by:
supportsCatalogsInIndexDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsCatalogsInPrivilegeDefinitions
Retrieves whether a catalog name can be used in a privilege definition statement.HSQLDB-Specific Information:
From 2.0, HSQLDB supports catalog names where allowed by the standard; this method always returns
true
.- Specified by:
supportsCatalogsInPrivilegeDefinitions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsPositionedDelete
Retrieves whether this database supports positionedDELETE
statements.HSQLDB-Specific Information:
HSQLDB 2.0 supports updatable result sets; this method always returns
true
.- Specified by:
supportsPositionedDelete
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsPositionedUpdate
Retrieves whether this database supports positionedUPDATE
statements.HSQLDB-Specific Information:
HSQLDB 2.0 supports updatable result sets; this method always returns
true
.- Specified by:
supportsPositionedUpdate
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSelectForUpdate
Retrieves whether this database supportsSELECT FOR UPDATE
statements.HSQLDB-Specific Information:
HSQLDB 2.0 supports updatable result sets; this method always returns
true
.- Specified by:
supportsSelectForUpdate
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsStoredProcedures
Retrieves whether this database supports stored procedure calls that use the stored procedure escape syntax.HSQLDB-Specific Information:
HSQLDB supports calling public static Java methods in the context of SQL Stored Procedures; this method always returns
true
.- Specified by:
supportsStoredProcedures
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- See Also:
-
supportsSubqueriesInComparisons
Retrieves whether this database supports subqueries in comparison expressions.HSQLDB-Specific Information:
HSQLDB has always supported subqueries in comparison expressions; this method always returns
true
.- Specified by:
supportsSubqueriesInComparisons
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSubqueriesInExists
Retrieves whether this database supports subqueries inEXISTS
expressions.HSQLDB-Specific Information:
HSQLDB has always supported subqueries in
EXISTS
expressions; this method always returnstrue
.- Specified by:
supportsSubqueriesInExists
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSubqueriesInIns
(JDBC4 correction:) Retrieves whether this database supports subqueries inIN
expressions.HSQLDB-Specific Information:
HSQLDB has always supported subqueries in
IN
statements; this method always returnstrue
.- Specified by:
supportsSubqueriesInIns
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsSubqueriesInQuantifieds
Retrieves whether this database supports subqueries in quantified expressions.HSQLDB-Specific Information:
HSQLDB has always supported subqueries in quantified expressions; this method always returns
true
.- Specified by:
supportsSubqueriesInQuantifieds
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsUnion
Retrieves whether this database supports SQLUNION
.HSQLDB-Specific Information:
HSQLDB supports SQL
UNION
; this method always returnstrue
.- Specified by:
supportsUnion
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsUnionAll
Retrieves whether this database supports SQLUNION ALL
.HSQLDB-Specific Information:
HSQLDB supports SQL
UNION ALL
; this method always returnstrue
.- Specified by:
supportsUnionAll
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsOpenCursorsAcrossCommit
Retrieves whether this database supports keeping cursors open across commits.HSQLDB-Specific Information:
HSQLDB 2.0 supports keeping cursors open across commits. This method always returns
true
.- Specified by:
supportsOpenCursorsAcrossCommit
in interfaceDatabaseMetaData
- Returns:
true
if cursors always remain open;false
if they might not remain open- Throws:
SQLException
- if a database access error occurs
-
supportsOpenCursorsAcrossRollback
Retrieves whether this database supports keeping cursors open across rollbacks.HSQLDB-Specific Information:
HSQLDB 2.0 closes open cursors at rollback. This method always returns
false
.- Specified by:
supportsOpenCursorsAcrossRollback
in interfaceDatabaseMetaData
- Returns:
true
if cursors always remain open;false
if they might not remain open- Throws:
SQLException
- if a database access error occurs
-
supportsOpenStatementsAcrossCommit
Retrieves whether this database supports keeping statements open across commits.HSQLDB-Specific Information:
HSQLDB supports keeping statements open across commits; this method always returns
true
.- Specified by:
supportsOpenStatementsAcrossCommit
in interfaceDatabaseMetaData
- Returns:
true
if statements always remain open;false
if they might not remain open- Throws:
SQLException
- if a database access error occurs
-
supportsOpenStatementsAcrossRollback
Retrieves whether this database supports keeping statements open across rollbacks.HSQLDB-Specific Information:
HSQLDB supports keeping statements open across rollbacks; this method always returns
true
.- Specified by:
supportsOpenStatementsAcrossRollback
in interfaceDatabaseMetaData
- Returns:
true
if statements always remain open;false
if they might not remain open- Throws:
SQLException
- if a database access error occurs
-
getMaxBinaryLiteralLength
Retrieves the maximum number of hex characters this database allows in an inline binary literal.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxBinaryLiteralLength
in interfaceDatabaseMetaData
- Returns:
- max the maximum length (in hex characters) for a binary literal; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxCharLiteralLength
Retrieves the maximum number of characters this database allows for a character literal.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxCharLiteralLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed for a character literal; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnNameLength
Retrieves the maximum number of characters this database allows for a column name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxColumnNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed for a column name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnsInGroupBy
Retrieves the maximum number of columns this database allows in aGROUP BY
clause.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxColumnsInGroupBy
in interfaceDatabaseMetaData
- Returns:
- the maximum number of columns allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnsInIndex
Retrieves the maximum number of columns this database allows in an index.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxColumnsInIndex
in interfaceDatabaseMetaData
- Returns:
- the maximum number of columns allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnsInOrderBy
Retrieves the maximum number of columns this database allows in anORDER BY
clause.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxColumnsInOrderBy
in interfaceDatabaseMetaData
- Returns:
- the maximum number of columns allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnsInSelect
Retrieves the maximum number of columns this database allows in aSELECT
list.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxColumnsInSelect
in interfaceDatabaseMetaData
- Returns:
- the maximum number of columns allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxColumnsInTable
Retrieves the maximum number of columns this database allows in a table.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxColumnsInTable
in interfaceDatabaseMetaData
- Returns:
- the maximum number of columns allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxConnections
Retrieves the maximum number of concurrent connections to this database that are possible.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxConnections
in interfaceDatabaseMetaData
- Returns:
- the maximum number of active connections possible at one time; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxCursorNameLength
Retrieves the maximum number of characters that this database allows in a cursor name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxCursorNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed in a cursor name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxIndexLength
Retrieves the maximum number of bytes this database allows for an index, including all of the parts of the index.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory and disk availability; this method always returns
0
.- Specified by:
getMaxIndexLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of bytes allowed; this limit includes the composite of all the constituent parts of the index; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxSchemaNameLength
Retrieves the maximum number of characters that this database allows in a schema name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxSchemaNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed in a schema name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxProcedureNameLength
Retrieves the maximum number of characters that this database allows in a procedure name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxProcedureNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed in a procedure name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxCatalogNameLength
Retrieves the maximum number of characters that this database allows in a catalog name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxCatalogNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed in a catalog name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxRowSize
Retrieves the maximum number of bytes this database allows in a single row.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory and disk availability; this method always returns
0
.- Specified by:
getMaxRowSize
in interfaceDatabaseMetaData
- Returns:
- the maximum number of bytes allowed for a row; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
doesMaxRowSizeIncludeBlobs
Retrieves whether the return value for the methodgetMaxRowSize
includes the SQL data typesLONGVARCHAR
andLONGVARBINARY
.HSQLDB-Specific Information:
Including 2.0,
getMaxRowSize()
always returns 0, indicating that the maximum row size is unknown or has no limit. This applies to the above types as well; this method always returnstrue
.- Specified by:
doesMaxRowSizeIncludeBlobs
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getMaxStatementLength
Retrieves the maximum number of characters this database allows in an SQL statement.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxStatementLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed for an SQL statement; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxStatements
Retrieves the maximum number of active statements to this database that can be open at the same time.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxStatements
in interfaceDatabaseMetaData
- Returns:
- the maximum number of statements that can be open at one time; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxTableNameLength
Retrieves the maximum number of characters this database allows in a table name.HSQLDB-Specific Information:
Up to and including 1.8.0.x, HSQLDB did not impose a "known" limit. Th hard limit was the maximum length of a java.lang.String (java.lang.Integer.MAX_VALUE); this method always returned
0
. Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.- Specified by:
getMaxTableNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed for a table name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getMaxTablesInSelect
Retrieves the maximum number of tables this database allows in aSELECT
statement.HSQLDB-Specific Information:
HSQLDB does not impose a "known" limit. The limit is subject to memory availability; this method always returns
0
.- Specified by:
getMaxTablesInSelect
in interfaceDatabaseMetaData
- Returns:
- the maximum number of tables allowed in a
SELECT
statement; a result of zero means that there is no limit or the limit is not known - Throws:
SQLException
- if a database access error occurs
-
getMaxUserNameLength
Retrieves the maximum number of characters this database allows in a user name.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB implements the SQL standard, which is 128 for all names.
- Specified by:
getMaxUserNameLength
in interfaceDatabaseMetaData
- Returns:
- the maximum number of characters allowed for a user name; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs
-
getDefaultTransactionIsolation
Retrieves this database's default transaction isolation level. The possible values are defined injava.sql.Connection
.HSQLDB-Specific Information:
Default isolation mode in version 2.0 is TRANSACTION_READ_COMMITTED.- Specified by:
getDefaultTransactionIsolation
in interfaceDatabaseMetaData
- Returns:
- the default isolation level
- Throws:
SQLException
- if a database access error occurs- See Also:
-
supportsTransactions
Retrieves whether this database supports transactions. If not, invoking the methodcommit
is a noop, and the isolation level isTRANSACTION_NONE
.HSQLDB-Specific Information:
HSQLDB supports transactions; this method always returns
true
.- Specified by:
supportsTransactions
in interfaceDatabaseMetaData
- Returns:
true
if transactions are supported;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsTransactionIsolationLevel
Retrieves whether this database supports the given transaction isolation level.HSQLDB-Specific Information:
HSQLDB supports all levels.- Specified by:
supportsTransactionIsolationLevel
in interfaceDatabaseMetaData
- Parameters:
level
- one of the transaction isolation levels defined injava.sql.Connection
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- See Also:
-
supportsDataDefinitionAndDataManipulationTransactions
Retrieves whether this database supports both data definition and data manipulation statements within a transaction.HSQLDB-Specific Information:
HSQLDB does not support a mix of both data definition and data manipulation statements within a transaction. DDL commits the current transaction before proceeding; this method always returns
false
.- Specified by:
supportsDataDefinitionAndDataManipulationTransactions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
supportsDataManipulationTransactionsOnly
Retrieves whether this database supports only data manipulation statements within a transaction.HSQLDB-Specific Information:
HSQLDB supports only data manipulation statements within a transaction. DDL commits the current transaction before proceeding, while DML does not; this method always returns
true
.- Specified by:
supportsDataManipulationTransactionsOnly
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
dataDefinitionCausesTransactionCommit
Retrieves whether a data definition statement within a transaction forces the transaction to commit.HSQLDB-Specific Information:
Including 2.0, a data definition statement within a transaction forces the transaction to commit; this method always returns
true
.- Specified by:
dataDefinitionCausesTransactionCommit
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
dataDefinitionIgnoredInTransactions
Retrieves whether this database ignores a data definition statement within a transaction.HSQLDB-Specific Information:
Including 2.0, a data definition statement is not ignored within a transaction. Rather, a data definition statement within a transaction forces the transaction to commit; this method always returns
false
.- Specified by:
dataDefinitionIgnoredInTransactions
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs
-
getProcedures
public ResultSet getProcedures(String catalog, String schemaPattern, String procedureNamePattern) throws SQLException Retrieves a description of the stored procedures available in the given catalog.Only procedure descriptions matching the schema and procedure name criteria are returned. They are ordered by JDBC 4.1[
PROCEDURE_CAT
,]PROCEDURE_SCHEM
,PROCEDURE_NAME
and (new to JDBC4)[SPECIFIC_ NAME
].Each procedure description has the the following columns:
- PROCEDURE_CAT String
=>
procedure catalog (may benull
) - PROCEDURE_SCHEM String
=>
procedure schema (may benull
) - PROCEDURE_NAME String
=>
procedure name - reserved for future use (HSQLDB-specific: NUM_INPUT_PARAMS)
- reserved for future use (HSQLDB-specific: NUM_OUTPUT_PARAMS)
- reserved for future use (HSQLDB-specific: NUM_RESULT_SETS)
- REMARKS String
=>
explanatory comment on the procedure - PROCEDURE_TYPE short
=>
kind of procedure:- procedureResultUnknown - (JDBC4 clarification:) Cannot determine if a return value will be returned
- procedureNoResult - (JDBC4 clarification:) Does not return a return value
- procedureReturnsResult - (JDBC4 clarification:) Returns a return value
- SPECIFIC_NAME String
=>
(JDBC4 new:) The name which uniquely identifies this procedure within its schema.
A user may not have permissions to execute any of the procedures that are returned by
getProcedures
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
In version 1.9, the rows returned by this method are based on rows in the INFORMATION_SCHEMA.ROUTINES table.
- Specified by:
getProcedures
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchprocedureNamePattern
- a procedure name pattern; must match the procedure name as it is stored in the database- Returns:
ResultSet
- each row is a procedure description- Throws:
SQLException
- if a database access error occurs- See Also:
- PROCEDURE_CAT String
-
getProcedureColumns
public ResultSet getProcedureColumns(String catalog, String schemaPattern, String procedureNamePattern, String columnNamePattern) throws SQLException Retrieves a description of the given catalog's stored procedure parameter and result columns.Only descriptions matching the schema, procedure and parameter name criteria are returned. They are ordered by JDBC 4.1[PROCEDURE_CAT,] PROCEDURE_SCHEM, PROCEDURE_NAME and SPECIFIC_NAME. Within this, the return value, if any, is first. Next are the parameter descriptions in call order. The column descriptions follow in column number order.
Each row in the
ResultSet
is a parameter description or column description with the following fields:- PROCEDURE_CAT String
=>
procedure catalog (may benull
) - PROCEDURE_SCHEM String
=>
procedure schema (may benull
) - PROCEDURE_NAME String
=>
procedure name - COLUMN_NAME String
=>
column/parameter name - COLUMN_TYPE Short
=>
kind of column/parameter:- procedureColumnUnknown - nobody knows
- procedureColumnIn - IN parameter
- procedureColumnInOut - INOUT parameter
- procedureColumnOut - OUT parameter
- procedureColumnReturn - procedure return value
- procedureColumnResult - result column in
ResultSet
- DATA_TYPE int
=>
SQL type from java.sql.Types - TYPE_NAME String
=>
SQL type name, for a UDT type the type name is fully qualified - PRECISION int
=>
precision - LENGTH int
=>
length in bytes of data - SCALE short
=>
scale - null is returned for data types where SCALE is not applicable. - RADIX short
=>
radix - NULLABLE short
=>
can it contain NULL.- procedureNoNulls - does not allow NULL values
- procedureNullable - allows NULL values
- procedureNullableUnknown - nullability unknown
- REMARKS String
=>
comment describing parameter/column - COLUMN_DEF String
=>
default value for the column, which should be interpreted as a string when the value is enclosed in single quotes (may benull
)- The string NULL (not enclosed in quotes) - if NULL was specified as the default value
- TRUNCATE (not enclosed in quotes) - if the specified default value cannot be represented without truncation
- NULL - if a default value was not specified
- SQL_DATA_TYPE int
=>
(JDBC4 new:) Reserved for future useHSQLDB-specific: CLI type from SQL 2003 Table 37, tables 6-9 Annex A1, and/or addenda in other documents, such as:
SQL 2003 Part 9: Management of External Data (SQL/MED) : DATALINK
SQL 2003 Part 14: XML-Related Specifications (SQL/XML) : XML - SQL_DATETIME_SUB int
=>
(JDBC4 new:) reserved for future useHSQLDB-specific: CLI SQL_DATETIME_SUB from SQL 2003 Table 37
- CHAR_OCTET_LENGTH int
=>
(JDBC4 new:) the maximum length of binary and character based columns. For any other datatype the returned value is a NULL - ORDINAL_POSITION int
=>
(JDBC4 new:) the ordinal position, starting from 1, for the input and output parameters for a procedure. A value of 0 is returned if this row describes the procedure's return value. JDBC 4.1[For result set columns, it is the ordinal position of the column in the result set starting from 1. If there are multiple result sets, the column ordinal positions are implementation defined.] - IS_NULLABLE String
=>
ISO rules are used to determine the nullability for a column.- YES --- if the parameter or result column can include NULLs
- NO --- if the parameter or result column cannot include NULLs
- empty string --- if the nullability for the parameter or result column is unknown
- SPECIFIC_NAME String
=>
(JDBC4 new:) the name which uniquely identifies this procedure within its schema.
Note: Some databases may not return the column descriptions for a procedure. Additional columns beyond (JDBC4 modified:) SPECIFIC_NAME can be defined by the database and must be accessed by their column name.
(JDBC4 clarification:)
The PRECISION column represents the specified column size for the given column. For numeric data, this is the maximum precision. For character data, this is the [declared or implicit maximum] length in characters. For datetime datatypes, this is the [maximum] length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the [maximum] length in bytes. For the ROWID datatype, this is the length in bytes[, as returned by the implementation-specific java.sql.RowId.getBytes() method]. JDBC 4.1 Deleted[0] JDBC 4.1 Added[Null] is returned for data types where the column size is not applicable.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getProcedureColumns
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchprocedureNamePattern
- a procedure name pattern; must match the procedure name as it is stored in the databasecolumnNamePattern
- a column name pattern; must match the column name as it is stored in the database- Returns:
ResultSet
- each row describes a stored procedure parameter or column- Throws:
SQLException
- if a database access error occurs- See Also:
- PROCEDURE_CAT String
-
getTables
public ResultSet getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types) throws SQLException Retrieves a description of the tables available in the given catalog. Only table descriptions matching the catalog, schema, table name and type criteria are returned. They are ordered byTABLE_TYPE
, JDBC 4.1[TABLE_CAT
,]TABLE_SCHEM
andTABLE_NAME
.Each table description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - TABLE_TYPE String
=>
table type. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", "GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", "SYNONYM". - REMARKS String
=>
explanatory comment on the table - TYPE_CAT String
=>
the types catalog (may benull
) - TYPE_SCHEM String
=>
the types schema (may benull
) - TYPE_NAME String
=>
type name (may benull
) - SELF_REFERENCING_COL_NAME String
=>
name of the designated "identifier" column of a typed table (may benull
) - REF_GENERATION String
=>
specifies how values in SELF_REFERENCING_COL_NAME are created. Values are "SYSTEM", "USER", "DERIVED". (may benull
)
Note: Some databases may not return information for all tables.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
HSQLDB returns extra information on TEXT tables in the REMARKS column.
HSQLDB includes the JDBC3 columns TYPE_CAT, TYPE_SCHEM, TYPE_NAME and SELF_REFERENCING_COL_NAME in anticipation of JDBC3 compliant tools.
Since 1.7.2, this feature is supported by default. If the jar is compiled without org.hsqldb.dbinfo.DatabaseInformationMain, the feature is not supported. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getTables
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtableNamePattern
- a table name pattern; must match the table name as it is stored in the databasetypes
- a list of table types, which must be from the list of table types returned fromgetTableTypes()
,to include;null
returns all types- Returns:
ResultSet
- each row is a table description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
getSchemas
Retrieves the schema names available in this database. The results are ordered by JDBC 4.1[TABLE_CATALOG
] andTABLE_SCHEM
.The schema columns are:
- TABLE_SCHEM String
=>
schema name - TABLE_CATALOG String
=>
catalog name (may benull
)
HSQLDB-Specific Information:
Starting with 1.8.0, the list of schemas is returned.
- Specified by:
getSchemas
in interfaceDatabaseMetaData
- Returns:
- a
ResultSet
object in which each row is a schema description - Throws:
SQLException
- if a database access error occurs
- TABLE_SCHEM String
-
getCatalogs
Retrieves the catalog names available in this database. The results are ordered by catalog name.The catalog column is:
- TABLE_CAT String
=>
catalog name
HSQLDB-Specific Information:
Since 1.7.2, this feature is supported by default. If the jar is compiled without org.hsqldb.dbinfo.DatabaseInformationMain, the feature is not supported. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getCatalogs
in interfaceDatabaseMetaData
- Returns:
- a
ResultSet
object in which each row has a singleString
column that is a catalog name - Throws:
SQLException
- if a database access error occurs
- TABLE_CAT String
-
getTableTypes
Retrieves the table types available in this database. The results are ordered by table type.The table type is:
- TABLE_TYPE String
=>
table type. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", "GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", "SYNONYM".
HSQLDB-Specific Information:
Since 1.7.1, HSQLDB reports: "TABLE", "VIEW" and "GLOBAL TEMPORARY" types. Since 1.7.2, this feature is supported by default. If the jar is compiled without org.hsqldb.dbinfo.DatabaseInformationMain, the feature is not supported. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getTableTypes
in interfaceDatabaseMetaData
- Returns:
- a
ResultSet
object in which each row has a singleString
column that is a table type - Throws:
SQLException
- if a database access error occurs
- TABLE_TYPE String
-
getColumns
public ResultSet getColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) throws SQLException Retrieves a description of table columns available in the specified catalog.Only column descriptions matching the catalog, schema, table and column name criteria are returned. They are ordered by JDBC 4.1[
TABLE_CAT
, ]TABLE_SCHEM
,TABLE_NAME
, andORDINAL_POSITION
.Each column description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - COLUMN_NAME String
=>
column name - DATA_TYPE int
=>
SQL type from java.sql.Types - TYPE_NAME String
=>
Data source dependent type name, for a UDT the type name is fully qualified - COLUMN_SIZE int
=>
column size. - BUFFER_LENGTH is not used.
- DECIMAL_DIGITS int
=>
the number of fractional digits. Null is returned for data types where DECIMAL_DIGITS is not applicable. - NUM_PREC_RADIX int
=>
Radix (typically either 10 or 2) - NULLABLE int
=>
is NULL allowed.- columnNoNulls - might not allow
NULL
values - columnNullable - definitely allows
NULL
values - columnNullableUnknown - nullability unknown
- columnNoNulls - might not allow
- REMARKS String
=>
comment describing column (may benull
) - COLUMN_DEF String
=>
(JDBC4 clarification:) default value for the column, which should be interpreted as a string when the value is enclosed in quotes (may benull
) - SQL_DATA_TYPE int
=>
unusedHSQLDB-specific: CLI type from SQL 2003 Table 37, tables 6-9 Annex A1, and/or addendums in other documents, such as:
SQL 2003 Part 9: Management of External Data (SQL/MED) : DATALINK
SQL 2003 Part 14: XML-Related Specifications (SQL/XML) : XML - SQL_DATETIME_SUB int
=>
unused (HSQLDB-specific: SQL 2003 CLI datetime/interval subcode) - CHAR_OCTET_LENGTH int
=>
for char types the maximum number of bytes in the column - ORDINAL_POSITION int
=>
index of column in table (starting at 1) - IS_NULLABLE String
=>
ISO rules are used to determine the nullability for a column.- YES --- if the column can include NULLs
- NO --- if the column cannot include NULLs
- empty string --- if the nullability for the column is unknown
- JDBC 4.1 Deleted[SCOPE_CATLOG] JDBC 4.1 Added[SCOPE_CATALOG] String
=>
catalog of table that is the scope of a reference attribute (null
if DATA_TYPE isn't REF) - SCOPE_SCHEMA String
=>
schema of table that is the scope of a reference attribute (null
if the DATA_TYPE isn't REF) - SCOPE_TABLE String
=>
table name that this the scope of a reference attribute (null
if the DATA_TYPE isn't REF) - SOURCE_DATA_TYPE short
=>
source type of a distinct type or user-generated Ref type, SQL type from java.sql.Types (null
if DATA_TYPE isn't DISTINCT or user-generated REF) - IS_AUTOINCREMENT String
=>
Indicates whether this column is auto incremented- YES --- if the column is auto incremented
- NO --- if the column is not auto incremented
- empty string --- if it cannot be determined whether the column is auto incremented
- (JDBC 4.1 New:)IS_GENERATEDCOLUMN String
=>
Indicates whether this is a generated column- YES --- if this a generated column
- NO --- if this not a generated column
- empty string --- if it cannot be determined whether this is a generated column
(JDBC4 clarification:) The COLUMN_SIZE column represents the specified column size for the given column. For numeric data, this is the maximum precision. For character data, this is the [declared or implicit maximum] length in characters. For datetime datatypes, this is the [maximum] length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the [maximum] length in bytes. For the ROWID datatype, this is the length in bytes[, as returned by the implementation-specific java.sql.RowId.getBytes() method]. JDBC 4.1 Deleted[0] JDBC 4.1 Added[Null] is returned for data types where the column size is not applicable.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
This feature is supported by default. If the jar is compiled without org.hsqldb.dbinfo.DatabaseInformationMain, the feature is not supported. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getColumns
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtableNamePattern
- a table name pattern; must match the table name as it is stored in the databasecolumnNamePattern
- a column name pattern; must match the column name as it is stored in the database- Returns:
ResultSet
- each row is a column description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
getColumnPrivileges
public ResultSet getColumnPrivileges(String catalog, String schema, String table, String columnNamePattern) throws SQLException Retrieves a description of the access rights for a table's columns.Only privileges matching the column name criteria are returned. They are ordered by COLUMN_NAME and PRIVILEGE.
Each privilege description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - COLUMN_NAME String
=>
column name - GRANTOR String
=>
grantor of access (may benull
) - GRANTEE String
=>
grantee of access - PRIVILEGE String
=>
name of access (SELECT, INSERT, UPDATE, REFRENCES, ...) - IS_GRANTABLE String
=>
"YES" if grantee is permitted to grant to others; "NO" if not;null
if unknown
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
This feature is supported by default. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getColumnPrivileges
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in the databasecolumnNamePattern
- a column name pattern; must match the column name as it is stored in the database- Returns:
ResultSet
- each row is a column privilege description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
getTablePrivileges
public ResultSet getTablePrivileges(String catalog, String schemaPattern, String tableNamePattern) throws SQLException Retrieves a description of the access rights for each table available in a catalog. Note that a table privilege applies to one or more columns in the table. It would be wrong to assume that this privilege applies to all columns (this may be true for some systems but is not true for all.)Only privileges matching the schema and table name criteria are returned. They are ordered by JDBC 4.1[
TABLE_CAT
,]TABLE_SCHEM
,TABLE_NAME
, andPRIVILEGE
.Each privilege description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - GRANTOR String
=>
grantor of access (may benull
) - GRANTEE String
=>
grantee of access - PRIVILEGE String
=>
name of access (SELECT, INSERT, UPDATE, REFRENCES, ...) - IS_GRANTABLE String
=>
"YES" if grantee is permitted to grant to others; "NO" if not;null
if unknown
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getTablePrivileges
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtableNamePattern
- a table name pattern; must match the table name as it is stored in the database- Returns:
ResultSet
- each row is a table privilege description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
getBestRowIdentifier
public ResultSet getBestRowIdentifier(String catalog, String schema, String table, int scope, boolean nullable) throws SQLException Retrieves a description of a table's optimal set of columns that uniquely identifies a row. They are ordered by SCOPE.Each column description has the following columns:
- SCOPE short
=>
actual scope of result- bestRowTemporary - very temporary, while using row
- bestRowTransaction - valid for remainder of current transaction
- bestRowSession - valid for remainder of current session
- COLUMN_NAME String
=>
column name - DATA_TYPE int
=>
SQL data type from java.sql.Types - TYPE_NAME String
=>
Data source dependent type name, for a UDT the type name is fully qualified - COLUMN_SIZE int
=>
precision - BUFFER_LENGTH int
=>
not used - DECIMAL_DIGITS short
=>
scale - Null is returned for data types where DECIMAL_DIGITS is not applicable. - PSEUDO_COLUMN short
=>
is this a pseudo column like an Oracle ROWID- bestRowUnknown - may or may not be pseudo column
- bestRowNotPseudo - is NOT a pseudo column
- bestRowPseudo - is a pseudo column
(JDBC4 clarification:)
The COLUMN_SIZE column represents the specified column size for the given column. For numeric data, this is the maximum precision. For character data, this is the [declared or implicit maximum] length in characters. For datetime datatypes, this is the [maximum] length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the [maximum] length in bytes. For the ROWID datatype, this is the length in bytes[, as returned by the implementation-specific java.sql.RowId.getBytes() method]. JDBC 4.1 Deleted[0] JDBC 4.1 Added[Null] is returned for data types where the column size is not applicable.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
If the name of a column is defined in the database without double quotes, an all-uppercase name must be specified when calling this method. Otherwise, the name must be specified in the exact case of the column definition in the database.
- Specified by:
getBestRowIdentifier
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in the databasescope
- the scope of interest; use same values as SCOPEnullable
- include columns that are nullable.- Returns:
ResultSet
- each row is a column description- Throws:
SQLException
- if a database access error occurs
- SCOPE short
-
getVersionColumns
Retrieves a description of a table's columns that are automatically updated when any value in a row is updated. They are unordered.Each column description has the following columns:
- SCOPE short
=>
is not used - COLUMN_NAME String
=>
column name - DATA_TYPE int
=>
SQL data type fromjava.sql.Types
- TYPE_NAME String
=>
Data source-dependent type name - COLUMN_SIZE int
=>
precision - BUFFER_LENGTH int
=>
length of column value in bytes - DECIMAL_DIGITS short
=>
scale - Null is returned for data types where DECIMAL_DIGITS is not applicable. - PSEUDO_COLUMN short
=>
whether this is pseudo column like an Oracle ROWID- versionColumnUnknown - may or may not be pseudo column
- versionColumnNotPseudo - is NOT a pseudo column
- versionColumnPseudo - is a pseudo column
(JDBC4 clarification:)
The COLUMN_SIZE column represents the specified column size for the given column. For numeric data, this is the maximum precision. For character data, this is the [declared or implicit maximum] length in characters. For datetime datatypes, this is the [maximum] length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the [maximum] length in bytes. For the ROWID datatype, this is the length in bytes[, as returned by the implementation-specific java.sql.RowId.getBytes() method]. JDBC 4.1 Deleted[0], JDBC 4.1 Added[Null] is returned for data types where the column size is not applicable.
HSQLDB-Specific Information:
HSQLDB 2.5.0 and later returns information on auto-updated TIMESTAMP columns defined with ON UPDATE CURRENT_TIMESTAMP, and the columns of SYSTEM_TIME periods. Columns defined as GENERATED AS IDENTITY, SEQUENCE, or an expression are not returned as they are not always automatically updated when other columns in a row are updated.
- Specified by:
getVersionColumns
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in the database- Returns:
- a
ResultSet
object in which each row is a column description - Throws:
SQLException
- if a database access error occurs
- SCOPE short
-
getPrimaryKeys
Retrieves a description of the given table's primary key columns. They are ordered by COLUMN_NAME.Each primary key column description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - COLUMN_NAME String
=>
column name - KEY_SEQ short
=>
(JDBC4 Clarification:) sequence number within primary key( a value of 1 represents the first column of the primary key, a value of 2 would represent the second column within the primary key). - PK_NAME String
=>
primary key name (may benull
)
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getPrimaryKeys
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in the database- Returns:
ResultSet
- each row is a primary key column description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
getImportedKeys
Retrieves a description of the primary key columns that are referenced by the given table's foreign key columns (the primary keys imported by a table). They are ordered by PKTABLE_CAT, PKTABLE_SCHEM, PKTABLE_NAME, and KEY_SEQ.Each primary key column description has the following columns:
- PKTABLE_CAT String
=>
primary key table catalog being imported (may benull
) - PKTABLE_SCHEM String
=>
primary key table schema being imported (may benull
) - PKTABLE_NAME String
=>
primary key table name being imported - PKCOLUMN_NAME String
=>
primary key column name being imported - FKTABLE_CAT String
=>
foreign key table catalog (may benull
) - FKTABLE_SCHEM String
=>
foreign key table schema (may benull
) - FKTABLE_NAME String
=>
foreign key table name - FKCOLUMN_NAME String
=>
foreign key column name - KEY_SEQ short
=>
(JDBC4 clarification) sequence number within a foreign key (a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key). - UPDATE_RULE short
=>
What happens to a foreign key when the primary key is updated:- importedNoAction - do not allow update of primary key if it has been imported
- importedKeyCascade - change imported key to agree with primary key update
- importedKeySetNull - change imported key to
NULL
if its primary key has been updated - importedKeySetDefault - change imported key to default values if its primary key has been updated
- importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- DELETE_RULE short
=>
What happens to the foreign key when primary is deleted.- importedKeyNoAction - do not allow delete of primary key if it has been imported
- importedKeyCascade - delete rows that import a deleted key
- importedKeySetNull - change imported key to NULL if its primary key has been deleted
- importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- importedKeySetDefault - change imported key to default if its primary key has been deleted
- FK_NAME String
=>
foreign key name (may benull
) - PK_NAME String
=>
primary key name (may benull
) - DEFERRABILITY short
=>
can the evaluation of foreign key constraints be deferred until commit- importedKeyInitiallyDeferred - see SQL92 for definition
- importedKeyInitiallyImmediate - see SQL92 for definition
- importedKeyNotDeferrable - see SQL92 for definition
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getImportedKeys
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in the database- Returns:
ResultSet
- each row is a primary key column description- Throws:
SQLException
- if a database access error occurs- See Also:
- PKTABLE_CAT String
-
getExportedKeys
Retrieves a description of the foreign key columns that reference the given table's primary key columns (the foreign keys exported by a table). They are ordered by FKTABLE_CAT, FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ.Each foreign key column description has the following columns:
- PKTABLE_CAT String
=>
primary key table catalog (may benull
) - PKTABLE_SCHEM String
=>
primary key table schema (may benull
) - PKTABLE_NAME String
=>
primary key table name - PKCOLUMN_NAME String
=>
primary key column name - FKTABLE_CAT String
=>
foreign key table catalog (may benull
) being exported (may benull
) - FKTABLE_SCHEM String
=>
foreign key table schema (may benull
) being exported (may benull
) - FKTABLE_NAME String
=>
foreign key table name being exported - FKCOLUMN_NAME String
=>
foreign key column name being exported - KEY_SEQ short
=>
(JDBC4 clarification:) sequence number within foreign key( a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key). - UPDATE_RULE short
=>
What happens to foreign key when primary is updated:- importedNoAction - do not allow update of primary key if it has been imported
- importedKeyCascade - change imported key to agree with primary key update
- importedKeySetNull - change imported key to
NULL
if its primary key has been updated - importedKeySetDefault - change imported key to default values if its primary key has been updated
- importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- DELETE_RULE short
=>
What happens to the foreign key when primary is deleted.- importedKeyNoAction - do not allow delete of primary key if it has been imported
- importedKeyCascade - delete rows that import a deleted key
- importedKeySetNull - change imported key to
NULL
if its primary key has been deleted - importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- importedKeySetDefault - change imported key to default if its primary key has been deleted
- FK_NAME String
=>
foreign key name (may benull
) - PK_NAME String
=>
primary key name (may benull
) - DEFERRABILITY short
=>
can the evaluation of foreign key constraints be deferred until commit- importedKeyInitiallyDeferred - see SQL92 for definition
- importedKeyInitiallyImmediate - see SQL92 for definition
- importedKeyNotDeferrable - see SQL92 for definition
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getExportedKeys
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in this database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in this database- Returns:
- a
ResultSet
object in which each row is a foreign key column description - Throws:
SQLException
- if a database access error occurs- See Also:
- PKTABLE_CAT String
-
getCrossReference
public ResultSet getCrossReference(String parentCatalog, String parentSchema, String parentTable, String foreignCatalog, String foreignSchema, String foreignTable) throws SQLException (JDBC4 clarification:) Retrieves a description of the foreign key columns in the given foreign key table that reference the primary key or the columns representing a unique constraint of the parent table (could be the same or a different table). The number of columns returned from the parent table must match the number of columns that make up the foreign key. They are ordered by FKTABLE_CAT, FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ.Each foreign key column description has the following columns:
- PKTABLE_CAT String
=>
parent key table catalog (may benull
) - PKTABLE_SCHEM String
=>
parent key table schema (may benull
) - PKTABLE_NAME String
=>
parent key table name - PKCOLUMN_NAME String
=>
parent key column name - FKTABLE_CAT String
=>
foreign key table catalog (may benull
) being exported (may benull
) - FKTABLE_SCHEM String
=>
foreign key table schema (may benull
) being exported (may benull
) - FKTABLE_NAME String
=>
foreign key table name being exported - FKCOLUMN_NAME String
=>
foreign key column name being exported - KEY_SEQ short
=>
sequence number within foreign key( a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key). - UPDATE_RULE short
=>
What happens to foreign key when parent key is updated:- importedNoAction - do not allow update of parent key if it has been imported
- importedKeyCascade - change imported key to agree with parent key update
- importedKeySetNull - change imported key to
NULL
if its parent key has been updated - importedKeySetDefault - change imported key to default values if its parent key has been updated
- importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- DELETE_RULE short
=>
What happens to the foreign key when parent key is deleted.- importedKeyNoAction - do not allow delete of parent key if it has been imported
- importedKeyCascade - delete rows that import a deleted key
- importedKeySetNull - change imported key to
NULL
if its primary key has been deleted - importedKeyRestrict - same as importedKeyNoAction (for ODBC 2.x compatibility)
- importedKeySetDefault - change imported key to default if its parent key has been deleted
- FK_NAME String
=>
foreign key name (may benull
) - PK_NAME String
=>
parent key name (may benull
) - DEFERRABILITY short
=>
can the evaluation of foreign key constraints be deferred until commit- importedKeyInitiallyDeferred - see SQL92 for definition
- importedKeyInitiallyImmediate - see SQL92 for definition
- importedKeyNotDeferrable - see SQL92 for definition
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getCrossReference
in interfaceDatabaseMetaData
- Parameters:
parentCatalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means drop catalog name from the selection criteriaparentSchema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means drop schema name from the selection criteriaparentTable
- the name of the table that exports the key; must match the table name as it is stored in the databaseforeignCatalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means drop catalog name from the selection criteriaforeignSchema
- a schema name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means drop schema name from the selection criteriaforeignTable
- the name of the table that imports the key; must match the table name as it is stored in the database- Returns:
ResultSet
- each row is a foreign key column description- Throws:
SQLException
- if a database access error occurs- See Also:
- PKTABLE_CAT String
-
getTypeInfo
Retrieves a description of all the (JDBC4 clarification:) data types supported by this database. They are ordered by DATA_TYPE and then by how closely the data type maps to the corresponding JDBC SQL type.(JDBC4 clarification:) If the database supports SQL distinct types, then getTypeInfo() will return a single row with a TYPE_NAME of DISTINCT and a DATA_TYPE of Types.DISTINCT. If the database supports SQL structured types, then getTypeInfo() will return a single row with a TYPE_NAME of STRUCT and a DATA_TYPE of Types.STRUCT.
(JDBC4 clarification:)
If SQL distinct or structured types are supported, then information on the individual types may be obtained from the getUDTs() method.
Each type description has the following columns:
- TYPE_NAME String
=>
Type name - DATA_TYPE int
=>
SQL data type from java.sql.Types - PRECISION int
=>
maximum precision - LITERAL_PREFIX String
=>
prefix used to quote a literal (may benull
) - LITERAL_SUFFIX String
=>
suffix used to quote a literal (may benull
) - CREATE_PARAMS String
=>
parameters used in creating the type (may benull
) - NULLABLE short
=>
can you use NULL for this type.- typeNoNulls - does not allow NULL values
- typeNullable - allows NULL values
- typeNullableUnknown - nullability unknown
- CASE_SENSITIVE boolean
=>
is it case sensitive. - SEARCHABLE short
=>
can you use "WHERE" based on this type:- typePredNone - No support
- typePredChar - Only supported with WHERE .. LIKE
- typePredBasic - Supported except for WHERE .. LIKE
- typeSearchable - Supported for all WHERE ..
- UNSIGNED_ATTRIBUTE boolean
=>
is it unsigned. - FIXED_PREC_SCALE boolean
=>
can it be a money value. - AUTO_INCREMENT boolean
=>
can it be used for an auto-increment value. - LOCAL_TYPE_NAME String
=>
localized version of type name (may benull
) - MINIMUM_SCALE short
=>
minimum scale supported - MAXIMUM_SCALE short
=>
maximum scale supported - SQL_DATA_TYPE int
=>
unused - SQL_DATETIME_SUB int
=>
unused - NUM_PREC_RADIX int
=>
usually 2 or 10
(JDBC4 clarification:) The PRECISION column represents the maximum column size that the server supports for the given datatype. For numeric data, this is the maximum precision. For character data, this is the [maximum] length in characters. For datetime datatypes, this is the [maximum] length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the [maximum] length in bytes. For the ROWID datatype, this is the length in bytes[, as returned by the implementation-specific java.sql.RowId.getBytes() method]. JDBC 4.1 Deleted[0] JDBC 4.1 Added[Null] is returned for data types where the column size is not applicable.
HSQLDB-Specific Information:
This feature is supported.
- Specified by:
getTypeInfo
in interfaceDatabaseMetaData
- Returns:
- a
ResultSet
object in which each row is an SQL type description - Throws:
SQLException
- if a database access error occurs
- TYPE_NAME String
-
getIndexInfo
public ResultSet getIndexInfo(String catalog, String schema, String table, boolean unique, boolean approximate) throws SQLException Retrieves a description of the given table's indices and statistics. They are ordered by NON_UNIQUE, TYPE, INDEX_NAME, and ORDINAL_POSITION.Each index column description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - NON_UNIQUE boolean
=>
Can index values be non-unique. false when TYPE is tableIndexStatistic - INDEX_QUALIFIER String
=>
index catalog (may benull
);null
when TYPE is tableIndexStatistic - INDEX_NAME String
=>
index name;null
when TYPE is tableIndexStatistic - TYPE short
=>
index type:- tableIndexStatistic - this identifies table statistics that are returned in conjunction with a table's index descriptions
- tableIndexClustered - this is a clustered index
- tableIndexHashed - this is a hashed index
- tableIndexOther - this is some other style of index
- ORDINAL_POSITION short
=>
column sequence number within index; zero when TYPE is tableIndexStatistic - COLUMN_NAME String
=>
column name;null
when TYPE is tableIndexStatistic - ASC_OR_DESC String
=>
column sort sequence, "A"=>
ascending, "D"=>
descending, may benull
if sort sequence is not supported;null
when TYPE is tableIndexStatistic - CARDINALITY int
=>
When TYPE is tableIndexStatistic, then this is the number of rows in the table; otherwise, it is the number of unique values in the index. - PAGES int
=>
When TYPE is tableIndexStatistic then this is the number of pages used for the table, otherwise it is the number of pages used for the current index. - FILTER_CONDITION String
=>
Filter condition, if any. (may benull
)
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
- Specified by:
getIndexInfo
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in this database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschema
- a schema name; must match the schema name as it is stored in this database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtable
- a table name; must match the table name as it is stored in this databaseunique
- when true, return only indices for unique values; when false, return indices regardless of whether unique or notapproximate
- when true, result is allowed to reflect approximate or out of data values; when false, results are requested to be accurate- Returns:
ResultSet
- each row is an index column description- Throws:
SQLException
- if a database access error occurs- See Also:
- TABLE_CAT String
-
supportsResultSetType
Retrieves whether this database supports the given result set type.- Specified by:
supportsResultSetType
in interfaceDatabaseMetaData
- Parameters:
type
- defined injava.sql.ResultSet
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
- See Also:
-
supportsResultSetConcurrency
Retrieves whether this database supports the given concurrency type in combination with the given result set type.- Specified by:
supportsResultSetConcurrency
in interfaceDatabaseMetaData
- Parameters:
type
- defined injava.sql.ResultSet
concurrency
- type defined injava.sql.ResultSet
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
- See Also:
-
ownUpdatesAreVisible
Retrieves whether for the given type ofResultSet
object, the result set's own updates are visible.HSQLDB-Specific Information:
Updates to ResultSet rows are not visible after moving from the updated row.
- Specified by:
ownUpdatesAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if updates are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
ownDeletesAreVisible
Retrieves whether a result set's own deletes are visible.HSQLDB-Specific Information:
Rows deleted from the ResultSet are still visible after moving from the deleted row.
- Specified by:
ownDeletesAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if deletes are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
ownInsertsAreVisible
Retrieves whether a result set's own inserts are visible.HSQLDB-Specific Information:
Rows added to a ResultSet are not visible after moving from the insert row; this method always returns
false
.- Specified by:
ownInsertsAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if inserts are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
othersUpdatesAreVisible
Retrieves whether updates made by others are visible.HSQLDB-Specific Information:
Updates made by other connections or the same connection while the ResultSet is open are not visible in the ResultSet.
- Specified by:
othersUpdatesAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if updates made by others are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
othersDeletesAreVisible
Retrieves whether deletes made by others are visible.HSQLDB-Specific Information:
Deletes made by other connections or the same connection while the ResultSet is open are not visible in the ResultSet.
- Specified by:
othersDeletesAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if deletes made by others are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
othersInsertsAreVisible
Retrieves whether inserts made by others are visible.HSQLDB-Specific Information:
Inserts made by other connections or the same connection while the ResultSet is open are not visible in the ResultSet.
- Specified by:
othersInsertsAreVisible
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if inserts made by others are visible for the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
updatesAreDetected
Retrieves whether or not a visible row update can be detected by calling the methodResultSet.rowUpdated
.HSQLDB-Specific Information:
Updates made to the rows of the ResultSet are not detected by calling the
ResultSet.rowUpdated
.- Specified by:
updatesAreDetected
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if changes are detected by the result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
deletesAreDetected
Retrieves whether or not a visible row delete can be detected by calling the methodResultSet.rowDeleted
. If the methoddeletesAreDetected
returnsfalse
, it means that deleted rows are removed from the result set.HSQLDB-Specific Information:
Deletes made to the rows of the ResultSet are not detected by calling the
ResultSet.rowDeleted
.- Specified by:
deletesAreDetected
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if deletes are detected by the given result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
insertsAreDetected
Retrieves whether or not a visible row insert can be detected by calling the methodResultSet.rowInserted
.HSQLDB-Specific Information:
Inserts made into the ResultSet are not visible and thus not detected by calling the
ResultSet.rowInserted
.- Specified by:
insertsAreDetected
in interfaceDatabaseMetaData
- Parameters:
type
- theResultSet
type; one ofResultSet.TYPE_FORWARD_ONLY
,ResultSet.TYPE_SCROLL_INSENSITIVE
, orResultSet.TYPE_SCROLL_SENSITIVE
- Returns:
true
if changes are detected by the specified result set type;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
supportsBatchUpdates
Retrieves whether this database supports batch updates.HSQLDB-Specific Information:
HSQLDB supports batch updates; this method always returns
true
.- Specified by:
supportsBatchUpdates
in interfaceDatabaseMetaData
- Returns:
true
if this database supports batch updates;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
getUDTs
public ResultSet getUDTs(String catalog, String schemaPattern, String typeNamePattern, int[] types) throws SQLException Retrieves a description of the user-defined types (UDTs) defined in a particular schema. Schema-specific UDTs may have typeJAVA_OBJECT
,STRUCT
, orDISTINCT
.Only types matching the catalog, schema, type name and type criteria are returned. They are ordered by
DATA_TYPE
, JDBC 4.1[TYPE_CAT
,]TYPE_SCHEM
andTYPE_NAME
. The type name parameter may be a fully-qualified name. In this case, the catalog and schemaPattern parameters are ignored.Each type description has the following columns:
- TYPE_CAT String
=>
the type's catalog (may benull
) - TYPE_SCHEM String
=>
type's schema (may benull
) - TYPE_NAME String
=>
type name - CLASS_NAME String
=>
Java class name - DATA_TYPE int
=>
type value defined in java.sql.Types. One of JAVA_OBJECT, STRUCT, or DISTINCT - REMARKS String
=>
explanatory comment on the type - BASE_TYPE short
=>
type code of the source type of a DISTINCT type or the type that implements the user-generated reference type of the SELF_REFERENCING_COLUMN of a structured type as defined in java.sql.Types (null
if DATA_TYPE is not DISTINCT or not STRUCT with REFERENCE_GENERATION = USER_DEFINED)
Note: If the driver does not support UDTs, an empty result set is returned.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
Starting with 2.0, DISTICT types are supported and are reported by this method.
- Specified by:
getUDTs
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema pattern name; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtypeNamePattern
- a type name pattern; must match the type name as it is stored in the database; may be a fully qualified nametypes
- a list of user-defined types (JAVA_OBJECT, STRUCT, or DISTINCT) to include;null
returns all types- Returns:
ResultSet
object in which each row describes a UDT- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
- See Also:
- TYPE_CAT String
-
getConnection
Retrieves the connection that produced this metadata object.- Specified by:
getConnection
in interfaceDatabaseMetaData
- Returns:
- the connection that produced this metadata object
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.2
-
supportsSavepoints
Retrieves whether this database supports savepoints.HSQLDB-Specific Information:
This SQL feature is supported through JDBC as well as SQL.
- Specified by:
supportsSavepoints
in interfaceDatabaseMetaData
- Returns:
true
if savepoints are supported;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
supportsNamedParameters
Retrieves whether this database supports named parameters to callable statements.HSQLDB-Specific Information:
HSQLDB supports JDBC named parameters to callable statements; this method returns true.
- Specified by:
supportsNamedParameters
in interfaceDatabaseMetaData
- Returns:
true
if named parameters are supported;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
supportsMultipleOpenResults
Retrieves whether it is possible to have multipleResultSet
objects returned from aCallableStatement
object simultaneously.HSQLDB-Specific Information:
HSQLDB supports multiple ResultSet objects returned from a
CallableStatement
; this method always returnstrue
.- Specified by:
supportsMultipleOpenResults
in interfaceDatabaseMetaData
- Returns:
true
if aCallableStatement
object can return multipleResultSet
objects simultaneously;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
supportsGetGeneratedKeys
Retrieves whether auto-generated keys can be retrieved after a statement has been executedHSQLDB-Specific Information:
HSQLDB supports retrieval of autogenerated keys through the JDBC interface; this method always returns
true
.- Specified by:
supportsGetGeneratedKeys
in interfaceDatabaseMetaData
- Returns:
true
if auto-generated keys can be retrieved after a statement has executed;false
otherwise(JDBC4 Clarification:)
If
true
is returned, the JDBC driver must support the returning of auto-generated keys for at least SQL INSERT statements- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getSuperTypes
public ResultSet getSuperTypes(String catalog, String schemaPattern, String typeNamePattern) throws SQLException Retrieves a description of the user-defined type (UDT) hierarchies defined in a particular schema in this database. Only the immediate super type sub type relationship is modeled.Only supertype information for UDTs matching the catalog, schema, and type name is returned. The type name parameter may be a fully-qualified name. When the UDT name supplied is a fully-qualified name, the catalog and schemaPattern parameters are ignored.
If a UDT does not have a direct super type, it is not listed here. A row of the
ResultSet
object returned by this method describes the designated UDT and a direct supertype. A row has the following columns:- TYPE_CAT String
=>
the UDT's catalog (may benull
) - TYPE_SCHEM String
=>
UDT's schema (may benull
) - TYPE_NAME String
=>
type name of the UDT - SUPERTYPE_CAT String
=>
the direct super type's catalog (may benull
) - SUPERTYPE_SCHEM String
=>
the direct super type's schema (may benull
) - SUPERTYPE_NAME String
=>
the direct super type's name
Note: If the driver does not support type hierarchies, an empty result set is returned.
HSQLDB-Specific Information:
HSQLDB supports the SQL Standard. It treats unquoted identifiers as case insensitive in SQL and stores them in upper case; it treats quoted identifiers as case sensitive and stores them verbatim. All JDBCDatabaseMetaData methods perform case-sensitive comparison between name (pattern) arguments and the corresponding identifier values as they are stored in the database. Therefore, care must be taken to specify name arguments precisely (including case) as they are stored in the database.
From 2.0, this feature is supported by default and return supertypes for DOMAIN and DISTINCT types.
If the jar is compiled without org.hsqldb.dbinfo.DatabaseInformationMain, the feature is not supported. The default implementation is the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getSuperTypes
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; "" retrieves those without a catalog;null
means drop catalog name from the selection criteriaschemaPattern
- a schema name pattern; "" retrieves those without a schematypeNamePattern
- a UDT name pattern; may be a fully-qualified name- Returns:
- a
ResultSet
object in which a row gives information about the designated UDT - Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
- TYPE_CAT String
-
getSuperTables
public ResultSet getSuperTables(String catalog, String schemaPattern, String tableNamePattern) throws SQLException Retrieves a description of the table hierarchies defined in a particular schema in this database.Only supertable information for tables matching the catalog, schema and table name are returned. The table name parameter may be a fully- qualified name, in which case, the catalog and schemaPattern parameters are ignored. If a table does not have a super table, it is not listed here. Supertables have to be defined in the same catalog and schema as the sub tables. Therefore, the type description does not need to include this information for the supertable.
Each type description has the following columns:
- TABLE_CAT String
=>
the type's catalog (may benull
) - TABLE_SCHEM String
=>
type's schema (may benull
) - TABLE_NAME String
=>
type name - SUPERTABLE_NAME String
=>
the direct super type's name
Note: If the driver does not support type hierarchies, an empty result set is returned.
HSQLDB-Specific Information:
This method is intended for tables of structured types. From 2.0 this method returns an empty ResultSet. the org.hsqldb.dbinfo.DatabaseInformationMain class.
- Specified by:
getSuperTables
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; "" retrieves those without a catalog;null
means drop catalog name from the selection criteriaschemaPattern
- a schema name pattern; "" retrieves those without a schematableNamePattern
- a table name pattern; may be a fully-qualified name- Returns:
- a
ResultSet
object in which each row is a type description - Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
- TABLE_CAT String
-
getAttributes
public ResultSet getAttributes(String catalog, String schemaPattern, String typeNamePattern, String attributeNamePattern) throws SQLException Retrieves a description of the given attribute of the given type for a user-defined type (UDT) that is available in the given schema and catalog.Descriptions are returned only for attributes of UDTs matching the catalog, schema, type, and attribute name criteria. They are ordered by JDBC 4.1[
TYPE_CAT
, ]TYPE_SCHEM
,TYPE_NAME
andORDINAL_POSITION
. This description does not contain inherited attributes.The
ResultSet
object that is returned has the following columns:- TYPE_CAT String
=>
type catalog (may benull
) - TYPE_SCHEM String
=>
type schema (may benull
) - TYPE_NAME String
=>
type name - ATTR_NAME String
=>
attribute name - DATA_TYPE int
=>
attribute type SQL type from java.sql.Types - ATTR_TYPE_NAME String
=>
Data source dependent type name. For a UDT, the type name is fully qualified. For a REF, the type name is fully qualified and represents the target type of the reference type. - ATTR_SIZE int
=>
column size. For char or date types this is the maximum number of characters; for numeric or decimal types this is precision. - DECIMAL_DIGITS int
=>
the number of fractional digits. Null is returned for data types where DECIMAL_DIGITS is not applicable. - NUM_PREC_RADIX int
=>
Radix (typically either 10 or 2) - NULLABLE int
=>
whether NULL is allowed- attributeNoNulls - might not allow NULL values
- attributeNullable - definitely allows NULL values
- attributeNullableUnknown - nullability unknown
- REMARKS String
=>
comment describing column (may benull
) - ATTR_DEF String
=>
default value (may benull
) - SQL_DATA_TYPE int
=>
unused - SQL_DATETIME_SUB int
=>
unused - CHAR_OCTET_LENGTH int
=>
for char types the maximum number of bytes in the column - ORDINAL_POSITION int
=>
index of JDBC 4.1 correction[the attribute in the UDT] (starting at 1) - IS_NULLABLE String
=>
ISO rules are used to determine the nullability for a column.- YES --- if the JDBC 4.1 correction[attribute] can include NULLs
- NO --- if the JDBC 4.1 correction[attribute] cannot include NULLs
- empty string --- if the nullability for the JDBC 4.1 correction[attribute] is unknown
- SCOPE_CATALOG String
=>
catalog of table that is the scope of a reference attribute (null
if DATA_TYPE isn't REF) - SCOPE_SCHEMA String
=>
schema of table that is the scope of a reference attribute (null
if DATA_TYPE isn't REF) - SCOPE_TABLE String
=>
table name that is the scope of a reference attribute (null
if the DATA_TYPE isn't REF) - SOURCE_DATA_TYPE short
=>
source type of a distinct type or user-generated Ref type,SQL type from java.sql.Types (null
if DATA_TYPE isn't DISTINCT or user-generated REF)
HSQLDB-Specific Information:
This method is intended for attributes of structured types. From 2.0 this method returns an empty ResultSet.
- Specified by:
getAttributes
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtypeNamePattern
- a type name pattern; must match the type name as it is stored in the databaseattributeNamePattern
- an attribute name pattern; must match the attribute name as it is declared in the database- Returns:
- a
ResultSet
object in which each row is an attribute description - Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
- TYPE_CAT String
-
supportsResultSetHoldability
Retrieves whether this database supports the given result set holdability.HSQLDB-Specific Information:
HSQLDB returns true for both alternatives.
- Specified by:
supportsResultSetHoldability
in interfaceDatabaseMetaData
- Parameters:
holdability
- one of the following constants:ResultSet.HOLD_CURSORS_OVER_COMMIT
orResultSet.CLOSE_CURSORS_AT_COMMIT
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
- See Also:
-
getResultSetHoldability
(JDBC4 clarification:) Retrieves this database's default holdability forResultSet
objects.HSQLDB-Specific Information:
HSQLDB defaults to HOLD_CURSORS_OVER_COMMIT for CONSUR_READ_ONLY ResultSet objects. If the ResultSet concurrency is CONCUR_UPDATABLE, then holdability is is enforced as CLOSE_CURSORS_AT_COMMIT.
- Specified by:
getResultSetHoldability
in interfaceDatabaseMetaData
- Returns:
- the default holdability; either
ResultSet.HOLD_CURSORS_OVER_COMMIT
orResultSet.CLOSE_CURSORS_AT_COMMIT
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getDatabaseMajorVersion
Retrieves the major version number of the underlying database.HSQLDB-Specific Information:
Returns the major version
- Specified by:
getDatabaseMajorVersion
in interfaceDatabaseMetaData
- Returns:
- the underlying database's major version
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getDatabaseMinorVersion
Retrieves the minor version number of the underlying database.HSQLDB-Specific Information:
This returns the digit after the first point in version.
- Specified by:
getDatabaseMinorVersion
in interfaceDatabaseMetaData
- Returns:
- underlying database's minor version
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getJDBCMajorVersion
Retrieves the major JDBC version number for this driver.HSQLDB-Specific Information:
- Specified by:
getJDBCMajorVersion
in interfaceDatabaseMetaData
- Returns:
- JDBC version major number
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getJDBCMinorVersion
Retrieves the minor JDBC version number for this driver.HSQLDB-Specific Information:
- Specified by:
getJDBCMinorVersion
in interfaceDatabaseMetaData
- Returns:
- JDBC version minor number
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getSQLStateType
(JDBC4 modified:) Indicates whether the SQLSTATE returned bySQLException.getSQLState
is X/Open (now known as Open Group) SQL CLI or SQL:2003.HSQLDB-Specific Information:
HSQLDB returns
sqlStateSQL
under JDBC4 which is equivalent to JDBC3 value of sqlStateSQL99.- Specified by:
getSQLStateType
in interfaceDatabaseMetaData
- Returns:
- the type of SQLSTATE; one of:
sqlStateXOpen or
sqlStateSQL
sqlStateSQL is new in JDBC4 and its value is the same as JDBC3 sqlStateSQL99
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
locatorsUpdateCopy
Indicates whether updates made to a LOB are made on a copy or directly to the LOB.HSQLDB-Specific Information:
Updates to a LOB are made directly. This means the lobs in an updatable ResultSet can be updated and the change is applied when the updateRow() method is applied. Lobs created by calling the Connection methods createClob() and createBlob() can be updated. The lob can then be sent to the database in a PreparedStatement with an UPDATE or INSERT SQL statement.
- Specified by:
locatorsUpdateCopy
in interfaceDatabaseMetaData
- Returns:
true
if updates are made to a copy of the LOB;false
if updates are made directly to the LOB- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
supportsStatementPooling
Retrieves whether this database supports statement pooling.HSQLDB-Specific Information:
Starting with 2.0, HSQLDB supports statement pooling when built under JDK 1.6+.
- Specified by:
supportsStatementPooling
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.4, HSQLDB 1.7
-
getRowIdLifetime
Indicates whether or not this data source supports the SQLROWID
type, and if so the lifetime for which aRowId
object remains valid.The returned int values have the following relationship:
so conditional logic such asROWID_UNSUPPORTED < ROWID_VALID_OTHER < ROWID_VALID_TRANSACTION < ROWID_VALID_SESSION < ROWID_VALID_FOREVER
can be used. Valid Forever means valid across all Sessions, and valid for a Session means valid across all its contained Transactions.if (metadata.getRowIdLifetime() > DatabaseMetaData.ROWID_VALID_TRANSACTION)
- Specified by:
getRowIdLifetime
in interfaceDatabaseMetaData
- Returns:
- the status indicating the lifetime of a
RowId
- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
-
getSchemas
Retrieves the schema names available in this database. The results are ordered by JDBC 4.1[TABLE_CATALOG
] andTABLE_SCHEM
.The schema columns are:
- TABLE_SCHEM String
=>
schema name - TABLE_CATALOG String
=>
catalog name (may benull
)
- Specified by:
getSchemas
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database;"" retrieves those without a catalog; null means catalog name should not be used to narrow down the search.schemaPattern
- a schema name; must match the schema name as it is stored in the database; null means schema name should not be used to narrow down the search.- Returns:
- a
ResultSet
object in which each row is a schema description - Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
- See Also:
- TABLE_SCHEM String
-
supportsStoredFunctionsUsingCallSyntax
Retrieves whether this database supports invoking user-defined or vendor functions using the stored procedure escape syntax.- Specified by:
supportsStoredFunctionsUsingCallSyntax
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
-
autoCommitFailureClosesAllResultSets
Retrieves whether aSQLException
while autoCommit istrue
indicates that all open ResultSets are closed, even ones that are holdable. When aSQLException
occurs while autocommit istrue
, it is vendor specific whether the JDBC driver responds with a commit operation, a rollback operation, or by doing neither a commit nor a rollback. A potential result of this difference is in whether or not holdable ResultSets are closed.- Specified by:
autoCommitFailureClosesAllResultSets
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
-
getClientInfoProperties
Retrieves a list of the client info properties that the driver supports. The result set contains the following columns- NAME String
=>
The name of the client info property
- MAX_LEN int
=>
The maximum length of the value for the property
- DEFAULT_VALUE String
=>
The default value of the property
- DESCRIPTION String
=>
A description of the property. This will typically contain information as to where this property is stored in the database.
The
ResultSet
is sorted by the NAME column- Specified by:
getClientInfoProperties
in interfaceDatabaseMetaData
- Returns:
- A
ResultSet
object; each row is a supported client info property - Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
- NAME String
-
getFunctions
public ResultSet getFunctions(String catalog, String schemaPattern, String functionNamePattern) throws SQLException Retrieves a description of the JDBC 4.1[ system and ]user functions available in the given catalog.Only system and user function descriptions matching the schema and function name criteria are returned. They are ordered by
FUNCTION_CAT
,FUNCTION_SCHEM
,FUNCTION_NAME
andSPECIFIC_ NAME
.Each function description has the following columns:
- FUNCTION_CAT String
=>
function catalog (may benull
) - FUNCTION_SCHEM String
=>
function schema (may benull
) - FUNCTION_NAME String
=>
function name. This is the name used to invoke the function - REMARKS String
=>
explanatory comment on the function - FUNCTION_TYPE short
=>
kind of function:- functionResultUnknown - Cannot determine if a return value or table will be returned
- functionNoTable- Does not return a table
- functionReturnsTable - Returns a table
- SPECIFIC_NAME String
=>
the name which uniquely identifies this function within its schema. This is a user specified, or DBMS generated, name that may be different then theFUNCTION_NAME
for example with overload functions
A user may not have permission to execute any of the functions that are returned by
getFunctions
- Specified by:
getFunctions
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchfunctionNamePattern
- a function name pattern; must match the function name as it is stored in the database- Returns:
ResultSet
- each row is a function description- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
- See Also:
- FUNCTION_CAT String
-
getFunctionColumns
public ResultSet getFunctionColumns(String catalog, String schemaPattern, String functionNamePattern, String columnNamePattern) throws SQLException Retrieves a description of the given catalog's system or user function parameters and return type.Only descriptions matching the schema, function and parameter name criteria are returned. They are ordered by
FUNCTION_CAT
,FUNCTION_SCHEM
,FUNCTION_NAME
andSPECIFIC_ NAME
. Within this, the return value, if any, is first. Next are the parameter descriptions in call order. The column descriptions follow in column number order.Each row in the
ResultSet
is a parameter description, column description or return type description with the following fields:- FUNCTION_CAT String
=>
function catalog (may benull
) - FUNCTION_SCHEM String
=>
function schema (may benull
) - FUNCTION_NAME String
=>
function name. This is the name used to invoke the function - COLUMN_NAME String
=>
column/parameter name - COLUMN_TYPE Short
=>
kind of column/parameter:- functionColumnUnknown - nobody knows
- functionColumnIn - IN parameter
- functionColumnInOut - INOUT parameter
- functionColumnOut - OUT parameter
- functionColumnReturn - function return value
- functionColumnResult - Indicates that the parameter or column
is a column in the
ResultSet
- DATA_TYPE int
=>
SQL type from java.sql.Types - TYPE_NAME String
=>
SQL type name, for a UDT type the type name is fully qualified - PRECISION int
=>
precision - LENGTH int
=>
length in bytes of data - SCALE short
=>
scale - null is returned for data types where SCALE is not applicable. - RADIX short
=>
radix - NULLABLE short
=>
can it contain NULL.- functionNoNulls - does not allow NULL values
- functionNullable - allows NULL values
- functionNullableUnknown - nullability unknown
- REMARKS String
=>
comment describing column/parameter - CHAR_OCTET_LENGTH int
=>
the maximum length of binary and character based parameters or columns. For any other datatype the returned value is a NULL - ORDINAL_POSITION int
=>
the ordinal position, starting from 1, for the input and output parameters. A value of 0 is returned if this row describes the function's return value. For result set columns, it is the ordinal position of the column in the result set starting from 1. - IS_NULLABLE String
=>
ISO rules are used to determine the nullability for a parameter or column.- YES --- if the parameter or column can include NULLs
- NO --- if the parameter or column cannot include NULLs
- empty string --- if the nullability for the parameter or column is unknown
- SPECIFIC_NAME String
=>
the name which uniquely identifies this function within its schema. This is a user specified, or DBMS generated, name that may be different then theFUNCTION_NAME
for example with overload functions
The PRECISION column represents the specified column size for the given parameter or column. For numeric data, this is the maximum precision. For character data, this is the length in characters. For datetime datatypes, this is the length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the length in bytes. For the ROWID datatype, this is the length in bytes. Null is returned for data types where the column size is not applicable.
- Specified by:
getFunctionColumns
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchfunctionNamePattern
- a procedure name pattern; must match the function name as it is stored in the databasecolumnNamePattern
- a parameter name pattern; must match the parameter or column name as it is stored in the database- Returns:
ResultSet
- each row describes a user function parameter, column or return type- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.6, HSQLDB 1.9
- See Also:
- FUNCTION_CAT String
-
unwrap
Returns an object that implements the given interface to allow access to non-standard methods, or standard methods not exposed by the proxy. The result may be either the object found to implement the interface or a proxy for that object. If the receiver implements the interface then that is the object. If the receiver is a wrapper and the wrapped object implements the interface then that is the object. Otherwise the object is the result of callingunwrap
recursively on the wrapped object. If the receiver is not a wrapper and does not implement the interface, then anSQLException
is thrown.- Specified by:
unwrap
in interfaceWrapper
- Parameters:
iface
- A Class defining an interface that the result must implement.- Returns:
- an object that implements the interface. May be a proxy for the actual implementing object.
- Throws:
SQLException
- If no object found that implements the interface- Since:
- JDK 1.6, HSQLDB 1.9
-
isWrapperFor
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 callingisWrapperFor
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 tounwrap
so that callers can use this method to avoid expensiveunwrap
calls that may fail. If this method returns true then callingunwrap
with the same argument should succeed.- Specified by:
isWrapperFor
in interfaceWrapper
- Parameters:
iface
- a Class defining an interface.- Returns:
- true if this implements the interface or directly or indirectly wraps an object that does.
- Throws:
SQLException
- if an error occurs while determining whether this is a wrapper for an object with the given interface.- Since:
- JDK 1.6, HSQLDB 1.9
-
getPseudoColumns
public ResultSet getPseudoColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern) throws SQLException Retrieves a description of the pseudo or hidden columns available in a given table within the specified catalog and schema. Pseudo or hidden columns may not always be stored within a table and are not visible in a ResultSet unless they are specified in the query's outermost SELECT list. Pseudo or hidden columns may not necessarily be able to be modified. If there are no pseudo or hidden columns, an empty ResultSet is returned.Only column descriptions matching the catalog, schema, table and column name criteria are returned. They are ordered by
TABLE_CAT
,TABLE_SCHEM
,TABLE_NAME
andCOLUMN_NAME
.Each column description has the following columns:
- TABLE_CAT String
=>
table catalog (may benull
) - TABLE_SCHEM String
=>
table schema (may benull
) - TABLE_NAME String
=>
table name - COLUMN_NAME String
=>
column name - DATA_TYPE int
=>
SQL type from java.sql.Types - COLUMN_SIZE int
=>
column size. - DECIMAL_DIGITS int
=>
the number of fractional digits. Null is returned for data types where DECIMAL_DIGITS is not applicable. - NUM_PREC_RADIX int
=>
Radix (typically either 10 or 2) - COLUMN_USAGE String
=>
The allowed usage for the column. The value returned will correspond to the enum name returned byPseudoColumnUsage.name()
- REMARKS String
=>
comment describing column (may benull
) - CHAR_OCTET_LENGTH int
=>
for char types the maximum number of bytes in the column - IS_NULLABLE String
=>
ISO rules are used to determine the nullability for a column.- YES --- if the column can include NULLs
- NO --- if the column cannot include NULLs
- empty string --- if the nullability for the column is unknown
The COLUMN_SIZE column specifies the column size for the given column. For numeric data, this is the maximum precision. For character data, this is the length in characters. For datetime datatypes, this is the length in characters of the String representation (assuming the maximum allowed precision of the fractional seconds component). For binary data, this is the length in bytes. For the ROWID datatype, this is the length in bytes. Null is returned for data types where the column size is not applicable.
- Specified by:
getPseudoColumns
in interfaceDatabaseMetaData
- Parameters:
catalog
- a catalog name; must match the catalog name as it is stored in the database; "" retrieves those without a catalog;null
means that the catalog name should not be used to narrow the searchschemaPattern
- a schema name pattern; must match the schema name as it is stored in the database; "" retrieves those without a schema;null
means that the schema name should not be used to narrow the searchtableNamePattern
- a table name pattern; must match the table name as it is stored in the databasecolumnNamePattern
- a column name pattern; must match the column name as it is stored in the database- Returns:
ResultSet
- each row is a column description- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.7 M11 2010/09/10 (b123), HSQLDB 2.0.1
- See Also:
- TABLE_CAT String
-
generatedKeyAlwaysReturned
Retrieves whether a generated key will always be returned if the column name(s) or index(es) specified for the auto generated key column(s) are valid and the statement succeeds. The key that is returned may or may not be based on the column(s) for the auto generated key. Consult your JDBC driver documentation for additional details.- Specified by:
generatedKeyAlwaysReturned
in interfaceDatabaseMetaData
- Returns:
true
if so;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- JDK 1.7 M11 2010/09/10 (b123), HSQLDB 2.0.1
-
getMaxLogicalLobSize
Retrieves the maximum number of bytes this database allows for the logical size for aLOB
.- Specified by:
getMaxLogicalLobSize
in interfaceDatabaseMetaData
- Returns:
- the maximum number of bytes allowed; a result of zero means that there is no limit or the limit is not known
- Throws:
SQLException
- if a database access error occurs- Since:
- 1.8
-
supportsRefCursors
Retrieves whether this database supports REF CURSOR.- Specified by:
supportsRefCursors
in interfaceDatabaseMetaData
- Returns:
true
if this database supports REF CURSOR;false
otherwise- Throws:
SQLException
- if a database access error occurs- Since:
- 1.8
-
getDatabaseDefaultCollation
Returns the name of the default collation for database.- Returns:
- name of collation
-