DatabaseMetaData (C-JDBC 1.1 API)

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

org.objectweb.cjdbc.driver
Class DatabaseMetaData

java.lang.Object
  org.objectweb.cjdbc.driver.DatabaseMetaData

All Implemented Interfaces:: java.sql.DatabaseMetaData

public class DatabaseMetaData
extends java.lang.Object
implements java.sql.DatabaseMetaData

This Connection class implements a virtual connection that is just used to store the needed information when the real connection will have to be established by the Controller to execute a query.

This code has been largely inspired from the Postgres JDBC driver by Peter T. Mount.

Version:: 1.0
Author:: Emmanuel Cecchet

Field Summary
`private Connection`	`connection` The connection association

Fields inherited from interface java.sql.DatabaseMetaData

attributeNoNulls, attributeNullable, attributeNullableUnknown, bestRowNotPseudo, bestRowPseudo, bestRowSession, bestRowTemporary, bestRowTransaction, bestRowUnknown, columnNoNulls, columnNullable, columnNullableUnknown, importedKeyCascade, importedKeyInitiallyDeferred, importedKeyInitiallyImmediate, importedKeyNoAction, importedKeyNotDeferrable, importedKeyRestrict, importedKeySetDefault, importedKeySetNull, procedureColumnIn, procedureColumnInOut, procedureColumnOut, procedureColumnResult, procedureColumnReturn, procedureColumnUnknown, procedureNoNulls, procedureNoResult, procedureNullable, procedureNullableUnknown, procedureResultUnknown, procedureReturnsResult, sqlStateSQL99, sqlStateXOpen, tableIndexClustered, tableIndexHashed, tableIndexOther, tableIndexStatistic, typeNoNulls, typeNullable, typeNullableUnknown, typePredBasic, typePredChar, typePredNone, typeSearchable, versionColumnNotPseudo, versionColumnPseudo, versionColumnUnknown

Constructor Summary
`DatabaseMetaData(Connection conn)` Creates a new `DatabaseMetaData` instance.

Method Summary
`boolean`	`allProceduresAreCallable()` Can all the procedures returned by `getProcedures` be called by the current user?
`boolean`	`allTablesAreSelectable()` Can all the tables returned by `getTable` be SELECTed by the current user?
`boolean`	`dataDefinitionCausesTransactionCommit()` Does a data definition statement within a transaction force the transaction to commit?
`boolean`	`dataDefinitionIgnoredInTransactions()` Is a data definition statement within a transaction ignored?
`boolean`	`deletesAreDetected(int type)` C-JDBC does NOT support deleted rows.
`boolean`	`doesMaxRowSizeIncludeBlobs()` Did `getMaxRowSize()` include LONGVARCHAR and LONGVARBINARY blobs?
`java.sql.ResultSet`	`getAttributes(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String typeNamePattern, java.lang.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.
`java.sql.ResultSet`	`getBestRowIdentifier(java.lang.String catalog, java.lang.String schema, java.lang.String table, int scope, boolean nullable)` This method is currently not supported and returns `null`.
`java.sql.ResultSet`	`getCatalogs()` Return a list of available catalogs
`java.lang.String`	`getCatalogSeparator()` Returns the catalog separator.
`java.lang.String`	`getCatalogTerm()` What is the database vendor's preferred term for "schema" - well, we do not provide support for schemas, so lets just use that term.
`java.sql.ResultSet`	`getColumnPrivileges(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String tableNamePattern, java.lang.String columnNamePattern)` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getColumns(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String tableNamePattern, java.lang.String columnNamePattern)`
`java.sql.Connection`	`getConnection()` Retrieves the `Connection` that produced this `DatabaseMetaData`.
`java.sql.ResultSet`	`getCrossReference(java.lang.String primaryCatalog, java.lang.String primarySchema, java.lang.String primaryTable, java.lang.String foreignCatalog, java.lang.String foreignSchema, java.lang.String foreignTable)` Feature not yet supported by C-JDBC
`int`	`getDatabaseMajorVersion()` Retrieves the major version number of the underlying database.
`int`	`getDatabaseMinorVersion()` Retrieves the minor version number of the underlying database.
`java.lang.String`	`getDatabaseProductName()` We return a comma separated list of database engine names connected to the controller.
`java.lang.String`	`getDatabaseProductVersion()` What is the version of this database product.
`int`	`getDefaultTransactionIsolation()` What is the database's default transaction isolation level?
`int`	`getDriverMajorVersion()` What is this JDBC driver's major version number?
`int`	`getDriverMinorVersion()` What is this JDBC driver's minor version number?
`java.lang.String`	`getDriverName()` What is the name of this JDBC driver?
`java.lang.String`	`getDriverVersion()` What is the version string of this JDBC driver?
`java.sql.ResultSet`	`getExportedKeys(java.lang.String catalog, java.lang.String schema, java.lang.String table)` Feature not yet supported by C-JDBC.
`java.lang.String`	`getExtraNameCharacters()` Gets all the "extra" characters that can be used in unquoted identifier names (those beyond a-zA-Z0-9 and _).
`java.lang.String`	`getIdentifierQuoteString()` What is the string used to quote SQL identifiers?
`java.sql.ResultSet`	`getImportedKeys(java.lang.String catalog, java.lang.String schema, java.lang.String table)` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getIndexInfo(java.lang.String catalog, java.lang.String schema, java.lang.String table, boolean unique, boolean approximate)` Feature not yet supported by C-JDBC.
`int`	`getJDBCMajorVersion()` Retrieves the major JDBC version number for this driver.
`int`	`getJDBCMinorVersion()` Retrieves the minor JDBC version number for this driver.
`int`	`getMaxBinaryLiteralLength()` How many hex characters can you have in an inline binary literal.
`int`	`getMaxCatalogNameLength()` Maximum number of characters in a catalog name.
`int`	`getMaxCharLiteralLength()` Maximum length for a character literal.
`int`	`getMaxColumnNameLength()` Maximum length for a column name.
`int`	`getMaxColumnsInGroupBy()` Maximum number of columns in a "GROUP BY" clause?
`int`	`getMaxColumnsInIndex()` Maximum number of columns allowed in an index?
`int`	`getMaxColumnsInOrderBy()` Maximum number of columns in an "ORDER BY clause?
`int`	`getMaxColumnsInSelect()` Maximum number of columns in a "SELECT" list?
`int`	`getMaxColumnsInTable()` Maximum number of columns in a table?
`int`	`getMaxConnections()` Maximum number of connections to the database (virtually no limit since these are virtual connections to the Controller).
`int`	`getMaxCursorNameLength()` Maximum cursor name length.
`int`	`getMaxIndexLength()` Maximum length of an index (in bytes)?
`int`	`getMaxProcedureNameLength()` Maximum length of a procedure name?
`int`	`getMaxRowSize()` Maximum length of a single row?
`int`	`getMaxSchemaNameLength()` Maximum length of a schema name.
`int`	`getMaxStatementLength()` Maximum length of a SQL statement?
`int`	`getMaxStatements()` How many active statements can we have open at one time to this database?
`int`	`getMaxTableNameLength()` Maximum length of a table name?
`int`	`getMaxTablesInSelect()` Maximum number of tables that can be specified in a SELECT.
`int`	`getMaxUserNameLength()` Maximum length of a user name.
`java.lang.String`	`getNumericFunctions()` Name of Open Group CLI is not supported.
`java.sql.ResultSet`	`getPrimaryKeys(java.lang.String catalog, java.lang.String schema, java.lang.String table)`
`java.sql.ResultSet`	`getProcedureColumns(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String procedureNamePattern, java.lang.String columnNamePattern)`
`java.sql.ResultSet`	`getProcedures(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String procedureNamePattern)`
`java.lang.String`	`getProcedureTerm()` What is the database vendor's preferred term for "procedure" - I kind of like "procedure" myself.
`int`	`getResultSetHoldability()` Retrieves the default holdability of this `ResultSet` object.
`java.sql.ResultSet`	`getSchemas()`
`java.lang.String`	`getSchemaTerm()` What is the database vendor's preferred term for "schema" - well, we do not provide support for schemas, so lets just use that term.
`java.lang.String`	`getSearchStringEscape()` This is the string that can be used to escape '_' and '%' in a search string pattern style catalog search parameters.
`java.lang.String`	`getSQLKeywords()` Get a comma separated list of all a database's SQL keywords that are NOT also SQL92 keywords.
`int`	`getSQLStateType()` Indicates whether the SQLSTATE returned by `SQLException.getSQLState` is X/Open (now known as Open Group) SQL CLI or SQL99.
`java.lang.String`	`getStringFunctions()` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getSuperTables(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String tableNamePattern)` Retrieves a description of the table hierarchies defined in a particular schema in this database.
`java.sql.ResultSet`	`getSuperTypes(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String typeNamePattern)` Retrieves a description of the user-defined type (UDT) hierarchies defined in a particular schema in this database.
`java.lang.String`	`getSystemFunctions()` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getTablePrivileges(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String tableNamePattern)` Gets a description of the access rights for each table available in a catalog.
`java.sql.ResultSet`	`getTables(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String tableNamePattern, java.lang.String[] types)` Gets a description of the available tables.
`java.sql.ResultSet`	`getTableTypes()` Gets the table types available in this database.
`java.lang.String`	`getTimeDateFunctions()` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getTypeInfo()` Feature not yet supported by C-JDBC.
`java.sql.ResultSet`	`getUDTs(java.lang.String catalog, java.lang.String schemaPattern, java.lang.String typeNamePattern, int[] types)` Feature not yet supported by C-JDBC.
`java.lang.String`	`getURL()` What is the URL for this database?
`java.lang.String`	`getUserName()` What is our user name as known to the database?
`java.sql.ResultSet`	`getVersionColumns(java.lang.String catalog, java.lang.String schema, java.lang.String table)` Feature not yet supported by C-JDBC.
`boolean`	`insertsAreDetected(int type)` We do not support row insert in `ResultSets`.
`boolean`	`isCatalogAtStart()` Does a catalog appear at the start of a qualified table name?
`boolean`	`isReadOnly()` Is the database in read-only mode?
`boolean`	`locatorsUpdateCopy()` Indicates whether updates made to a LOB are made on a copy or directly to the LOB.
`boolean`	`nullPlusNonNullIsNull()` Are concatenations between NULL and non-NULL values NULL?
`boolean`	`nullsAreSortedAtEnd()` Are NULL values sorted at the end regardless of sort order?
`boolean`	`nullsAreSortedAtStart()` Are NULL values sorted at the start regardless of sort order?
`boolean`	`nullsAreSortedHigh()` Are NULL values sorted high?
`boolean`	`nullsAreSortedLow()` Are NULL values sorted low?
`boolean`	`othersDeletesAreVisible(int type)` C-JDBC does not support deletes.
`boolean`	`othersInsertsAreVisible(int type)` C-JDBC does not support inserts.
`boolean`	`othersUpdatesAreVisible(int type)` C-JDBC does not support updates.
`boolean`	`ownDeletesAreVisible(int type)` C-JDBC does not support deletes.
`boolean`	`ownInsertsAreVisible(int type)` C-JDBC does not support inserts.
`boolean`	`ownUpdatesAreVisible(int type)` C-JDBC does not support updates.
`boolean`	`storesLowerCaseIdentifiers()` Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in lower case?
`boolean`	`storesLowerCaseQuotedIdentifiers()` Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in lower case?
`boolean`	`storesMixedCaseIdentifiers()` Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in mixed case?
`boolean`	`storesMixedCaseQuotedIdentifiers()` Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in mixed case?
`boolean`	`storesUpperCaseIdentifiers()` Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in upper case?
`boolean`	`storesUpperCaseQuotedIdentifiers()` Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in upper case?
`boolean`	`supportsAlterTableWithAddColumn()` Not implemented (returns `false`).
`boolean`	`supportsAlterTableWithDropColumn()` Not implemented (returns `false`).
`boolean`	`supportsANSI92EntryLevelSQL()` Does this driver support the ANSI-92 entry level SQL grammar?
`boolean`	`supportsANSI92FullSQL()` Does this driver support the ANSI-92 full SQL grammar?
`boolean`	`supportsANSI92IntermediateSQL()` Does this driver support the ANSI-92 intermediate level SQL grammar?
`boolean`	`supportsBatchUpdates()` Does this driver support batch updates ?
`boolean`	`supportsCatalogsInDataManipulation()` Can a catalog name be used in a data manipulation statement?
`boolean`	`supportsCatalogsInIndexDefinitions()` Can a catalog name be used in an index definition?
`boolean`	`supportsCatalogsInPrivilegeDefinitions()` Can a catalog name be used in a privilege definition statement?
`boolean`	`supportsCatalogsInProcedureCalls()` Can a catalog name be used in a procedure call statement?
`boolean`	`supportsCatalogsInTableDefinitions()` Can a catalog name be used in a table definition statement?
`boolean`	`supportsColumnAliasing()` Is column aliasing supported?
`boolean`	`supportsConvert()` Not implemented (returns `false`).
`boolean`	`supportsConvert(int fromType, int toType)` Not implemented (returns `false`).
`boolean`	`supportsCoreSQLGrammar()` Does this driver support the Core ODBC SQL grammar.
`boolean`	`supportsCorrelatedSubqueries()` Not implemented (returns `false`).
`boolean`	`supportsDataDefinitionAndDataManipulationTransactions()` Are both data definition and data manipulation transactions supported?
`boolean`	`supportsDataManipulationTransactionsOnly()` Are only data manipulation statements within a transaction supported?
`boolean`	`supportsDifferentTableCorrelationNames()` Not implemented (returns `false`).
`boolean`	`supportsExpressionsInOrderBy()` Not implemented (returns `false`).
`boolean`	`supportsExtendedSQLGrammar()` Does this driver support the Extended (Level 2) ODBC SQL grammar.
`boolean`	`supportsFullOuterJoins()` Not implemented (returns `false`).
`boolean`	`supportsGetGeneratedKeys()` Retrieves whether auto-generated keys can be retrieved after a statement has been executed.
`boolean`	`supportsGroupBy()` Is some form of "GROUP BY" clause supported?
`boolean`	`supportsGroupByBeyondSelect()` Can a "GROUP BY" clause add columns not in the SELECT provided it specifies all the columns in the SELECT?
`boolean`	`supportsGroupByUnrelated()` Can a "GROUP BY" clause use columns not in the SELECT?
`boolean`	`supportsIntegrityEnhancementFacility()` Is the SQL Integrity Enhancement Facility supported?
`boolean`	`supportsLikeEscapeClause()` Is the escape character in "LIKE" clauses supported?
`boolean`	`supportsLimitedOuterJoins()` Is there limited support for outer joins?
`boolean`	`supportsMinimumSQLGrammar()` Does this driver support the minimum ODBC SQL grammar.
`boolean`	`supportsMixedCaseIdentifiers()` Does the database treat mixed case unquoted SQL identifiers as case sensitive and as a result store them in mixed case?
`boolean`	`supportsMixedCaseQuotedIdentifiers()` Does the database treat mixed case quoted SQL identifiers as case sensitive and as a result store them in mixed case?
`boolean`	`supportsMultipleOpenResults()` Retrieves whether it is possible to have multiple `ResultSet` objects returned from a `CallableStatement` object simultaneously.
`boolean`	`supportsMultipleResultSets()` Are multiple `ResultSets` from a single execute supported?
`boolean`	`supportsMultipleTransactions()` Can we have multiple transactions open at once (on different connections?).
`boolean`	`supportsNamedParameters()` Retrieves whether this database supports named parameters to callable statements.
`boolean`	`supportsNonNullableColumns()` Can columns be defined as non-nullable.
`boolean`	`supportsOpenCursorsAcrossCommit()` Does this database support having cursors remain open across commits.
`boolean`	`supportsOpenCursorsAcrossRollback()` Do we support open cursors across rollback ?
`boolean`	`supportsOpenStatementsAcrossCommit()` Can statements remain open across commits?
`boolean`	`supportsOpenStatementsAcrossRollback()` Can statements remain open across rollbacks?
`boolean`	`supportsOrderByUnrelated()` Can an "ORDER BY" clause use columns not in the SELECT?
`boolean`	`supportsOuterJoins()` Is some form of outer join supported?
`boolean`	`supportsPositionedDelete()` We support cursors for gets only it seems.
`boolean`	`supportsPositionedUpdate()` Is positioned UPDATE supported?
`boolean`	`supportsResultSetConcurrency(int type, int concurrency)` Which combination of concurrency level and `ResultSet` type is supported ?
`boolean`	`supportsResultSetHoldability(int holdability)` Retrieves whether this database supports the given result set holdability.
`boolean`	`supportsResultSetType(int type)` Supported `ResultSet` types.
`boolean`	`supportsSavepoints()` Retrieves whether this database supports savepoints.
`boolean`	`supportsSchemasInDataManipulation()` Can a schema name be used in a data manipulation statement?
`boolean`	`supportsSchemasInIndexDefinitions()` Can a schema name be used in an index definition statement?
`boolean`	`supportsSchemasInPrivilegeDefinitions()` Can a schema name be used in a privilege definition statement?
`boolean`	`supportsSchemasInProcedureCalls()` Can a schema name be used in a procedure call statement?
`boolean`	`supportsSchemasInTableDefinitions()` Can a schema be used in a table definition statement?
`boolean`	`supportsSelectForUpdate()` Not implemented (returns `false`).
`boolean`	`supportsStatementPooling()` Retrieves whether this database supports statement pooling.
`boolean`	`supportsStoredProcedures()` Yes, stored procedures are supported since 1.0b6.
`boolean`	`supportsSubqueriesInComparisons()` Not implemented (returns `false`).
`boolean`	`supportsSubqueriesInExists()` Not implemented (returns `false`).
`boolean`	`supportsSubqueriesInIns()` Not implemented (returns `false`).
`boolean`	`supportsSubqueriesInQuantifieds()` Not implemented (returns `false`).
`boolean`	`supportsTableCorrelationNames()` Not implemented (returns `false`).
`boolean`	`supportsTransactionIsolationLevel(int level)` Does the database support the given transaction isolation level?
`boolean`	`supportsTransactions()` Are transactions supported?
`boolean`	`supportsUnion()` Is SQL UNION supported?
`boolean`	`supportsUnionAll()` Is SQL UNION ALL supported?
`boolean`	`updatesAreDetected(int type)` Not implemented (returns `false`).
`boolean`	`usesLocalFilePerTable()` Does the database use a file for each table?
`boolean`	`usesLocalFiles()` Does the database store tables in a local file?

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

connection

private Connection connection

The connection association

Constructor Detail

DatabaseMetaData

public DatabaseMetaData(Connection conn)

Creates a new DatabaseMetaData instance.
Parameters:: conn - a Connection value

Method Detail

allProceduresAreCallable

public boolean allProceduresAreCallable()
                                 throws java.sql.SQLException

Can all the procedures returned by getProcedures be called by the current user?

Specified by:: allProceduresAreCallable in interface java.sql.DatabaseMetaData

Returns:: true but we don't support catalogs ...
Throws:: java.sql.SQLException - if a database access error occurs

allTablesAreSelectable

public boolean allTablesAreSelectable()
                               throws java.sql.SQLException

Can all the tables returned by getTable be SELECTed by the current user?

Specified by:: allTablesAreSelectable in interface java.sql.DatabaseMetaData

Returns:: true but we don't support catalogs ...
Throws:: java.sql.SQLException - if a database access error occurs

dataDefinitionCausesTransactionCommit

public boolean dataDefinitionCausesTransactionCommit()
                                              throws java.sql.SQLException

Does a data definition statement within a transaction force the transaction to commit? I think this means something like:

  CREATE TABLE T (A INT); INSERT INTO T (A) VALUES (2); BEGIN; UPDATE T SET A = A + 1; CREATE TABLE X (A INT); SELECT A FROM T INTO X; COMMIT;

does the CREATE TABLE call cause a commit? The answer is no.

Specified by:: dataDefinitionCausesTransactionCommit in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

dataDefinitionIgnoredInTransactions

public boolean dataDefinitionIgnoredInTransactions()
                                            throws java.sql.SQLException

Is a data definition statement within a transaction ignored? It seems to be (from experiment in previous method).

Specified by:: dataDefinitionIgnoredInTransactions in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

deletesAreDetected

public boolean deletesAreDetected(int type)
                           throws java.sql.SQLException

C-JDBC does NOT support deleted rows.

Specified by:: deletesAreDetected in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException - if an error occurs

doesMaxRowSizeIncludeBlobs

public boolean doesMaxRowSizeIncludeBlobs()
                                   throws java.sql.SQLException

Did getMaxRowSize() include LONGVARCHAR and LONGVARBINARY blobs? We don't handle blobs yet.

Specified by:: doesMaxRowSizeIncludeBlobs in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

getBestRowIdentifier

public java.sql.ResultSet getBestRowIdentifier(java.lang.String catalog,
                                               java.lang.String schema,
                                               java.lang.String table,
                                               int scope,
                                               boolean nullable)
                                        throws java.sql.SQLException

This method is currently not supported and returns null. It could be forwarded to the Controller but it is not clear that the result would be the same for heterogeneous databases.

Specified by:: getBestRowIdentifier in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name; "" retrieves those without a schema; table - a table name; scope - the scope of interest; use same values as SCOPE; nullable - include columns that are nullable?
Returns:: ResultSet each row is a column description
Throws:: java.sql.SQLException - if an error occurs

getCatalogs

public java.sql.ResultSet getCatalogs()
                               throws java.sql.SQLException

Return a list of available catalogs

Specified by:: getCatalogs in interface java.sql.DatabaseMetaData

Returns:: ResultSet, each row is a name of catalog.
Throws:: java.sql.SQLException - if an error occurs
See Also:: DatabaseMetaData.getCatalogs()

getCatalogSeparator

public java.lang.String getCatalogSeparator()
                                     throws java.sql.SQLException

Returns the catalog separator.

Specified by:: getCatalogSeparator in interface java.sql.DatabaseMetaData

Returns:: "."
Throws:: java.sql.SQLException - if an error occurs

getCatalogTerm

public java.lang.String getCatalogTerm()
                                throws java.sql.SQLException

What is the database vendor's preferred term for "schema" - well, we do not provide support for schemas, so lets just use that term.

Specified by:: getCatalogTerm in interface java.sql.DatabaseMetaData

Returns:: the vendor term
Throws:: java.sql.SQLException - if an error occurs

getColumns

public java.sql.ResultSet getColumns(java.lang.String catalog,
                                     java.lang.String schemaPattern,
                                     java.lang.String tableNamePattern,
                                     java.lang.String columnNamePattern)
                              throws java.sql.SQLException

Specified by:: getColumns in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schemaPattern - a schema name pattern; "" retrieves those without a schema; tableNamePattern - a table name pattern; columnNamePattern - a column name pattern
Returns:: null
Throws:: java.sql.SQLException - if an error occurs
See Also:: getSearchStringEscape()

getColumnPrivileges

public java.sql.ResultSet getColumnPrivileges(java.lang.String catalog,
                                              java.lang.String schemaPattern,
                                              java.lang.String tableNamePattern,
                                              java.lang.String columnNamePattern)
                                       throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getColumnPrivileges in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schemaPattern - a schema name pattern; "" retrieves those without a schema; tableNamePattern - a table name pattern; columnNamePattern - a column name pattern
Returns:: null
Throws:: java.sql.SQLException - if an error occurs
See Also:: getSearchStringEscape()

getConnection

public java.sql.Connection getConnection()
                                  throws java.sql.SQLException

Retrieves the Connection that produced this DatabaseMetaData.

Specified by:: getConnection in interface java.sql.DatabaseMetaData

Returns:: the Connection object
Throws:: java.sql.SQLException - if an error occurs

getCrossReference

public java.sql.ResultSet getCrossReference(java.lang.String primaryCatalog,
                                            java.lang.String primarySchema,
                                            java.lang.String primaryTable,
                                            java.lang.String foreignCatalog,
                                            java.lang.String foreignSchema,
                                            java.lang.String foreignTable)
                                     throws java.sql.SQLException

Feature not yet supported by C-JDBC

Specified by:: getCrossReference in interface java.sql.DatabaseMetaData

Parameters:: primaryCatalog - a String value; primarySchema - a String value; primaryTable - a String value; foreignCatalog - a String value; foreignSchema - a String value; foreignTable - a String value
Returns:: null
Throws:: java.sql.SQLException - if an error occurs
See Also:: getImportedKeys(java.lang.String, java.lang.String, java.lang.String)

getDatabaseProductName

public java.lang.String getDatabaseProductName()
                                        throws java.sql.SQLException

We return a comma separated list of database engine names connected to the controller. A name appears only once regardless of the number of instances of this particular db engine. If no database product name is provided by the backend drivers, default is to return "C-JDBC Controller".

Specified by:: getDatabaseProductName in interface java.sql.DatabaseMetaData

Returns:: comma separated list of database product names
Throws:: java.sql.SQLException - if a database access error occurs

getDatabaseProductVersion

public java.lang.String getDatabaseProductVersion()
                                           throws java.sql.SQLException

What is the version of this database product.

Specified by:: getDatabaseProductVersion in interface java.sql.DatabaseMetaData

Returns:: the C-JDBC driver version
Throws:: java.sql.SQLException - if an error occurs

getDefaultTransactionIsolation

public int getDefaultTransactionIsolation()
                                   throws java.sql.SQLException

What is the database's default transaction isolation level? We do not support this, so assume it's TRANSACTION_READ_COMMITTED.

Specified by:: getDefaultTransactionIsolation in interface java.sql.DatabaseMetaData

Returns:: the default isolation level
Throws:: java.sql.SQLException - if a database access error occurs
See Also:: Connection

getDriverMajorVersion

public int getDriverMajorVersion()

What is this JDBC driver's major version number?

Specified by:: getDriverMajorVersion in interface java.sql.DatabaseMetaData

Returns:: the JDBC driver major version

getDriverMinorVersion

public int getDriverMinorVersion()

What is this JDBC driver's minor version number?

Specified by:: getDriverMinorVersion in interface java.sql.DatabaseMetaData

Returns:: the JDBC driver minor version

getDriverName

public java.lang.String getDriverName()
                               throws java.sql.SQLException

What is the name of this JDBC driver?

Specified by:: getDriverName in interface java.sql.DatabaseMetaData

Returns:: the JDBC driver name
Throws:: java.sql.SQLException - why?

getDriverVersion

public java.lang.String getDriverVersion()
                                  throws java.sql.SQLException

What is the version string of this JDBC driver?

Specified by:: getDriverVersion in interface java.sql.DatabaseMetaData

Returns:: the JDBC driver name.
Throws:: java.sql.SQLException - why?

getExportedKeys

public java.sql.ResultSet getExportedKeys(java.lang.String catalog,
                                          java.lang.String schema,
                                          java.lang.String table)
                                   throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getExportedKeys in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name pattern; "" retrieves those without a schema; table - a table name
Returns:: null
Throws:: java.sql.SQLException - why?
See Also:: getExportedKeys(java.lang.String, java.lang.String, java.lang.String)

getExtraNameCharacters

public java.lang.String getExtraNameCharacters()
                                        throws java.sql.SQLException

Gets all the "extra" characters that can be used in unquoted identifier names (those beyond a-zA-Z0-9 and _).

For portability reasons, we assume that no extra character is allowed.

Specified by:: getExtraNameCharacters in interface java.sql.DatabaseMetaData

Returns:: a string containing the extra characters
Throws:: java.sql.SQLException - if a database access error occurs

getIdentifierQuoteString

public java.lang.String getIdentifierQuoteString()
                                          throws java.sql.SQLException

What is the string used to quote SQL identifiers? This returns a space if identifier quoting isn't supported. A JDBC Compliant driver will always use a double quote character.

If an SQL identifier is a table name, column name, etc. then we do not support it.

Specified by:: getIdentifierQuoteString in interface java.sql.DatabaseMetaData

Returns:: a space
Throws:: java.sql.SQLException - if a database access error occurs

getImportedKeys

public java.sql.ResultSet getImportedKeys(java.lang.String catalog,
                                          java.lang.String schema,
                                          java.lang.String table)
                                   throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getImportedKeys in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name pattern; "" retrieves those without a schema; table - a table name
Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs
See Also:: getExportedKeys(java.lang.String, java.lang.String, java.lang.String)

getIndexInfo

public java.sql.ResultSet getIndexInfo(java.lang.String catalog,
                                       java.lang.String schema,
                                       java.lang.String table,
                                       boolean unique,
                                       boolean approximate)
                                throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getIndexInfo in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name pattern; "" retrieves those without a schema; table - a table name; unique - when true, return only indices for unique values; when false, return indices regardless of whether unique or not; approximate - when true, result is allowed to reflect approximate or out of data values; when false, results are requested to be accurate
Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getMaxBinaryLiteralLength

public int getMaxBinaryLiteralLength()
                              throws java.sql.SQLException

How many hex characters can you have in an inline binary literal. The spec says 0 should be returned if unknown.

Specified by:: getMaxBinaryLiteralLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxCatalogNameLength

public int getMaxCatalogNameLength()
                            throws java.sql.SQLException

Maximum number of characters in a catalog name. The spec says 0 should be returned if unknown.

Specified by:: getMaxCatalogNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxCharLiteralLength

public int getMaxCharLiteralLength()
                            throws java.sql.SQLException

Maximum length for a character literal. The spec says 0 should be returned if unknown.

Specified by:: getMaxCharLiteralLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnNameLength

public int getMaxColumnNameLength()
                           throws java.sql.SQLException

Maximum length for a column name. The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnsInGroupBy

public int getMaxColumnsInGroupBy()
                           throws java.sql.SQLException

Maximum number of columns in a "GROUP BY" clause? The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnsInGroupBy in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnsInIndex

public int getMaxColumnsInIndex()
                         throws java.sql.SQLException

Maximum number of columns allowed in an index? The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnsInIndex in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnsInOrderBy

public int getMaxColumnsInOrderBy()
                           throws java.sql.SQLException

Maximum number of columns in an "ORDER BY clause? The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnsInOrderBy in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnsInSelect

public int getMaxColumnsInSelect()
                          throws java.sql.SQLException

Maximum number of columns in a "SELECT" list? The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnsInSelect in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxColumnsInTable

public int getMaxColumnsInTable()
                         throws java.sql.SQLException

Maximum number of columns in a table? The spec says 0 should be returned if unknown.

Specified by:: getMaxColumnsInTable in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxConnections

public int getMaxConnections()
                      throws java.sql.SQLException

Maximum number of connections to the database (virtually no limit since these are virtual connections to the Controller). The spec says 0 should be returned if unknown.

Specified by:: getMaxConnections in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxCursorNameLength

public int getMaxCursorNameLength()
                           throws java.sql.SQLException

Maximum cursor name length. The spec says 0 should be returned if unknown.

Specified by:: getMaxCursorNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxIndexLength

public int getMaxIndexLength()
                      throws java.sql.SQLException

Maximum length of an index (in bytes)? The spec says 0 should be returned if unknown.

Specified by:: getMaxIndexLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxProcedureNameLength

public int getMaxProcedureNameLength()
                              throws java.sql.SQLException

Maximum length of a procedure name? The spec says 0 should be returned if unknown.

Specified by:: getMaxProcedureNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxRowSize

public int getMaxRowSize()
                  throws java.sql.SQLException

Maximum length of a single row? (not including blobs). The spec says 0 should be returned if unknown.

Specified by:: getMaxRowSize in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxSchemaNameLength

public int getMaxSchemaNameLength()
                           throws java.sql.SQLException

Maximum length of a schema name. The spec says 0 should be returned if unknown.

Specified by:: getMaxSchemaNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxStatementLength

public int getMaxStatementLength()
                          throws java.sql.SQLException

Maximum length of a SQL statement? The spec says 0 should be returned if unknown.

Specified by:: getMaxStatementLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxStatements

public int getMaxStatements()
                     throws java.sql.SQLException

How many active statements can we have open at one time to this database? Basically, since each Statement downloads the results as the query is executed, we can have many. The spec says 0 should be returned if no limit or unknown.

Specified by:: getMaxStatements in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxTableNameLength

public int getMaxTableNameLength()
                          throws java.sql.SQLException

Maximum length of a table name? The spec says 0 should be returned if unknown.

Specified by:: getMaxTableNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxTablesInSelect

public int getMaxTablesInSelect()
                         throws java.sql.SQLException

Maximum number of tables that can be specified in a SELECT. The spec says 0 should be returned if unknown.

Specified by:: getMaxTablesInSelect in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getMaxUserNameLength

public int getMaxUserNameLength()
                         throws java.sql.SQLException

Maximum length of a user name. The spec says 0 should be returned if unknown.

Specified by:: getMaxUserNameLength in interface java.sql.DatabaseMetaData

Returns:: 0
Throws:: java.sql.SQLException - if a database access error occurs

getNumericFunctions

public java.lang.String getNumericFunctions()
                                     throws java.sql.SQLException

Name of Open Group CLI is not supported.

Specified by:: getNumericFunctions in interface java.sql.DatabaseMetaData

Returns:: null
Throws:: java.sql.SQLException - never

getPrimaryKeys

public java.sql.ResultSet getPrimaryKeys(java.lang.String catalog,
                                         java.lang.String schema,
                                         java.lang.String table)
                                  throws java.sql.SQLException

Specified by:: getPrimaryKeys in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name pattern; "" retrieves those without a schema; table - a table name
Returns:: null
Throws:: java.sql.SQLException - if a database-access error occurs

getProcedureColumns

public java.sql.ResultSet getProcedureColumns(java.lang.String catalog,
                                              java.lang.String schemaPattern,
                                              java.lang.String procedureNamePattern,
                                              java.lang.String columnNamePattern)
                                       throws java.sql.SQLException

Specified by:: getProcedureColumns in interface java.sql.DatabaseMetaData

Parameters:: catalog - This is ignored in org.postgresql, advise this is set to null; schemaPattern - This is ignored in org.postgresql, advise this is set to null; procedureNamePattern - a procedure name pattern; columnNamePattern - a column name pattern
Returns:: null
Throws:: java.sql.SQLException - if a database-access error occurs
See Also:: getSearchStringEscape()

getProcedures

public java.sql.ResultSet getProcedures(java.lang.String catalog,
                                        java.lang.String schemaPattern,
                                        java.lang.String procedureNamePattern)
                                 throws java.sql.SQLException

Specified by:: getProcedures in interface java.sql.DatabaseMetaData

Parameters:: catalog - - a catalog name; "" retrieves those without a * catalog; null means drop catalog name from criteria; schemaPattern - - a schema name pattern; "" retrieves those * without a schema - we ignore this parameter; procedureNamePattern - - a procedure name pattern
Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getProcedureTerm

public java.lang.String getProcedureTerm()
                                  throws java.sql.SQLException

What is the database vendor's preferred term for "procedure" - I kind of like "procedure" myself.

Specified by:: getProcedureTerm in interface java.sql.DatabaseMetaData

Returns:: the vendor term
Throws:: java.sql.SQLException - if a database access error occurs

getSchemas

public java.sql.ResultSet getSchemas()
                              throws java.sql.SQLException

Specified by:: getSchemas in interface java.sql.DatabaseMetaData

Throws:: java.sql.SQLException
See Also:: DatabaseMetaData.getSchemas()

getSchemaTerm

public java.lang.String getSchemaTerm()
                               throws java.sql.SQLException

What is the database vendor's preferred term for "schema" - well, we do not provide support for schemas, so lets just use that term.

Specified by:: getSchemaTerm in interface java.sql.DatabaseMetaData

Returns:: the vendor term
Throws:: java.sql.SQLException - if a database access error occurs

getSearchStringEscape

public java.lang.String getSearchStringEscape()
                                       throws java.sql.SQLException

This is the string that can be used to escape '_' and '%' in a search string pattern style catalog search parameters. We assume that '\' will work for all databases ...

Specified by:: getSearchStringEscape in interface java.sql.DatabaseMetaData

Returns:: the string used to escape wildcard characters
Throws:: java.sql.SQLException - if a database access error occurs

getSQLKeywords

public java.lang.String getSQLKeywords()
                                throws java.sql.SQLException

Get a comma separated list of all a database's SQL keywords that are NOT also SQL92 keywords. We assume that we don't use any non-SQL92 keywords.

Specified by:: getSQLKeywords in interface java.sql.DatabaseMetaData

Returns:: an empty string
Throws:: java.sql.SQLException - if a database access error occurs

getStringFunctions

public java.lang.String getStringFunctions()
                                    throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getStringFunctions in interface java.sql.DatabaseMetaData

Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getSystemFunctions

public java.lang.String getSystemFunctions()
                                    throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getSystemFunctions in interface java.sql.DatabaseMetaData

Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getTables

public java.sql.ResultSet getTables(java.lang.String catalog,
                                    java.lang.String schemaPattern,
                                    java.lang.String tableNamePattern,
                                    java.lang.String[] types)
                             throws java.sql.SQLException

Gets a description of the available tables.

Specified by:: getTables in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; this is ignored, and should be set to null; schemaPattern - a schema name pattern; this is ignored, and should be set to null; tableNamePattern - a table name pattern. For all tables this should be "%"; types - a list of table types to include; null returns all types
Returns:: null
Throws:: java.sql.SQLException - if a database-access error occurs.

getTablePrivileges

public java.sql.ResultSet getTablePrivileges(java.lang.String catalog,
                                             java.lang.String schemaPattern,
                                             java.lang.String tableNamePattern)
                                      throws java.sql.SQLException

Gets 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 priviledge 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 TABLE_SCHEM, TABLE_NAME, and PRIVILEGE.

Specified by:: getTablePrivileges in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; null means drop catalog name from the selection criteria; schemaPattern - a schema name pattern; "" retrieves those without a schema; tableNamePattern - a table name pattern
Returns:: ResultSet each row is a table privilege description
Throws:: java.sql.SQLException - if a database access error occurs

getTableTypes

public java.sql.ResultSet getTableTypes()
                                 throws java.sql.SQLException

Gets the table types available in this database. The results are ordered by table type.

Specified by:: getTableTypes in interface java.sql.DatabaseMetaData

Returns:: ResultSet each row has a single String column that is a catalog name
Throws:: java.sql.SQLException - if a database error occurs

getTimeDateFunctions

public java.lang.String getTimeDateFunctions()
                                      throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getTimeDateFunctions in interface java.sql.DatabaseMetaData

Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getTypeInfo

public java.sql.ResultSet getTypeInfo()
                               throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getTypeInfo in interface java.sql.DatabaseMetaData

Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

getUDTs

public java.sql.ResultSet getUDTs(java.lang.String catalog,
                                  java.lang.String schemaPattern,
                                  java.lang.String typeNamePattern,
                                  int[] types)
                           throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getUDTs in interface java.sql.DatabaseMetaData

Parameters:: catalog - a String value; schemaPattern - a String value; typeNamePattern - a String value; types - an int[] value
Returns:: null
Throws:: java.sql.SQLException - if an error occurs

getURL

public java.lang.String getURL()
                        throws java.sql.SQLException

What is the URL for this database?

Specified by:: getURL in interface java.sql.DatabaseMetaData

Returns:: the url or null if it cannott be generated
Throws:: java.sql.SQLException - if a database access error occurs

getUserName

public java.lang.String getUserName()
                             throws java.sql.SQLException

What is our user name as known to the database?

Specified by:: getUserName in interface java.sql.DatabaseMetaData

Returns:: our database user name
Throws:: java.sql.SQLException - if a database access error occurs

getVersionColumns

public java.sql.ResultSet getVersionColumns(java.lang.String catalog,
                                            java.lang.String schema,
                                            java.lang.String table)
                                     throws java.sql.SQLException

Feature not yet supported by C-JDBC.

Specified by:: getVersionColumns in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; schema - a schema name; "" retrieves those without a schema; table - a table name
Returns:: null
Throws:: java.sql.SQLException - if a database access error occurs

insertsAreDetected

public boolean insertsAreDetected(int type)
                           throws java.sql.SQLException

We do not support row insert in ResultSets.

Specified by:: insertsAreDetected in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

isCatalogAtStart

public boolean isCatalogAtStart()
                         throws java.sql.SQLException

Does a catalog appear at the start of a qualified table name? (Otherwise it appears at the end).

Specified by:: isCatalogAtStart in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

isReadOnly

public boolean isReadOnly()
                   throws java.sql.SQLException

Is the database in read-only mode?

Specified by:: isReadOnly in interface java.sql.DatabaseMetaData

Returns:: true if so
Throws:: java.sql.SQLException - if a database access error occurs

nullPlusNonNullIsNull

public boolean nullPlusNonNullIsNull()
                              throws java.sql.SQLException

Are concatenations between NULL and non-NULL values NULL? A JDBC Compliant driver always returns true.

Specified by:: nullPlusNonNullIsNull in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

nullsAreSortedAtEnd

public boolean nullsAreSortedAtEnd()
                            throws java.sql.SQLException

Are NULL values sorted at the end regardless of sort order?

Specified by:: nullsAreSortedAtEnd in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

nullsAreSortedAtStart

public boolean nullsAreSortedAtStart()
                              throws java.sql.SQLException

Are NULL values sorted at the start regardless of sort order?

Specified by:: nullsAreSortedAtStart in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

nullsAreSortedHigh

public boolean nullsAreSortedHigh()
                           throws java.sql.SQLException

Are NULL values sorted high?

Specified by:: nullsAreSortedHigh in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

nullsAreSortedLow

public boolean nullsAreSortedLow()
                          throws java.sql.SQLException

Are NULL values sorted low?

Specified by:: nullsAreSortedLow in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

othersDeletesAreVisible

public boolean othersDeletesAreVisible(int type)
                                throws java.sql.SQLException

C-JDBC does not support deletes.

Specified by:: othersDeletesAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

othersInsertsAreVisible

public boolean othersInsertsAreVisible(int type)
                                throws java.sql.SQLException

C-JDBC does not support inserts.

Specified by:: othersInsertsAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

othersUpdatesAreVisible

public boolean othersUpdatesAreVisible(int type)
                                throws java.sql.SQLException

C-JDBC does not support updates.

Specified by:: othersUpdatesAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

ownDeletesAreVisible

public boolean ownDeletesAreVisible(int type)
                             throws java.sql.SQLException

C-JDBC does not support deletes.

Specified by:: ownDeletesAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

ownInsertsAreVisible

public boolean ownInsertsAreVisible(int type)
                             throws java.sql.SQLException

C-JDBC does not support inserts.

Specified by:: ownInsertsAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

ownUpdatesAreVisible

public boolean ownUpdatesAreVisible(int type)
                             throws java.sql.SQLException

C-JDBC does not support updates.

Specified by:: ownUpdatesAreVisible in interface java.sql.DatabaseMetaData

Parameters:: type - ignored
Returns:: false
Throws:: java.sql.SQLException -

storesLowerCaseIdentifiers

public boolean storesLowerCaseIdentifiers()
                                   throws java.sql.SQLException

Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in lower case?

Specified by:: storesLowerCaseIdentifiers in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if an error occurs

storesLowerCaseQuotedIdentifiers

public boolean storesLowerCaseQuotedIdentifiers()
                                         throws java.sql.SQLException

Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in lower case?

Specified by:: storesLowerCaseQuotedIdentifiers in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if an error occurs

storesMixedCaseIdentifiers

public boolean storesMixedCaseIdentifiers()
                                   throws java.sql.SQLException

Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in mixed case?

Specified by:: storesMixedCaseIdentifiers in interface java.sql.DatabaseMetaData

Returns:: true if so
Throws:: java.sql.SQLException - if an error occurs

storesMixedCaseQuotedIdentifiers

public boolean storesMixedCaseQuotedIdentifiers()
                                         throws java.sql.SQLException

Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in mixed case?

Specified by:: storesMixedCaseQuotedIdentifiers in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if an error occurs

storesUpperCaseIdentifiers

public boolean storesUpperCaseIdentifiers()
                                   throws java.sql.SQLException

Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in upper case?

Specified by:: storesUpperCaseIdentifiers in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if an error occurs

storesUpperCaseQuotedIdentifiers

public boolean storesUpperCaseQuotedIdentifiers()
                                         throws java.sql.SQLException

Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in upper case?

Specified by:: storesUpperCaseQuotedIdentifiers in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if an error occurs

supportsAlterTableWithAddColumn

public boolean supportsAlterTableWithAddColumn()
                                        throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsAlterTableWithAddColumn in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsAlterTableWithDropColumn

public boolean supportsAlterTableWithDropColumn()
                                         throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsAlterTableWithDropColumn in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsANSI92EntryLevelSQL

public boolean supportsANSI92EntryLevelSQL()
                                    throws java.sql.SQLException

Does this driver support the ANSI-92 entry level SQL grammar? All JDBC Compliant drivers must return true. I think we have to support outer joins for this to be true.

Specified by:: supportsANSI92EntryLevelSQL in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsANSI92FullSQL

public boolean supportsANSI92FullSQL()
                              throws java.sql.SQLException

Does this driver support the ANSI-92 full SQL grammar?

Specified by:: supportsANSI92FullSQL in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsANSI92IntermediateSQL

public boolean supportsANSI92IntermediateSQL()
                                      throws java.sql.SQLException

Does this driver support the ANSI-92 intermediate level SQL grammar? Anyone who does not support Entry level cannot support Intermediate level.

Specified by:: supportsANSI92IntermediateSQL in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsBatchUpdates

public boolean supportsBatchUpdates()
                             throws java.sql.SQLException

Does this driver support batch updates ? Yes, since 1.0a5.

Specified by:: supportsBatchUpdates in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsCatalogsInDataManipulation

public boolean supportsCatalogsInDataManipulation()
                                           throws java.sql.SQLException

Can a catalog name be used in a data manipulation statement?

Specified by:: supportsCatalogsInDataManipulation in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsCatalogsInIndexDefinitions

public boolean supportsCatalogsInIndexDefinitions()
                                           throws java.sql.SQLException

Can a catalog name be used in an index definition?

Specified by:: supportsCatalogsInIndexDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsCatalogsInPrivilegeDefinitions

public boolean supportsCatalogsInPrivilegeDefinitions()
                                               throws java.sql.SQLException

Can a catalog name be used in a privilege definition statement?

Specified by:: supportsCatalogsInPrivilegeDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsCatalogsInProcedureCalls

public boolean supportsCatalogsInProcedureCalls()
                                         throws java.sql.SQLException

Can a catalog name be used in a procedure call statement?

Specified by:: supportsCatalogsInProcedureCalls in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsCatalogsInTableDefinitions

public boolean supportsCatalogsInTableDefinitions()
                                           throws java.sql.SQLException

Can a catalog name be used in a table definition statement?

Specified by:: supportsCatalogsInTableDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsColumnAliasing

public boolean supportsColumnAliasing()
                               throws java.sql.SQLException

Is column aliasing supported?

If so, the SQL AS clause can be used to provide names for computed columns or to provide alias names for columns as required. A JDBC Compliant driver always returns true.

e.g.

  select count(C) as C_COUNT from T group by C;

should return a column named as C_COUNT instead of count(C)

Specified by:: supportsColumnAliasing in interface java.sql.DatabaseMetaData

Returns:: true if so
Throws:: java.sql.SQLException - if a database access error occurs

supportsConvert

public boolean supportsConvert()
                        throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsConvert in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsConvert

public boolean supportsConvert(int fromType,
                               int toType)
                        throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsConvert in interface java.sql.DatabaseMetaData

Parameters:: fromType - an int value; toType - an int value
Returns:: false
Throws:: java.sql.SQLException -

supportsCoreSQLGrammar

public boolean supportsCoreSQLGrammar()
                               throws java.sql.SQLException

Does this driver support the Core ODBC SQL grammar. We need SQL-92 conformance for this.

Specified by:: supportsCoreSQLGrammar in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsCorrelatedSubqueries

public boolean supportsCorrelatedSubqueries()
                                     throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsCorrelatedSubqueries in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsDataDefinitionAndDataManipulationTransactions

public boolean supportsDataDefinitionAndDataManipulationTransactions()
                                                              throws java.sql.SQLException

Are both data definition and data manipulation transactions supported? In Postgres we could not do a CREATE TABLE within a transaction, so I am assuming that we don't.

Specified by:: supportsDataDefinitionAndDataManipulationTransactions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsDataManipulationTransactionsOnly

public boolean supportsDataManipulationTransactionsOnly()
                                                 throws java.sql.SQLException

Are only data manipulation statements within a transaction supported?

Specified by:: supportsDataManipulationTransactionsOnly in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsDifferentTableCorrelationNames

public boolean supportsDifferentTableCorrelationNames()
                                               throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsDifferentTableCorrelationNames in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsExpressionsInOrderBy

public boolean supportsExpressionsInOrderBy()
                                     throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsExpressionsInOrderBy in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsExtendedSQLGrammar

public boolean supportsExtendedSQLGrammar()
                                   throws java.sql.SQLException

Does this driver support the Extended (Level 2) ODBC SQL grammar. We don't conform to the Core (Level 1), so we can't conform to the Extended SQL Grammar.

Specified by:: supportsExtendedSQLGrammar in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsFullOuterJoins

public boolean supportsFullOuterJoins()
                               throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsFullOuterJoins in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsGroupBy

public boolean supportsGroupBy()
                        throws java.sql.SQLException

Is some form of "GROUP BY" clause supported? I checked it, and yes it is.

Specified by:: supportsGroupBy in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsGroupByBeyondSelect

public boolean supportsGroupByBeyondSelect()
                                    throws java.sql.SQLException

Can a "GROUP BY" clause add columns not in the SELECT provided it specifies all the columns in the SELECT? Does anyone actually understand what they mean here?

Specified by:: supportsGroupByBeyondSelect in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsGroupByUnrelated

public boolean supportsGroupByUnrelated()
                                 throws java.sql.SQLException

Can a "GROUP BY" clause use columns not in the SELECT? I checked it - it seems to allow it.

Specified by:: supportsGroupByUnrelated in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsIntegrityEnhancementFacility

public boolean supportsIntegrityEnhancementFacility()
                                             throws java.sql.SQLException

Is the SQL Integrity Enhancement Facility supported? I haven't seen this mentioned anywhere, so I guess not

Specified by:: supportsIntegrityEnhancementFacility in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsLikeEscapeClause

public boolean supportsLikeEscapeClause()
                                 throws java.sql.SQLException

Is the escape character in "LIKE" clauses supported? A JDBC compliant driver always returns true.

Specified by:: supportsLikeEscapeClause in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsLimitedOuterJoins

public boolean supportsLimitedOuterJoins()
                                  throws java.sql.SQLException

Is there limited support for outer joins? (This will be true if supportFullOuterJoins is true)

Specified by:: supportsLimitedOuterJoins in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsMinimumSQLGrammar

public boolean supportsMinimumSQLGrammar()
                                  throws java.sql.SQLException

Does this driver support the minimum ODBC SQL grammar. This grammar is defined at:
http://www.microsoft.com/msdn/sdk/platforms/doc/odbc/src/intropr.htm

In Postgres Appendix C. From this description, we seem to support the ODBC minimal (Level 0) grammar.

Specified by:: supportsMinimumSQLGrammar in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsMixedCaseIdentifiers

public boolean supportsMixedCaseIdentifiers()
                                     throws java.sql.SQLException

Does the database treat mixed case unquoted SQL identifiers as case sensitive and as a result store them in mixed case? A JDBC-Compliant driver will always return false.

Predicament - what do they mean by "SQL identifiers" - if it means the names of the tables and columns, then the answers given below are correct - otherwise I don't know.

Specified by:: supportsMixedCaseIdentifiers in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsMixedCaseQuotedIdentifiers

public boolean supportsMixedCaseQuotedIdentifiers()
                                           throws java.sql.SQLException

Does the database treat mixed case quoted SQL identifiers as case sensitive and as a result store them in mixed case? A JDBC compliant driver will always return true.

Predicament - what do they mean by "SQL identifiers" - if it means the names of the tables and columns, then the answers given below are correct - otherwise I don't know.

Specified by:: supportsMixedCaseQuotedIdentifiers in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsMultipleResultSets

public boolean supportsMultipleResultSets()
                                   throws java.sql.SQLException

Are multiple ResultSets from a single execute supported? Well, it should be implemented, but this is possible for most of the backends. Should really ask the Controller about that.

Specified by:: supportsMultipleResultSets in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsMultipleTransactions

public boolean supportsMultipleTransactions()
                                     throws java.sql.SQLException

Can we have multiple transactions open at once (on different connections?). I guess we can have, since we are relying on it.

Specified by:: supportsMultipleTransactions in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsNonNullableColumns

public boolean supportsNonNullableColumns()
                                   throws java.sql.SQLException

Can columns be defined as non-nullable. A JDBC Compliant driver always returns true.

Specified by:: supportsNonNullableColumns in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsOpenCursorsAcrossCommit

public boolean supportsOpenCursorsAcrossCommit()
                                        throws java.sql.SQLException

Does this database support having cursors remain open across commits. Note that a return value of flase does not mean that cursors are always close on commit; rather false means that cursors are not always left open across commits.

Specified by:: supportsOpenCursorsAcrossCommit in interface java.sql.DatabaseMetaData

Returns:: true if so
Throws:: java.sql.SQLException - if a database access error occurs

supportsOpenCursorsAcrossRollback

public boolean supportsOpenCursorsAcrossRollback()
                                          throws java.sql.SQLException

Do we support open cursors across rollback ?

Specified by:: supportsOpenCursorsAcrossRollback in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsOpenStatementsAcrossCommit

public boolean supportsOpenStatementsAcrossCommit()
                                           throws java.sql.SQLException

Can statements remain open across commits? They may, but this driver cannot guarentee that. In further reflection. We are talking a Statement object jere, so the answer is yes, since the Statement is only a vehicle to ExecSQL().

Specified by:: supportsOpenStatementsAcrossCommit in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsOpenStatementsAcrossRollback

public boolean supportsOpenStatementsAcrossRollback()
                                             throws java.sql.SQLException

Can statements remain open across rollbacks? They may, but this driver cannot guarentee that. In further contemplation, we are talking a Statement object here, so the answer is yes, since the Statement is only a vehicle to ExecSQL() in Connection.

Specified by:: supportsOpenStatementsAcrossRollback in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsOrderByUnrelated

public boolean supportsOrderByUnrelated()
                                 throws java.sql.SQLException

Can an "ORDER BY" clause use columns not in the SELECT?

Specified by:: supportsOrderByUnrelated in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsOuterJoins

public boolean supportsOuterJoins()
                           throws java.sql.SQLException

Is some form of outer join supported?

Specified by:: supportsOuterJoins in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsPositionedDelete

public boolean supportsPositionedDelete()
                                 throws java.sql.SQLException

We support cursors for gets only it seems. I dont see a method to get a positioned delete.

Specified by:: supportsPositionedDelete in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsPositionedUpdate

public boolean supportsPositionedUpdate()
                                 throws java.sql.SQLException

Is positioned UPDATE supported?

Specified by:: supportsPositionedUpdate in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsResultSetConcurrency

public boolean supportsResultSetConcurrency(int type,
                                            int concurrency)
                                     throws java.sql.SQLException

Which combination of concurrency level and ResultSet type is supported ?

Specified by:: supportsResultSetConcurrency in interface java.sql.DatabaseMetaData

Parameters:: type - ResultSet type; concurrency - concurrency level
Returns:: false for TYPE_SCROLL_SENSITIVE and CONCUR_UPDATABLE
Throws:: java.sql.SQLException - if an error occurs

supportsResultSetType

public boolean supportsResultSetType(int type)
                              throws java.sql.SQLException

Supported ResultSet types.

Specified by:: supportsResultSetType in interface java.sql.DatabaseMetaData

Parameters:: type - ResultSet type
Returns:: false for TYPE_SCROLL_SENSITIVE
Throws:: java.sql.SQLException - if an error occurs

supportsSchemasInDataManipulation

public boolean supportsSchemasInDataManipulation()
                                          throws java.sql.SQLException

Can a schema name be used in a data manipulation statement? Nope.

Specified by:: supportsSchemasInDataManipulation in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSchemasInIndexDefinitions

public boolean supportsSchemasInIndexDefinitions()
                                          throws java.sql.SQLException

Can a schema name be used in an index definition statement?

Specified by:: supportsSchemasInIndexDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSchemasInPrivilegeDefinitions

public boolean supportsSchemasInPrivilegeDefinitions()
                                              throws java.sql.SQLException

Can a schema name be used in a privilege definition statement?

Specified by:: supportsSchemasInPrivilegeDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSchemasInProcedureCalls

public boolean supportsSchemasInProcedureCalls()
                                        throws java.sql.SQLException

Can a schema name be used in a procedure call statement? Nope.

Specified by:: supportsSchemasInProcedureCalls in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSchemasInTableDefinitions

public boolean supportsSchemasInTableDefinitions()
                                          throws java.sql.SQLException

Can a schema be used in a table definition statement? Nope.

Specified by:: supportsSchemasInTableDefinitions in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSelectForUpdate

public boolean supportsSelectForUpdate()
                                throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsSelectForUpdate in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsStoredProcedures

public boolean supportsStoredProcedures()
                                 throws java.sql.SQLException

Yes, stored procedures are supported since 1.0b6.

Specified by:: supportsStoredProcedures in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException -

supportsSubqueriesInComparisons

public boolean supportsSubqueriesInComparisons()
                                        throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsSubqueriesInComparisons in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsSubqueriesInExists

public boolean supportsSubqueriesInExists()
                                   throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know

Specified by:: supportsSubqueriesInExists in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsSubqueriesInIns

public boolean supportsSubqueriesInIns()
                                throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsSubqueriesInIns in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsSubqueriesInQuantifieds

public boolean supportsSubqueriesInQuantifieds()
                                        throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsSubqueriesInQuantifieds in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsTableCorrelationNames

public boolean supportsTableCorrelationNames()
                                      throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: supportsTableCorrelationNames in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException -

supportsTransactionIsolationLevel

public boolean supportsTransactionIsolationLevel(int level)
                                          throws java.sql.SQLException

Does the database support the given transaction isolation level? We should support all of them or at least ask the Controller ...

Specified by:: supportsTransactionIsolationLevel in interface java.sql.DatabaseMetaData

Parameters:: level - the values are defined in java.sql.Connection
Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs
See Also:: Connection

supportsTransactions

public boolean supportsTransactions()
                             throws java.sql.SQLException

Are transactions supported? If not, commit and rollback are noops and the isolation level is TRANSACTION_NONE. We do support transactions.

Specified by:: supportsTransactions in interface java.sql.DatabaseMetaData

Returns:: true if transactions are supported
Throws:: java.sql.SQLException - if a database access error occurs

supportsUnion

public boolean supportsUnion()
                      throws java.sql.SQLException

Is SQL UNION supported?

Specified by:: supportsUnion in interface java.sql.DatabaseMetaData

Returns:: true
Throws:: java.sql.SQLException - if a database access error occurs

supportsUnionAll

public boolean supportsUnionAll()
                         throws java.sql.SQLException

Is SQL UNION ALL supported? Nope.

Specified by:: supportsUnionAll in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

updatesAreDetected

public boolean updatesAreDetected(int type)
                           throws java.sql.SQLException

Not implemented (returns false). We should ask the Controller to know.

Specified by:: updatesAreDetected in interface java.sql.DatabaseMetaData

Parameters:: type - an int value
Returns:: false
Throws:: java.sql.SQLException -

usesLocalFilePerTable

public boolean usesLocalFilePerTable()
                              throws java.sql.SQLException

Does the database use a file for each table? Well, not really, since it doesn't use local files.

Specified by:: usesLocalFilePerTable in interface java.sql.DatabaseMetaData

Returns:: true if so
Throws:: java.sql.SQLException - if a database access error occurs

usesLocalFiles

public boolean usesLocalFiles()
                       throws java.sql.SQLException

Does the database store tables in a local file? No, it stores them in a file on the server.

Specified by:: usesLocalFiles in interface java.sql.DatabaseMetaData

Returns:: false
Throws:: java.sql.SQLException - if a database access error occurs

supportsSavepoints

public boolean supportsSavepoints()
                           throws java.sql.SQLException

Retrieves whether this database supports savepoints.

This is not yet supported by C-JDBC.

Specified by:: supportsSavepoints in interface java.sql.DatabaseMetaData

Returns:: true if savepoints are supported; false otherwise
Throws:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

supportsNamedParameters

public boolean supportsNamedParameters()
                                throws java.sql.SQLException

Retrieves whether this database supports named parameters to callable statements.

This is not yet supported by C-JDBC.

Specified by:: supportsNamedParameters in interface java.sql.DatabaseMetaData

Returns:: true if named parameters are supported; false otherwise
Throws:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

supportsMultipleOpenResults

public boolean supportsMultipleOpenResults()
                                    throws java.sql.SQLException

Retrieves whether it is possible to have multiple ResultSet objects returned from a CallableStatement object simultaneously.

This is not yet supported by C-JDBC.

Specified by:: supportsMultipleOpenResults in interface java.sql.DatabaseMetaData

Returns:: true if a CallableStatement object can return multiple ResultSet objects simultaneously; false otherwise
Throws:: java.sql.SQLException - if a datanase access error occurs
Since:: JDK 1.4

supportsGetGeneratedKeys

public boolean supportsGetGeneratedKeys()
                                 throws java.sql.SQLException

Retrieves whether auto-generated keys can be retrieved after a statement has been executed.

Specified by:: supportsGetGeneratedKeys in interface java.sql.DatabaseMetaData

Returns:: true if auto-generated keys can be retrieved after a statement has executed; false otherwise
Throws:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

getSuperTypes

public java.sql.ResultSet getSuperTypes(java.lang.String catalog,
                                        java.lang.String schemaPattern,
                                        java.lang.String typeNamePattern)
                                 throws java.sql.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 be null)
TYPE_SCHEM String => UDT's schema (may be null)
TYPE_NAME String => type name of the UDT
SUPERTYPE_CAT String => the direct super type's catalog (may be null)
SUPERTYPE_SCHEM String => the direct super type's schema (may be null)
SUPERTYPE_NAME String => the direct super type's name

Note: If the driver does not support type hierarchies, an empty result set is returned.

Specified by:: getSuperTypes in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; null means drop catalog name from the selection criteria; schemaPattern - a schema name pattern; "" retrieves those without a schema; typeNamePattern - 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:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

getSuperTables

public java.sql.ResultSet getSuperTables(java.lang.String catalog,
                                         java.lang.String schemaPattern,
                                         java.lang.String tableNamePattern)
                                  throws java.sql.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 be null)
TABLE_SCHEM String => type's schema (may be null)
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.

Specified by:: getSuperTables in interface java.sql.DatabaseMetaData

Parameters:: catalog - a catalog name; "" retrieves those without a catalog; null means drop catalog name from the selection criteria; schemaPattern - a schema name pattern; "" retrieves those without a schema; tableNamePattern - a table name pattern; may be a fully-qualified name
Returns:: a ResultSet object in which each row is a type description
Throws:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

getAttributes

public java.sql.ResultSet getAttributes(java.lang.String catalog,
                                        java.lang.String schemaPattern,
                                        java.lang.String typeNamePattern,
                                        java.lang.String attributeNamePattern)
                                 throws java.sql.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 TYPE_SCHEM, TYPE_NAME and ORDINAL_POSITION. This description does not contain inherited attributes.

The ResultSet object that is returned has the following columns:

TYPE_CAT String => type catalog (may be null)
TYPE_SCHEM String => type schema (may be null)
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
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 be null)
ATTR_DEF String => default value (may be null)
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 column in table (starting at 1)
IS_NULLABLE String => "NO" means column definitely does not allow NULL values; "YES" means the column might allow NULL values. An empty string means 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)

Specified by:: getAttributes in interface java.sql.DatabaseMetaData

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 search; schemaPattern - 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 search; typeNamePattern - a type name pattern; must match the type name as it is stored in the database; attributeNamePattern - 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:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4

supportsResultSetHoldability

public boolean supportsResultSetHoldability(int holdability)
                                     throws java.sql.SQLException

Retrieves whether this database supports the given result set holdability.

This is not yet supported by C-JDBC.

Specified by:: supportsResultSetHoldability in interface java.sql.DatabaseMetaData

Parameters:: holdability - one of the following constants: ResultSet.HOLD_CURSORS_OVER_COMMIT or ResultSet.CLOSE_CURSORS_AT_COMMIT
Returns:: true if so; false otherwise
Throws:: java.sql.SQLException - if a database access error occurs
Since:: JDK 1.4
See Also:: Connection





getResultSetHoldability
public int getResultSetHoldability()
                            throws java.sql.SQLException

Retrieves the default holdability of this ResultSet object.


Specified by:
getResultSetHoldability in interface java.sql.DatabaseMetaData



Returns:
the default holdability; either
         ResultSet.HOLD_CURSORS_OVER_COMMIT or
         ResultSet.CLOSE_CURSORS_AT_COMMIT
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






getDatabaseMajorVersion
public int getDatabaseMajorVersion()
                            throws java.sql.SQLException

Retrieves the major version number of the underlying database.
 
 This is not yet supported by C-JDBC.


Specified by:
getDatabaseMajorVersion in interface java.sql.DatabaseMetaData



Returns:
the underlying database's major version
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






getDatabaseMinorVersion
public int getDatabaseMinorVersion()
                            throws java.sql.SQLException

Retrieves the minor version number of the underlying database.
 
 This is not yet supported by C-JDBC.


Specified by:
getDatabaseMinorVersion in interface java.sql.DatabaseMetaData



Returns:
underlying database's minor version
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






getJDBCMajorVersion
public int getJDBCMajorVersion()
                        throws java.sql.SQLException

Retrieves the major JDBC version number for this driver.


Specified by:
getJDBCMajorVersion in interface java.sql.DatabaseMetaData



Returns:
JDBC version major number
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






getJDBCMinorVersion
public int getJDBCMinorVersion()
                        throws java.sql.SQLException

Retrieves the minor JDBC version number for this driver.


Specified by:
getJDBCMinorVersion in interface java.sql.DatabaseMetaData



Returns:
JDBC version minor number
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






getSQLStateType
public int getSQLStateType()
                    throws java.sql.SQLException

Indicates whether the SQLSTATE returned by
 SQLException.getSQLState is X/Open (now known as Open Group)
 SQL CLI or SQL99.


Specified by:
getSQLStateType in interface java.sql.DatabaseMetaData



Returns:
the type of SQLSTATE; one of: sqlStateXOpen or sqlStateSQL99
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






locatorsUpdateCopy
public boolean locatorsUpdateCopy()
                           throws java.sql.SQLException

Indicates whether updates made to a LOB are made on a copy or directly to
 the LOB.


Specified by:
locatorsUpdateCopy in interface java.sql.DatabaseMetaData



Returns:
true if updates are made to a copy of the LOB;
         false if updates are made directly to the LOB
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4






supportsStatementPooling
public boolean supportsStatementPooling()
                                 throws java.sql.SQLException

Retrieves whether this database supports statement pooling.
 
 This is not yet supported in C-JDBC.


Specified by:
supportsStatementPooling in interface java.sql.DatabaseMetaData



Returns:
true if so; false otherwise
Throws:
java.sql.SQLException - if a database access error occurs
Since:
  JDK 1.4















  
      Overview 
      Package 
    Class 
      Use 
      Tree 
      Deprecated 
      Index 
      Help 
  









 PREV CLASS 
 NEXT CLASS

  FRAMES   
 NO FRAMES   
 






  SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD






Copyright © 2002, 2005 - ObjectWeb Consortium - All Rights Reserved.

org.objectweb.cjdbc.driver Class DatabaseMetaData

connection

DatabaseMetaData

allProceduresAreCallable

allTablesAreSelectable

dataDefinitionCausesTransactionCommit

dataDefinitionIgnoredInTransactions

deletesAreDetected

doesMaxRowSizeIncludeBlobs

getBestRowIdentifier

getCatalogs

getCatalogSeparator

getCatalogTerm

getColumns

getColumnPrivileges

getConnection

getCrossReference

getDatabaseProductName

getDatabaseProductVersion

getDefaultTransactionIsolation

getDriverMajorVersion

getDriverMinorVersion

getDriverName

getDriverVersion

getExportedKeys

getExtraNameCharacters

getIdentifierQuoteString

getImportedKeys

getIndexInfo

getMaxBinaryLiteralLength

getMaxCatalogNameLength

getMaxCharLiteralLength

getMaxColumnNameLength

getMaxColumnsInGroupBy

getMaxColumnsInIndex

getMaxColumnsInOrderBy

getMaxColumnsInSelect

getMaxColumnsInTable

getMaxConnections

getMaxCursorNameLength

getMaxIndexLength

getMaxProcedureNameLength

getMaxRowSize

getMaxSchemaNameLength

getMaxStatementLength

getMaxStatements

getMaxTableNameLength

getMaxTablesInSelect

getMaxUserNameLength

getNumericFunctions

getPrimaryKeys

getProcedureColumns

getProcedures

getProcedureTerm

getSchemas

getSchemaTerm

getSearchStringEscape

getSQLKeywords

getStringFunctions

getSystemFunctions

getTables

getTablePrivileges

getTableTypes

getTimeDateFunctions

getTypeInfo

getUDTs

getURL

getUserName

getVersionColumns

insertsAreDetected

isCatalogAtStart

isReadOnly

nullPlusNonNullIsNull

nullsAreSortedAtEnd

nullsAreSortedAtStart

nullsAreSortedHigh

nullsAreSortedLow

othersDeletesAreVisible

othersInsertsAreVisible

othersUpdatesAreVisible

org.objectweb.cjdbc.driver
Class DatabaseMetaData