MonetDatabaseMetaData (MonetDB JDBC new 2.32 API)

java.lang.Object
- nl.cwi.monetdb.jdbc.MonetWrapper
- - nl.cwi.monetdb.jdbc.MonetDatabaseMetaData

All Implemented Interfaces:

DatabaseMetaData, Wrapper
```
public class MonetDatabaseMetaData
extends MonetWrapper
implements DatabaseMetaData
```
A DatabaseMetaData object suitable for the MonetDB database.

Version:

0.6

Author:

Fabian Groffen, Martin van Dinther

Field Summary
- Fields inherited from interface java.sql.DatabaseMetaData
  attributeNoNulls, attributeNullable, attributeNullableUnknown, bestRowNotPseudo, bestRowPseudo, bestRowSession, bestRowTemporary, bestRowTransaction, bestRowUnknown, columnNoNulls, columnNullable, columnNullableUnknown, functionColumnIn, functionColumnInOut, functionColumnOut, functionColumnResult, functionColumnUnknown, functionNoNulls, functionNoTable, functionNullable, functionNullableUnknown, functionResultUnknown, functionReturn, functionReturnsTable, importedKeyCascade, importedKeyInitiallyDeferred, importedKeyInitiallyImmediate, importedKeyNoAction, importedKeyNotDeferrable, importedKeyRestrict, importedKeySetDefault, importedKeySetNull, procedureColumnIn, procedureColumnInOut, procedureColumnOut, procedureColumnResult, procedureColumnReturn, procedureColumnUnknown, procedureNoNulls, procedureNoResult, procedureNullable, procedureNullableUnknown, procedureResultUnknown, procedureReturnsResult, sqlStateSQL, sqlStateSQL99, sqlStateXOpen, tableIndexClustered, tableIndexHashed, tableIndexOther, tableIndexStatistic, typeNoNulls, typeNullable, typeNullableUnknown, typePredBasic, typePredChar, typePredNone, typeSearchable, versionColumnNotPseudo, versionColumnPseudo, versionColumnUnknown

Constructor Summary

Constructors
Constructor and Description

MonetDatabaseMetaData(Connection parent)

Constructors
Constructor and Description
`MonetDatabaseMetaData(Connection parent)`

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`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`	`autoCommitFailureClosesAllResultSets()` Retrieves whether a SQLException while autoCommit is true inidcates that all open ResultSets are closed, even ones that are holdable.
`boolean`	`dataDefinitionCausesTransactionCommit()` Does a data definition statement within a transaction force the transaction to commit? I think this means something like:
`boolean`	`dataDefinitionIgnoredInTransactions()` Is a data definition statement within a transaction ignored?
`boolean`	`deletesAreDetected(int i)`
`boolean`	`doesMaxRowSizeIncludeBlobs()` Did getMaxRowSize() include the SQL data types LONGVARCHAR and LONGVARBINARY blobs? Yes I thought so...
`boolean`	`generatedKeyAlwaysReturned()` Retrieves whether a generated key will always be returned if the column name(s) or index(es) specified for the auto generated key column(s) are valid and the statement succeeds.
`ResultSet`	`getAttributes(String catalog, String schemaPattern, String typeNamePattern, String attributeNamePattern)` Retrieves a description of the given attribute of the given type for a user-defined type (UDT) that is available in the given schema and catalog.
`ResultSet`	`getBestRowIdentifier(String catalog, String schema, String table, int scope, boolean nullable)` Get a description of a table's optimal set of columns that uniquely identifies a row.
`ResultSet`	`getCatalogs()` Get the catalog names available in this database.
`String`	`getCatalogSeparator()` What is the Catalog separator.
`String`	`getCatalogTerm()` What is the database vendor's preferred term for "catalog"? MonetDB doesn't really have them (from driver accessible) but from the monetdb.conf file the term "database" sounds best
`ResultSet`	`getClientInfoProperties()` Retrieves a list of the client info properties that the driver supports.
`ResultSet`	`getColumnPrivileges(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern)` Get a description of the access rights for a table's columns.
`ResultSet`	`getColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern)` Get a description of table columns available in a catalog.
`Connection`	`getConnection()` Retrieves the connection that produced this metadata object.
`ResultSet`	`getCrossReference(String pcatalog, String pschema, String ptable, String fcatalog, String fschema, String ftable)` Get a description of the foreign key columns in the foreign key table that reference the primary key columns of the primary key table.
`int`	`getDatabaseMajorVersion()` Retrieves the major version number of the underlying database.
`int`	`getDatabaseMinorVersion()` Retrieves the minor version number of the underlying database.
`String`	`getDatabaseProductName()` What is the name of this database product - this should be MonetDB of course, so we return that explicitly.
`String`	`getDatabaseProductVersion()` What is the version of this database product.
`int`	`getDefaultTransactionIsolation()` What is the database's default transaction isolation level? We only see commited data, nonrepeatable reads and phantom reads can occur.
`int`	`getDriverMajorVersion()` What is this JDBC driver's major version number?
`int`	`getDriverMinorVersion()` What is this JDBC driver's minor version number?
`String`	`getDriverName()` What is the name of this JDBC driver?
`String`	`getDriverVersion()` Retrieves the version number of this JDBC driver as a String.
`ResultSet`	`getExportedKeys(String catalog, String schema, String table)` Get a description of a foreign key columns that reference a table's primary key columns (the foreign keys exported by a table).
`String`	`getExtraNameCharacters()` Get all the "extra" characters that can be used in unquoted identifier names (those beyond a-zA-Z0-9 and _) MonetDB has no extra characters (verified it for chars: !@#$%^&*()~{}[]?
`ResultSet`	`getFunctionColumns(String catalog, String schemaPattern, String functionNamePattern, String columnNamePattern)` Retrieves a description of the given catalog's system or user function parameters and return type.
`ResultSet`	`getFunctions(String catalog, String schemaPattern, String functionNamePattern)` Retrieves a description of the system and user functions available in the given catalog.
`String`	`getIdentifierQuoteString()` What is the string used to quote SQL identifiers? This returns a space if identifier quoting isn't supported.
`ResultSet`	`getImportedKeys(String catalog, String schema, String table)` Get a description of the primary key columns that are referenced by a table's foreign key columns (the primary keys imported by a table).
`ResultSet`	`getIndexInfo(String catalog, String schema, String table, boolean unique, boolean approximate)` Retrieves a description of the given table's indices and statistics.
`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()` What is the maximum length of a catalog
`int`	`getMaxCharLiteralLength()` What is the maximum length for a character literal
`int`	`getMaxColumnNameLength()` Whats the limit on column name length.
`int`	`getMaxColumnsInGroupBy()` What is the maximum number of columns in a "GROUP BY" clause?
`int`	`getMaxColumnsInIndex()` What's the maximum number of columns allowed in an index?
`int`	`getMaxColumnsInOrderBy()` What's the maximum number of columns in an "ORDER BY clause?
`int`	`getMaxColumnsInSelect()` What is the maximum number of columns in a "SELECT" list?
`int`	`getMaxColumnsInTable()` What is the maximum number of columns in a table? The theoretical max value of int column sys._columns.id is 2^31 -1 but this is for all columns of all tables in all schemas (including all data dictionary columns).
`int`	`getMaxConnections()` How many active connections can we have at a time to this database? Well, since it depends on Mserver, which just listens for new connections and creates a new thread for each connection, this number can be very high, and theoretically till the system runs out of resources.
`int`	`getMaxCursorNameLength()` What is the maximum cursor name length Actually we do not do named cursors, so I keep the value small as a precaution for maybe the future.
`int`	`getMaxIndexLength()` Retrieves the maximum number of bytes for an index, including all of the parts of the index.
`int`	`getMaxProcedureNameLength()` What is the maximum length of a procedure name
`int`	`getMaxRowSize()` What is the maximum length of a single row?
`int`	`getMaxSchemaNameLength()` Retrieves the maximum number of characters that this database allows in a schema name.
`int`	`getMaxStatementLength()` What is the maximum length of a SQL statement?
`int`	`getMaxStatements()` 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.
`int`	`getMaxTableNameLength()` What is the maximum length of a table name
`int`	`getMaxTablesInSelect()` What is the maximum number of tables that can be specified in a SELECT?
`int`	`getMaxUserNameLength()` What is the maximum length of a user name
`String`	`getNumericFunctions()`
`ResultSet`	`getPrimaryKeys(String catalog, String schema, String table)` Get a description of a table's primary key columns.
`ResultSet`	`getProcedureColumns(String catalog, String schemaPattern, String procedureNamePattern, String columnNamePattern)` Get a description of a catalog's stored procedure parameters and result columns.
`ResultSet`	`getProcedures(String catalog, String schemaPattern, String procedureNamePattern)` Get a description of stored procedures available in a catalog
`String`	`getProcedureTerm()` What is the database vendor's preferred term for "procedure"?
`ResultSet`	`getPseudoColumns(String catalog, String schemaPattern, String tableNamePattern, String columnNamePattern)` Retrieves a description of the pseudo or hidden columns available in a given table within the specified catalog and schema.
`int`	`getResultSetHoldability()` Retrieves the default holdability of this `ResultSet` object.
`RowIdLifetime`	`getRowIdLifetime()` Indicates whether or not this data source supports the SQL ROWID type, and if so the lifetime for which a RowId object remains valid.
`ResultSet`	`getSchemas()` Get the schema names available in this database.
`ResultSet`	`getSchemas(String catalog, String schemaPattern)` Get the schema names available in this database.
`String`	`getSchemaTerm()` What is the database vendor's preferred term for "schema"? MonetDB uses the term "schema".
`String`	`getSearchStringEscape()` This is the string that can be used to escape '_' and '%' in a search string pattern style catalog search parameters
`String`	`getSQLKeywords()` Get a comma separated list of all a database's SQL keywords that are NOT also SQL:2003 keywords.
`int`	`getSQLStateType()` Indicates whether the SQLSTATEs returned by `SQLException.getSQLState` is X/Open (now known as Open Group) SQL CLI or SQL:2003.
`String`	`getStringFunctions()`
`ResultSet`	`getSuperTables(String catalog, String schemaPattern, String tableNamePattern)` Retrieves a description of the table hierarchies defined in a particular schema in this database.
`ResultSet`	`getSuperTypes(String catalog, String schemaPattern, String typeNamePattern)` Retrieves a description of the user-defined type (UDT) hierarchies defined in a particular schema in this database.
`String`	`getSystemFunctions()`
`ResultSet`	`getTablePrivileges(String catalog, String schemaPattern, String tableNamePattern)` Get a description of the access rights for each table available in a catalog.
`ResultSet`	`getTables(String catalog, String schemaPattern, String tableNamePattern, String[] types)` Retrieves a description of the tables available in the given catalog.
`ResultSet`	`getTableTypes()` Get the table types available in this database.
`String`	`getTimeDateFunctions()`
`ResultSet`	`getTypeInfo()` Get a description of all the SQL data types supported by this database.
`ResultSet`	`getUDTs(String catalog, String schemaPattern, String typeNamePattern, int[] types)` Retrieves a description of the user-defined types (UDTs) defined in a particular schema.
`String`	`getURL()` What is the URL for this database?
`String`	`getUserName()` What is our user name as known to the database?
`ResultSet`	`getVersionColumns(String catalog, String schema, String table)` Get a description of a table's columns that are automatically updated when any value in a row is updated.
`boolean`	`insertsAreDetected(int type)`
`boolean`	`isCatalogAtStart()` Does a catalog appear at the start of a qualified table name? (Otherwise it appears at the end).
`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? A JDBC Compliant driver always returns true
`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()` Retrieves whether NULL values are sorted high.
`boolean`	`nullsAreSortedLow()` Retrieves whether NULL values are sorted low.
`boolean`	`othersDeletesAreVisible(int i)`
`boolean`	`othersInsertsAreVisible(int type)`
`boolean`	`othersUpdatesAreVisible(int type)`
`boolean`	`ownDeletesAreVisible(int type)`
`boolean`	`ownInsertsAreVisible(int type)`
`boolean`	`ownUpdatesAreVisible(int type)`
`boolean`	`rowChangesAreDetected(int type)`
`boolean`	`rowChangesAreVisible(int type)`
`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()` Is "ALTER TABLE" with an add column supported?
`boolean`	`supportsAlterTableWithDropColumn()` Is "ALTER TABLE" with a drop column supported?
`boolean`	`supportsANSI92EntryLevelSQL()` Does this driver support the ANSI-92 entry level SQL grammar? All JDBC Compliant drivers must return true.
`boolean`	`supportsANSI92FullSQL()` Does this driver support the ANSI-92 full SQL grammar? Would be good if it was like that
`boolean`	`supportsANSI92IntermediateSQL()` Does this driver support the ANSI-92 intermediate level SQL grammar? probably not
`boolean`	`supportsBatchUpdates()` Indicates whether the driver supports 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()` Retrieves whether this database supports the JDBC scalar function CONVERT for the conversion of one JDBC type to another.
`boolean`	`supportsConvert(int fromType, int toType)` Retrieves whether this database supports the JDBC scalar function CONVERT for conversions between the JDBC types fromType and toType.
`boolean`	`supportsCoreSQLGrammar()` Does this driver support the Core ODBC SQL grammar.
`boolean`	`supportsCorrelatedSubqueries()` Are correlated subqueries supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsDataDefinitionAndDataManipulationTransactions()` Are both data definition and data manipulation transactions supported? Supposedly that data definition is like CREATE or ALTER TABLE yes it is.
`boolean`	`supportsDataManipulationTransactionsOnly()` Are only data manipulation statements within a transaction supported?
`boolean`	`supportsDifferentTableCorrelationNames()` If table correlation names are supported, are they restricted to be different from the names of the tables?
`boolean`	`supportsExpressionsInOrderBy()` Are expressions in "ORDER BY" lists supported? e.g.
`boolean`	`supportsExtendedSQLGrammar()` Does this driver support the Extended (Level 2) ODBC SQL grammar.
`boolean`	`supportsFullOuterJoins()` Are full nested outer joins supported?
`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? (MonetDB already supports the more difficult supportsGroupByUnrelated(), so this is a piece of cake)
`boolean`	`supportsGroupByUnrelated()` Can a "GROUP BY" clause use columns not in the SELECT?
`boolean`	`supportsIntegrityEnhancementFacility()` Is the SQL Integrity Enhancement Facility supported? Our best guess is that this means support for constraints
`boolean`	`supportsLikeEscapeClause()` Is the escape character in "LIKE" clauses supported? A JDBC compliant driver always returns true.
`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? A JDBC-Compliant driver will always return false.
`boolean`	`supportsMixedCaseQuotedIdentifiers()` 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.
`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?) This is the main idea behind the Connection, is it?
`boolean`	`supportsNamedParameters()` Retrieves whether this database supports named parameters to callable statements.
`boolean`	`supportsNonNullableColumns()` Can columns be defined as non-nullable.
`boolean`	`supportsOpenCursorsAcrossCommit()` ResultSet objects (cursors) are not closed upon explicit or implicit commit.
`boolean`	`supportsOpenCursorsAcrossRollback()` Same as above
`boolean`	`supportsOpenStatementsAcrossCommit()` Can statements remain open across commits? They may, but this driver cannot guarentee that.
`boolean`	`supportsOpenStatementsAcrossRollback()` Can statements remain open across rollbacks? They may, but this driver cannot guarentee that.
`boolean`	`supportsOrderByUnrelated()` Can an "ORDER BY" clause use columns not in the SELECT? MonetDB differs from SQL03 => true
`boolean`	`supportsOuterJoins()` Is some form of outer join supported?
`boolean`	`supportsPositionedDelete()` MonetDB doesn't support positioned DELETEs I guess
`boolean`	`supportsPositionedUpdate()` Is positioned UPDATE supported? (same as above)
`boolean`	`supportsResultSetConcurrency(int type, int concurrency)` Does the database support the concurrency type in combination with the given result set type?
`boolean`	`supportsResultSetHoldability(int holdability)` Retrieves whether this database supports the given result set holdability.
`boolean`	`supportsResultSetType(int type)` Does the database support the given result set type?
`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? Ohw probably, but I don't know of procedures in MonetDB
`boolean`	`supportsSchemasInTableDefinitions()` Can a schema be used in a table definition statement?
`boolean`	`supportsSelectForUpdate()` Is SELECT FOR UPDATE supported? My test resulted in a negative answer
`boolean`	`supportsStatementPooling()` Retrieves whether this database supports statement pooling.
`boolean`	`supportsStoredFunctionsUsingCallSyntax()` Retrieves whether this database supports invoking user-defined or vendor functions using the stored procedure escape syntax.
`boolean`	`supportsStoredProcedures()` Are stored procedure calls using the stored procedure escape syntax supported?
`boolean`	`supportsSubqueriesInComparisons()` Are subqueries in comparison expressions supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsSubqueriesInExists()` Are subqueries in 'exists' expressions supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsSubqueriesInIns()` Are subqueries in 'in' statements supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsSubqueriesInQuantifieds()` Are subqueries in quantified expressions supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsTableCorrelationNames()` Are table correlation names supported? A JDBC Compliant driver always returns true.
`boolean`	`supportsTransactionIsolationLevel(int level)` Does the database support the given transaction isolation level? We only support TRANSACTION_READ_COMMITTED as far as I know
`boolean`	`supportsTransactions()` Are transactions supported? If not, commit and rollback are noops and the isolation level is TRANSACTION_NONE.
`boolean`	`supportsUnion()` Is SQL UNION supported? since 2004-03-20
`boolean`	`supportsUnionAll()` Is SQL UNION ALL supported? since 2004-03-20
`boolean`	`updatesAreDetected(int type)`
`boolean`	`usesLocalFilePerTable()` Does the database use a local file for each table?
`boolean`	`usesLocalFiles()` Does the database store tables in a local file? No, it stores them in files on the server.

Methods inherited from class nl.cwi.monetdb.jdbc.MonetWrapper
isWrapperFor, unwrap

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface java.sql.DatabaseMetaData
getMaxLogicalLobSize, supportsRefCursors

Methods inherited from interface java.sql.Wrapper
isWrapperFor, unwrap

- Constructor Detail
  - MonetDatabaseMetaData
```
public MonetDatabaseMetaData(Connection parent)
```
- Method Detail
  - allProceduresAreCallable
```
public boolean allProceduresAreCallable()
```
    Can all the procedures returned by getProcedures be called by the current user?
    
    Specified by:
    
    allProceduresAreCallable in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - allTablesAreSelectable
```
public boolean allTablesAreSelectable()
```
    Can all the tables returned by getTable be SELECTed by the current user?
    
    Specified by:
    
    allTablesAreSelectable in interface DatabaseMetaData
    
    Returns:
    
    true because we only have one user a.t.m.
  - getURL
```
public String getURL()
              throws SQLException
```
    What is the URL for this database?
    
    Specified by:
    
    getURL in interface DatabaseMetaData
    
    Returns:
    
    a reconstructed connection string
    
    Throws:
    
    SQLException - if a database access error occurs
  - getUserName
```
public String getUserName()
                   throws SQLException
```
    What is our user name as known to the database?
    
    Specified by:
    
    getUserName in interface DatabaseMetaData
    
    Returns:
    
    sql user
    
    Throws:
    
    SQLException - if a database access error occurs
  - isReadOnly
```
public boolean isReadOnly()
```
    Is the database in read-only mode?
    
    Specified by:
    
    isReadOnly in interface DatabaseMetaData
    
    Returns:
    
    always false for now
  - nullsAreSortedHigh
```
public boolean nullsAreSortedHigh()
```
    Retrieves whether NULL values are sorted high. Sorted high means that NULL values sort higher than any other value in a domain. In an ascending order, if this method returns true, NULL values will appear at the end. By contrast, the method nullsAreSortedAtEnd indicates whether NULL values are sorted at the end regardless of sort order.
    
    Specified by:
    
    nullsAreSortedHigh in interface DatabaseMetaData
    
    Returns:
    
    false because MonetDB shows NULL values at the beginning upon ORDER BY .. ASC
  - nullsAreSortedLow
```
public boolean nullsAreSortedLow()
```
    Retrieves whether NULL values are sorted low. Sorted low means that NULL values sort lower than any other value in a domain. In an ascending order, if this method returns true, NULL values will appear at the beginning. By contrast, the method nullsAreSortedAtStart indicates whether NULL values are sorted at the beginning regardless of sort order.
    
    Specified by:
    
    nullsAreSortedLow in interface DatabaseMetaData
    
    Returns:
    
    true because MonetDB shows NULL values at the beginning upon ORDER BY .. ASC
    
    See Also:
    
    nullsAreSortedHigh()
  - nullsAreSortedAtStart
```
public boolean nullsAreSortedAtStart()
```
    Are NULL values sorted at the start regardless of sort order?
    
    Specified by:
    
    nullsAreSortedAtStart in interface DatabaseMetaData
    
    Returns:
    
    false, since MonetDB doesn't do this
  - nullsAreSortedAtEnd
```
public boolean nullsAreSortedAtEnd()
```
    Are NULL values sorted at the end regardless of sort order?
    
    Specified by:
    
    nullsAreSortedAtEnd in interface DatabaseMetaData
    
    Returns:
    
    false, since MonetDB doesn't do this
  - getDatabaseProductName
```
public String getDatabaseProductName()
```
    What is the name of this database product - this should be MonetDB of course, so we return that explicitly.
    
    Specified by:
    
    getDatabaseProductName in interface DatabaseMetaData
    
    Returns:
    
    the database product name
  - getDatabaseProductVersion
```
public String getDatabaseProductVersion()
                                 throws SQLException
```
    What is the version of this database product.
    
    Specified by:
    
    getDatabaseProductVersion in interface DatabaseMetaData
    
    Returns:
    
    the mserver5 version number string
    
    Throws:
    
    SQLException - if a database access error occurs
  - getDriverName
```
public String getDriverName()
```
    What is the name of this JDBC driver?
    
    Specified by:
    
    getDriverName in interface DatabaseMetaData
    
    Returns:
    
    the JDBC driver name
  - getDriverVersion
```
public String getDriverVersion()
```
    Retrieves the version number of this JDBC driver as a String.
    
    Specified by:
    
    getDriverVersion in interface DatabaseMetaData
    
    Returns:
    
    the JDBC driver version string
  - getDriverMajorVersion
```
public int getDriverMajorVersion()
```
    What is this JDBC driver's major version number?
    
    Specified by:
    
    getDriverMajorVersion in interface DatabaseMetaData
    
    Returns:
    
    the JDBC driver major version number
  - getDriverMinorVersion
```
public int getDriverMinorVersion()
```
    What is this JDBC driver's minor version number?
    
    Specified by:
    
    getDriverMinorVersion in interface DatabaseMetaData
    
    Returns:
    
    the JDBC driver minor version number
  - usesLocalFiles
```
public boolean usesLocalFiles()
```
    Does the database store tables in a local file? No, it stores them in files on the server.
    
    Specified by:
    
    usesLocalFiles in interface DatabaseMetaData
    
    Returns:
    
    false because that's what MonetDB is for
  - usesLocalFilePerTable
```
public boolean usesLocalFilePerTable()
```
    Does the database use a local file for each table?
    
    Specified by:
    
    usesLocalFilePerTable in interface DatabaseMetaData
    
    Returns:
    
    false for it doesn't
  - supportsMixedCaseIdentifiers
```
public boolean supportsMixedCaseIdentifiers()
```
    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.
    
    Specified by:
    
    supportsMixedCaseIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    false
  - storesUpperCaseIdentifiers
```
public boolean storesUpperCaseIdentifiers()
```
    Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in upper case?
    
    Specified by:
    
    storesUpperCaseIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - storesLowerCaseIdentifiers
```
public boolean storesLowerCaseIdentifiers()
```
    Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in lower case?
    
    Specified by:
    
    storesLowerCaseIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - storesMixedCaseIdentifiers
```
public boolean storesMixedCaseIdentifiers()
```
    Does the database treat mixed case unquoted SQL identifiers as case insensitive and store them in mixed case?
    
    Specified by:
    
    storesMixedCaseIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsMixedCaseQuotedIdentifiers
```
public boolean supportsMixedCaseQuotedIdentifiers()
```
    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.
    
    Specified by:
    
    supportsMixedCaseQuotedIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - storesUpperCaseQuotedIdentifiers
```
public boolean storesUpperCaseQuotedIdentifiers()
```
    Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in upper case?
    
    Specified by:
    
    storesUpperCaseQuotedIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - storesLowerCaseQuotedIdentifiers
```
public boolean storesLowerCaseQuotedIdentifiers()
```
    Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in lower case?
    
    Specified by:
    
    storesLowerCaseQuotedIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - storesMixedCaseQuotedIdentifiers
```
public boolean storesMixedCaseQuotedIdentifiers()
```
    Does the database treat mixed case quoted SQL identifiers as case insensitive and store them in mixed case?
    
    Specified by:
    
    storesMixedCaseQuotedIdentifiers in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - getIdentifierQuoteString
```
public String getIdentifierQuoteString()
```
    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.
    
    Specified by:
    
    getIdentifierQuoteString in interface DatabaseMetaData
    
    Returns:
    
    the quoting string
  - getSQLKeywords
```
public String getSQLKeywords()
```
    Get a comma separated list of all a database's SQL keywords that are NOT also SQL:2003 keywords.
    
    Specified by:
    
    getSQLKeywords in interface DatabaseMetaData
    
    Returns:
    
    a comma separated list of MonetDB keywords
  - getNumericFunctions
```
public String getNumericFunctions()
```
    Specified by:
    
    getNumericFunctions in interface DatabaseMetaData
  - getStringFunctions
```
public String getStringFunctions()
```
    Specified by:
    
    getStringFunctions in interface DatabaseMetaData
  - getSystemFunctions
```
public String getSystemFunctions()
```
    Specified by:
    
    getSystemFunctions in interface DatabaseMetaData
  - getTimeDateFunctions
```
public String getTimeDateFunctions()
```
    Specified by:
    
    getTimeDateFunctions in interface DatabaseMetaData
  - getSearchStringEscape
```
public String getSearchStringEscape()
```
    This is the string that can be used to escape '_' and '%' in a search string pattern style catalog search parameters
    
    Specified by:
    
    getSearchStringEscape in interface DatabaseMetaData
    
    Returns:
    
    the string used to escape wildcard characters
  - getExtraNameCharacters
```
public String getExtraNameCharacters()
```
    Get all the "extra" characters that can be used in unquoted identifier names (those beyond a-zA-Z0-9 and _) MonetDB has no extra characters (verified it for chars: !@#$%^&*()~{}[]?
    
    Specified by:
    
    getExtraNameCharacters in interface DatabaseMetaData
    
    Returns:
    
    a string containing the extra characters
  - supportsAlterTableWithAddColumn
```
public boolean supportsAlterTableWithAddColumn()
```
    Is "ALTER TABLE" with an add column supported?
    
    Specified by:
    
    supportsAlterTableWithAddColumn in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsAlterTableWithDropColumn
```
public boolean supportsAlterTableWithDropColumn()
```
    Is "ALTER TABLE" with a drop column supported?
    
    Specified by:
    
    supportsAlterTableWithDropColumn in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsColumnAliasing
```
public boolean supportsColumnAliasing()
```
    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 DatabaseMetaData
    
    Returns:
    
    true if so
  - nullPlusNonNullIsNull
```
public boolean nullPlusNonNullIsNull()
```
    Are concatenations between NULL and non-NULL values NULL? A JDBC Compliant driver always returns true
    
    Specified by:
    
    nullPlusNonNullIsNull in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsConvert
```
public boolean supportsConvert()
```
    Retrieves whether this database supports the JDBC scalar function CONVERT for the conversion of one JDBC type to another. The JDBC types are the generic SQL data types defined in java.sql.Types.
    
    Specified by:
    
    supportsConvert in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsConvert
```
public boolean supportsConvert(int fromType,
                               int toType)
```
    Retrieves whether this database supports the JDBC scalar function CONVERT for conversions between the JDBC types fromType and toType. The JDBC types are the generic SQL data types defined in java.sql.Types.
    
    Specified by:
    
    supportsConvert in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsTableCorrelationNames
```
public boolean supportsTableCorrelationNames()
```
    Are table correlation names supported? A JDBC Compliant driver always returns true.
    
    Specified by:
    
    supportsTableCorrelationNames in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsDifferentTableCorrelationNames
```
public boolean supportsDifferentTableCorrelationNames()
```
    If table correlation names are supported, are they restricted to be different from the names of the tables?
    
    Specified by:
    
    supportsDifferentTableCorrelationNames in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsExpressionsInOrderBy
```
public boolean supportsExpressionsInOrderBy()
```
    Are expressions in "ORDER BY" lists supported? e.g. select * from t order by a + b; MonetDB supports this, try: select (radix * 1000) + digits as comp, * from types order by (radix * 1000) + digits, -id;
    
    Specified by:
    
    supportsExpressionsInOrderBy in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsOrderByUnrelated
```
public boolean supportsOrderByUnrelated()
```
    Can an "ORDER BY" clause use columns not in the SELECT? MonetDB differs from SQL03 => true
    
    Specified by:
    
    supportsOrderByUnrelated in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsGroupBy
```
public boolean supportsGroupBy()
```
    Is some form of "GROUP BY" clause supported?
    
    Specified by:
    
    supportsGroupBy in interface DatabaseMetaData
    
    Returns:
    
    true since MonetDB supports it
  - supportsGroupByUnrelated
```
public boolean supportsGroupByUnrelated()
```
    Can a "GROUP BY" clause use columns not in the SELECT?
    
    Specified by:
    
    supportsGroupByUnrelated in interface DatabaseMetaData
    
    Returns:
    
    true since that also is supported
  - supportsGroupByBeyondSelect
```
public boolean supportsGroupByBeyondSelect()
```
    Can a "GROUP BY" clause add columns not in the SELECT provided it specifies all the columns in the SELECT? (MonetDB already supports the more difficult supportsGroupByUnrelated(), so this is a piece of cake)
    
    Specified by:
    
    supportsGroupByBeyondSelect in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsLikeEscapeClause
```
public boolean supportsLikeEscapeClause()
```
    Is the escape character in "LIKE" clauses supported? A JDBC compliant driver always returns true.
    
    Specified by:
    
    supportsLikeEscapeClause in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsMultipleResultSets
```
public boolean supportsMultipleResultSets()
```
    Are multiple ResultSets from a single execute supported?
    
    Specified by:
    
    supportsMultipleResultSets in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsMultipleTransactions
```
public boolean supportsMultipleTransactions()
```
    Can we have multiple transactions open at once (on different connections?) This is the main idea behind the Connection, is it?
    
    Specified by:
    
    supportsMultipleTransactions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsNonNullableColumns
```
public boolean supportsNonNullableColumns()
```
    Can columns be defined as non-nullable. A JDBC Compliant driver always returns true.
    
    Specified by:
    
    supportsNonNullableColumns in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsMinimumSQLGrammar
```
public boolean supportsMinimumSQLGrammar()
```
    Does this driver support the minimum ODBC SQL grammar. This grammar is defined at: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odappcpr.asp From this description, we seem to support the ODBC minimal (Level 0) grammar.
    
    Specified by:
    
    supportsMinimumSQLGrammar in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCoreSQLGrammar
```
public boolean supportsCoreSQLGrammar()
```
    Does this driver support the Core ODBC SQL grammar. We need SQL-92 conformance for this.
    
    Specified by:
    
    supportsCoreSQLGrammar in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsExtendedSQLGrammar
```
public boolean supportsExtendedSQLGrammar()
```
    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 DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsANSI92EntryLevelSQL
```
public boolean supportsANSI92EntryLevelSQL()
```
    Does this driver support the ANSI-92 entry level SQL grammar? All JDBC Compliant drivers must return true. We should be this compliant, so let's 'act' like we are.
    
    Specified by:
    
    supportsANSI92EntryLevelSQL in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsANSI92IntermediateSQL
```
public boolean supportsANSI92IntermediateSQL()
```
    Does this driver support the ANSI-92 intermediate level SQL grammar? probably not
    
    Specified by:
    
    supportsANSI92IntermediateSQL in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsANSI92FullSQL
```
public boolean supportsANSI92FullSQL()
```
    Does this driver support the ANSI-92 full SQL grammar? Would be good if it was like that
    
    Specified by:
    
    supportsANSI92FullSQL in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsIntegrityEnhancementFacility
```
public boolean supportsIntegrityEnhancementFacility()
```
    Is the SQL Integrity Enhancement Facility supported? Our best guess is that this means support for constraints
    
    Specified by:
    
    supportsIntegrityEnhancementFacility in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsOuterJoins
```
public boolean supportsOuterJoins()
```
    Is some form of outer join supported?
    
    Specified by:
    
    supportsOuterJoins in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsFullOuterJoins
```
public boolean supportsFullOuterJoins()
```
    Are full nested outer joins supported?
    
    Specified by:
    
    supportsFullOuterJoins in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsLimitedOuterJoins
```
public boolean supportsLimitedOuterJoins()
```
    Is there limited support for outer joins?
    
    Specified by:
    
    supportsLimitedOuterJoins in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - getSchemaTerm
```
public String getSchemaTerm()
```
    What is the database vendor's preferred term for "schema"? MonetDB uses the term "schema".
    
    Specified by:
    
    getSchemaTerm in interface DatabaseMetaData
    
    Returns:
    
    the vendor term
  - getProcedureTerm
```
public String getProcedureTerm()
```
    What is the database vendor's preferred term for "procedure"?
    
    Specified by:
    
    getProcedureTerm in interface DatabaseMetaData
    
    Returns:
    
    the vendor term
  - getCatalogTerm
```
public String getCatalogTerm()
```
    What is the database vendor's preferred term for "catalog"? MonetDB doesn't really have them (from driver accessible) but from the monetdb.conf file the term "database" sounds best
    
    Specified by:
    
    getCatalogTerm in interface DatabaseMetaData
    
    Returns:
    
    the vendor term
  - isCatalogAtStart
```
public boolean isCatalogAtStart()
```
    Does a catalog appear at the start of a qualified table name? (Otherwise it appears at the end). Currently there is no catalog support at all in MonetDB
    
    Specified by:
    
    isCatalogAtStart in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - getCatalogSeparator
```
public String getCatalogSeparator()
```
    What is the Catalog separator.
    
    Specified by:
    
    getCatalogSeparator in interface DatabaseMetaData
    
    Returns:
    
    the catalog separator string
  - supportsSchemasInDataManipulation
```
public boolean supportsSchemasInDataManipulation()
```
    Can a schema name be used in a data manipulation statement?
    
    Specified by:
    
    supportsSchemasInDataManipulation in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsSchemasInProcedureCalls
```
public boolean supportsSchemasInProcedureCalls()
```
    Can a schema name be used in a procedure call statement? Ohw probably, but I don't know of procedures in MonetDB
    
    Specified by:
    
    supportsSchemasInProcedureCalls in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsSchemasInTableDefinitions
```
public boolean supportsSchemasInTableDefinitions()
```
    Can a schema be used in a table definition statement?
    
    Specified by:
    
    supportsSchemasInTableDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsSchemasInIndexDefinitions
```
public boolean supportsSchemasInIndexDefinitions()
```
    Can a schema name be used in an index definition statement?
    
    Specified by:
    
    supportsSchemasInIndexDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsSchemasInPrivilegeDefinitions
```
public boolean supportsSchemasInPrivilegeDefinitions()
```
    Can a schema name be used in a privilege definition statement?
    
    Specified by:
    
    supportsSchemasInPrivilegeDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCatalogsInDataManipulation
```
public boolean supportsCatalogsInDataManipulation()
```
    Can a catalog name be used in a data manipulation statement?
    
    Specified by:
    
    supportsCatalogsInDataManipulation in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCatalogsInProcedureCalls
```
public boolean supportsCatalogsInProcedureCalls()
```
    Can a catalog name be used in a procedure call statement?
    
    Specified by:
    
    supportsCatalogsInProcedureCalls in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCatalogsInTableDefinitions
```
public boolean supportsCatalogsInTableDefinitions()
```
    Can a catalog name be used in a table definition statement?
    
    Specified by:
    
    supportsCatalogsInTableDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCatalogsInIndexDefinitions
```
public boolean supportsCatalogsInIndexDefinitions()
```
    Can a catalog name be used in an index definition?
    
    Specified by:
    
    supportsCatalogsInIndexDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsCatalogsInPrivilegeDefinitions
```
public boolean supportsCatalogsInPrivilegeDefinitions()
```
    Can a catalog name be used in a privilege definition statement?
    
    Specified by:
    
    supportsCatalogsInPrivilegeDefinitions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsPositionedDelete
```
public boolean supportsPositionedDelete()
```
    MonetDB doesn't support positioned DELETEs I guess
    
    Specified by:
    
    supportsPositionedDelete in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsPositionedUpdate
```
public boolean supportsPositionedUpdate()
```
    Is positioned UPDATE supported? (same as above)
    
    Specified by:
    
    supportsPositionedUpdate in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsSelectForUpdate
```
public boolean supportsSelectForUpdate()
```
    Is SELECT FOR UPDATE supported? My test resulted in a negative answer
    
    Specified by:
    
    supportsSelectForUpdate in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsStoredProcedures
```
public boolean supportsStoredProcedures()
```
    Are stored procedure calls using the stored procedure escape syntax supported?
    
    Specified by:
    
    supportsStoredProcedures in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsSubqueriesInComparisons
```
public boolean supportsSubqueriesInComparisons()
```
    Are subqueries in comparison expressions supported? A JDBC Compliant driver always returns true. MonetDB also supports this
    
    Specified by:
    
    supportsSubqueriesInComparisons in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsSubqueriesInExists
```
public boolean supportsSubqueriesInExists()
```
    Are subqueries in 'exists' expressions supported? A JDBC Compliant driver always returns true.
    
    Specified by:
    
    supportsSubqueriesInExists in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsSubqueriesInIns
```
public boolean supportsSubqueriesInIns()
```
    Are subqueries in 'in' statements supported? A JDBC Compliant driver always returns true.
    
    Specified by:
    
    supportsSubqueriesInIns in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsSubqueriesInQuantifieds
```
public boolean supportsSubqueriesInQuantifieds()
```
    Are subqueries in quantified expressions supported? A JDBC Compliant driver always returns true. (No idea what this is, but we support a good deal of subquerying.)
    
    Specified by:
    
    supportsSubqueriesInQuantifieds in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsCorrelatedSubqueries
```
public boolean supportsCorrelatedSubqueries()
```
    Are correlated subqueries supported? A JDBC Compliant driver always returns true. (a.k.a. subselect in from?)
    
    Specified by:
    
    supportsCorrelatedSubqueries in interface DatabaseMetaData
    
    Returns:
    
    true if so; false otherwise
  - supportsUnion
```
public boolean supportsUnion()
```
    Is SQL UNION supported? since 2004-03-20
    
    Specified by:
    
    supportsUnion in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsUnionAll
```
public boolean supportsUnionAll()
```
    Is SQL UNION ALL supported? since 2004-03-20
    
    Specified by:
    
    supportsUnionAll in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsOpenCursorsAcrossCommit
```
public boolean supportsOpenCursorsAcrossCommit()
```
    ResultSet objects (cursors) are not closed upon explicit or implicit commit.
    
    Specified by:
    
    supportsOpenCursorsAcrossCommit in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsOpenCursorsAcrossRollback
```
public boolean supportsOpenCursorsAcrossRollback()
```
    Same as above
    
    Specified by:
    
    supportsOpenCursorsAcrossRollback in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsOpenStatementsAcrossCommit
```
public boolean supportsOpenStatementsAcrossCommit()
```
    Can statements remain open across commits? They may, but this driver cannot guarentee that. In further reflection. we are taking a Statement object here, so the answer is yes, since the Statement is only a vehicle to execute some SQL
    
    Specified by:
    
    supportsOpenStatementsAcrossCommit in interface DatabaseMetaData
    
    Returns:
    
    true if they always remain open; false otherwise
  - supportsOpenStatementsAcrossRollback
```
public boolean supportsOpenStatementsAcrossRollback()
```
    Can statements remain open across rollbacks? They may, but this driver cannot guarentee that. In further contemplation, we are taking a Statement object here, so the answer is yes again.
    
    Specified by:
    
    supportsOpenStatementsAcrossRollback in interface DatabaseMetaData
    
    Returns:
    
    true if they always remain open; false otherwise
  - getMaxBinaryLiteralLength
```
public int getMaxBinaryLiteralLength()
```
    How many hex characters can you have in an inline binary literal
    
    Specified by:
    
    getMaxBinaryLiteralLength in interface DatabaseMetaData
    
    Returns:
    
    the max literal length
  - getMaxCharLiteralLength
```
public int getMaxCharLiteralLength()
```
    What is the maximum length for a character literal
    
    Specified by:
    
    getMaxCharLiteralLength in interface DatabaseMetaData
    
    Returns:
    
    the max literal length
  - getMaxColumnNameLength
```
public int getMaxColumnNameLength()
```
    Whats the limit on column name length. I take some safety here, but it's just a varchar in MonetDB
    
    Specified by:
    
    getMaxColumnNameLength in interface DatabaseMetaData
    
    Returns:
    
    the maximum column name length
  - getMaxColumnsInGroupBy
```
public int getMaxColumnsInGroupBy()
```
    What is the maximum number of columns in a "GROUP BY" clause?
    
    Specified by:
    
    getMaxColumnsInGroupBy in interface DatabaseMetaData
    
    Returns:
    
    the max number of columns
  - getMaxColumnsInIndex
```
public int getMaxColumnsInIndex()
```
    What's the maximum number of columns allowed in an index?
    
    Specified by:
    
    getMaxColumnsInIndex in interface DatabaseMetaData
    
    Returns:
    
    max number of columns
  - getMaxColumnsInOrderBy
```
public int getMaxColumnsInOrderBy()
```
    What's the maximum number of columns in an "ORDER BY clause?
    
    Specified by:
    
    getMaxColumnsInOrderBy in interface DatabaseMetaData
    
    Returns:
    
    the max columns
  - getMaxColumnsInSelect
```
public int getMaxColumnsInSelect()
```
    What is the maximum number of columns in a "SELECT" list?
    
    Specified by:
    
    getMaxColumnsInSelect in interface DatabaseMetaData
    
    Returns:
    
    the max columns
  - getMaxColumnsInTable
```
public int getMaxColumnsInTable()
```
    What is the maximum number of columns in a table? The theoretical max value of int column sys._columns.id is 2^31 -1 but this is for all columns of all tables in all schemas (including all data dictionary columns). For one table we should reduce it to a more practical soft limit of say 100 thousand
    
    Specified by:
    
    getMaxColumnsInTable in interface DatabaseMetaData
    
    Returns:
    
    the max columns
  - getMaxConnections
```
public int getMaxConnections()
                      throws SQLException
```
    How many active connections can we have at a time to this database? Well, since it depends on Mserver, which just listens for new connections and creates a new thread for each connection, this number can be very high, and theoretically till the system runs out of resources. However, knowing MonetDB is knowing that you should handle it a little bit with care, so I give a very minimalistic number here.
    
    Specified by:
    
    getMaxConnections in interface DatabaseMetaData
    
    Returns:
    
    the maximum number of connections
    
    Throws:
    
    SQLException
  - getMaxCursorNameLength
```
public int getMaxCursorNameLength()
```
    What is the maximum cursor name length Actually we do not do named cursors, so I keep the value small as a precaution for maybe the future.
    
    Specified by:
    
    getMaxCursorNameLength in interface DatabaseMetaData
    
    Returns:
    
    max cursor name length in bytes
  - getMaxIndexLength
```
public int getMaxIndexLength()
```
    Retrieves the maximum number of bytes for an index, including all of the parts of the index.
    
    Specified by:
    
    getMaxIndexLength in interface DatabaseMetaData
    
    Returns:
    
    max index length in bytes, which includes the composite of all the constituent parts of the index; a result of zero means that there is no limit or the limit is not known
  - getMaxSchemaNameLength
```
public int getMaxSchemaNameLength()
```
    Retrieves the maximum number of characters that this database allows in a schema name.
    
    Specified by:
    
    getMaxSchemaNameLength in interface DatabaseMetaData
    
    Returns:
    
    the number of characters or 0 if there is no limit, or the limit is unknown.
  - getMaxProcedureNameLength
```
public int getMaxProcedureNameLength()
```
    What is the maximum length of a procedure name
    
    Specified by:
    
    getMaxProcedureNameLength in interface DatabaseMetaData
    
    Returns:
    
    the max name length in bytes
  - getMaxCatalogNameLength
```
public int getMaxCatalogNameLength()
```
    What is the maximum length of a catalog
    
    Specified by:
    
    getMaxCatalogNameLength in interface DatabaseMetaData
    
    Returns:
    
    the maximum number of characters allowed in a catalog name; a result of zero means that there is no limit or the limit is not known
  - getMaxRowSize
```
public int getMaxRowSize()
```
    What is the maximum length of a single row?
    
    Specified by:
    
    getMaxRowSize in interface DatabaseMetaData
    
    Returns:
    
    max row size in bytes
  - doesMaxRowSizeIncludeBlobs
```
public boolean doesMaxRowSizeIncludeBlobs()
```
    Did getMaxRowSize() include the SQL data types LONGVARCHAR and LONGVARBINARY blobs? Yes I thought so...
    
    Specified by:
    
    doesMaxRowSizeIncludeBlobs in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - getMaxStatementLength
```
public int getMaxStatementLength()
```
    What is the maximum length of a SQL statement?
    
    Specified by:
    
    getMaxStatementLength in interface DatabaseMetaData
    
    Returns:
    
    max length in bytes
  - getMaxStatements
```
public int getMaxStatements()
```
    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.
    
    Specified by:
    
    getMaxStatements in interface DatabaseMetaData
    
    Returns:
    
    the maximum
  - getMaxTableNameLength
```
public int getMaxTableNameLength()
```
    What is the maximum length of a table name
    
    Specified by:
    
    getMaxTableNameLength in interface DatabaseMetaData
    
    Returns:
    
    max name length in bytes
  - getMaxTablesInSelect
```
public int getMaxTablesInSelect()
```
    What is the maximum number of tables that can be specified in a SELECT?
    
    Specified by:
    
    getMaxTablesInSelect in interface DatabaseMetaData
    
    Returns:
    
    the maximum
  - getMaxUserNameLength
```
public int getMaxUserNameLength()
```
    What is the maximum length of a user name
    
    Specified by:
    
    getMaxUserNameLength in interface DatabaseMetaData
    
    Returns:
    
    the max name length in bytes
  - getDefaultTransactionIsolation
```
public int getDefaultTransactionIsolation()
```
    What is the database's default transaction isolation level? We only see commited data, nonrepeatable reads and phantom reads can occur.
    
    Specified by:
    
    getDefaultTransactionIsolation in interface DatabaseMetaData
    
    Returns:
    
    the default isolation level
    
    See Also:
    
    Connection
  - supportsTransactions
```
public boolean supportsTransactions()
```
    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 DatabaseMetaData
    
    Returns:
    
    true if transactions are supported
  - supportsTransactionIsolationLevel
```
public boolean supportsTransactionIsolationLevel(int level)
```
    Does the database support the given transaction isolation level? We only support TRANSACTION_READ_COMMITTED as far as I know
    
    Specified by:
    
    supportsTransactionIsolationLevel in interface DatabaseMetaData
    
    Parameters:
    
    level - the values are defined in java.sql.Connection
    
    Returns:
    
    true if so
    
    See Also:
    
    Connection
  - supportsDataDefinitionAndDataManipulationTransactions
```
public boolean supportsDataDefinitionAndDataManipulationTransactions()
```
    Are both data definition and data manipulation transactions supported? Supposedly that data definition is like CREATE or ALTER TABLE yes it is.
    
    Specified by:
    
    supportsDataDefinitionAndDataManipulationTransactions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - supportsDataManipulationTransactionsOnly
```
public boolean supportsDataManipulationTransactionsOnly()
```
    Are only data manipulation statements within a transaction supported?
    
    Specified by:
    
    supportsDataManipulationTransactionsOnly in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - dataDefinitionCausesTransactionCommit
```
public boolean dataDefinitionCausesTransactionCommit()
```
    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 DatabaseMetaData
    
    Returns:
    
    true if so
  - dataDefinitionIgnoredInTransactions
```
public boolean dataDefinitionIgnoredInTransactions()
```
    Is a data definition statement within a transaction ignored?
    
    Specified by:
    
    dataDefinitionIgnoredInTransactions in interface DatabaseMetaData
    
    Returns:
    
    true if so
  - getProcedures
```
public ResultSet getProcedures(String catalog,
                               String schemaPattern,
                               String procedureNamePattern)
                        throws SQLException
```
    Get a description of stored procedures available in a catalog
    Only procedure descriptions matching the schema and procedure name criteria are returned. They are ordered by PROCEDURE_SCHEM, PROCEDURE_NAME and SPECIFIC_NAME.
    Each procedure description has the following columns:
    1. PROCEDURE_CAT String => procedure catalog (may be null)
    2. PROCEDURE_SCHEM String => procedure schema (may be null)
    3. PROCEDURE_NAME String => procedure name
    4. Field4 reserved (make it null)
    5. Field5 reserved (make it null)
    6. Field6 reserved (make it null)
    7. REMARKS String => explanatory comment on the procedure
    8. PROCEDURE_TYPE short => kind of procedure
      
      procedureResultUnknown - May return a result
      procedureNoResult - Does not return a result
      procedureReturnsResult - Returns a result
  - SPECIFIC_NAME String => The name which uniquely identifies this procedure within its schema.

Specified by:: getProcedures in interface 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; procedureNamePattern - - a procedure name pattern; must match the procedure name as it is stored in the database
Returns:: ResultSet - each row is a procedure description
Throws:: SQLException - if a database access error occurs

getProcedureColumns
```
public ResultSet getProcedureColumns(String catalog,
                                     String schemaPattern,
                                     String procedureNamePattern,
                                     String columnNamePattern)
                              throws SQLException
```
Get a description of a catalog's stored procedure parameters and result columns.
Only descriptions matching the schema, procedure and parameter name criteria are returned. They are ordered by PROCEDURE_SCHEM, PROCEDURE_NAME and SPECIFIC_NAME. Within this, the return value, if any, is first. Next are the parameter descriptions in call order. The column descriptions follow in column number order.
Each row in the ResultSet is a parameter description or column description with the following fields:
1. PROCEDURE_CAT String => procedure catalog (may be null)
2. PROCEDURE_SCHEM String => procedure schema (may be null)
3. PROCEDURE_NAME String => procedure name
4. COLUMN_NAME String => column/parameter name
5. COLUMN_TYPE Short => kind of column/parameter:
  - procedureColumnUnknown - nobody knows
  - procedureColumnIn - IN parameter
  - procedureColumnInOut - INOUT parameter
  - procedureColumnOut - OUT parameter
  - procedureColumnReturn - procedure return value
  - procedureColumnResult - result column in ResultSet
6. DATA_TYPE int => SQL type from java.sql.Types
7. TYPE_NAME String => SQL type name, for a UDT type the type name is fully qualified
8. PRECISION int => precision
9. LENGTH int => length in bytes of data
10. SCALE short => scale - null is returned for data types where SCALE is not applicable.
11. RADIX short => radix
12. NULLABLE short => can it contain NULL?
  - procedureNoNulls - does not allow NULL values
  - procedureNullable - allows NULL values
  - procedureNullableUnknown - nullability unknown
13. REMARKS String => comment describing parameter/column
14. COLUMN_DEF String => default value for the column, which should be interpreted as a string when the value is enclosed in single quotes (may be null) The string NULL (not enclosed in quotes) - if NULL was specified as the default value TRUNCATE (not enclosed in quotes) - if the specified default value cannot be represented without truncation NULL - if a default value was not specified
15. SQL_DATA_TYPE int => reserved for future use
16. SQL_DATETIME_SUB int => reserved for future use
17. CHAR_OCTET_LENGTH int => the maximum length of binary and character based columns. For any other datatype the returned value is a NULL
18. ORDINAL_POSITION int => the ordinal position, starting from 1, for the input and output parameters for a procedure. A value of 0 is returned if this row describes the procedure's return value. For result set columns, it is the ordinal position of the column in the result set starting from 1. If there are multiple result sets, the column ordinal positions are implementation defined.
19. IS_NULLABLE String => ISO rules are used to determine the nullability for a column.
  - YES --- if the parameter can include NULLs
  - NO --- if the parameter cannot include NULLs
  - empty string --- if the nullability for the parameter is unknown
20. SPECIFIC_NAME String => the name which uniquely identifies this procedure within its schema.
Specified by:

getProcedureColumns in interface 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

procedureNamePattern - - a procedure name pattern; must match the procedure name as it is stored in the database

columnNamePattern - - a column name pattern; must match the column name as it is stored in the database

Returns:

ResultSet - each row describes a stored procedure parameter or column

Throws:

SQLException - if a database-access error occurs

See Also:

getSearchStringEscape()

getTables
```
public ResultSet getTables(String catalog,
                           String schemaPattern,
                           String tableNamePattern,
                           String[] types)
                    throws SQLException
```
Retrieves a description of the tables available in the given catalog. Only table descriptions matching the catalog, schema, table name and type criteria are returned. They are ordered by TABLE_TYPE, TABLE_CAT, TABLE_SCHEM and TABLE_NAME.
Each table description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. TABLE_TYPE String => table type. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", "GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", "SYNONYM".
5. REMARKS String => explanatory comment on the table
6. TYPE_CAT String => the types catalog (may be null)
7. TYPE_SCHEM String => the types schema (may be null)
8. TYPE_NAME String => type name (may be null)
9. SELF_REFERENCING_COL_NAME String => name of the designated "identifier" column of a typed table (may be null)
10. REF_GENERATION String => specifies how values in SELF_REFERENCING_COL_NAME are created. Values are "SYSTEM", "USER", "DERIVED". (may be null)
Specified by:

getTables in interface 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

tableNamePattern - - a table name pattern; must match the table name as it is stored in the database For all tables this should be "%"

types - - a list of table types, which must be from the list of table types returned from getTableTypes(),to include; null returns all types

Returns:

ResultSet - each row is a table description

Throws:

SQLException - if a database-access error occurs.

getSchemas
```
public ResultSet getSchemas(String catalog,
                            String schemaPattern)
                     throws SQLException
```
Get the schema names available in this database. The results are ordered by schema name.
The schema column is:
1. TABLE_SCHEM String => schema name
2. TABLE_CATALOG String => catalog name (may be null)
Specified by:

getSchemas in interface 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 catalog name should not be used to narrow down the search.

schemaPattern - a schema name; must match the schema name as it is stored in the database; null means schema name should not be used to narrow down the search.

Returns:

ResultSet each row has a single String column that is a schema name

Throws:

SQLException - if a database error occurs

getCatalogs
```
public ResultSet getCatalogs()
                      throws SQLException
```
Get the catalog names available in this database. The results are ordered by catalog name.
The catalog column is:
1. TABLE_CAT String => catalog name
Specified by:

getCatalogs in interface DatabaseMetaData

Returns:

ResultSet each row has a single String column that is a catalog name

Throws:

SQLException - if a database error occurs

getTableTypes
```
public ResultSet getTableTypes()
                        throws SQLException
```
Get the table types available in this database. The results are ordered by table type.
The table type is:
1. TABLE_TYPE String => table type. Typical types are "TABLE", "VIEW", "SYSTEM TABLE", "GLOBAL TEMPORARY", "LOCAL TEMPORARY", "ALIAS", "SYNONYM".
Specified by:

getTableTypes in interface DatabaseMetaData

Returns:

ResultSet each row has a single String column that is a table type

Throws:

SQLException - if a database error occurs

getColumns
```
public ResultSet getColumns(String catalog,
                            String schemaPattern,
                            String tableNamePattern,
                            String columnNamePattern)
                     throws SQLException
```
Get a description of table columns available in a catalog.
Only column descriptions matching the catalog, schema, table and column name criteria are returned. They are ordered by TABLE_SCHEM, TABLE_NAME and ORDINAL_POSITION.
Each column description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. COLUMN_NAME String => column name
5. DATA_TYPE int => SQL type from java.sql.Types
6. TYPE_NAME String => Data source dependent type name
7. COLUMN_SIZE int => column size. For char or date types this is the maximum number of characters, for numeric or decimal types this is precision.
8. BUFFER_LENGTH is not used.
9. DECIMAL_DIGITS int => the number of fractional digits
10. NUM_PREC_RADIX int => Radix (typically either 10 or 2)
11. NULLABLE int => is NULL allowed?
  - columnNoNulls - might not allow NULL values
  - columnNullable - definitely allows NULL values
  - columnNullableUnknown - nullability unknown
12. REMARKS String => comment describing column (may be null)
13. COLUMN_DEF String => default value (may be null)
14. SQL_DATA_TYPE int => unused
15. SQL_DATETIME_SUB int => unused
16. CHAR_OCTET_LENGTH int => for char types the maximum number of bytes in the column
17. ORDINAL_POSITION int => index of column in table (starting at 1)
18. IS_NULLABLE String => "NO" means column definitely does not allow NULL values; "YES" means the column might allow NULL values. An empty string means nobody knows.
19. SCOPE_CATALOG String => catalog of table that is the scope of a reference attribute (null if DATA_TYPE isn't REF)
20. SCOPE_SCHEMA String => schema of table that is the scope of a reference attribute (null if the DATA_TYPE isn't REF)
21. SCOPE_TABLE String => table name that this the scope of a reference attribute (null if the DATA_TYPE isn't REF)
22. 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)
23. IS_AUTOINCREMENT String => Indicates whether this column is auto incremented
  - YES --- if the column is auto incremented
  - NO --- if the column is not auto incremented
  - empty string --- if it cannot be determined whether the column is auto incremented
24. IS_GENERATEDCOLUMN String => Indicates whether this is a generated column
  - YES --- if this a generated column
  - NO --- if this not a generated column
  - empty string --- if it cannot be determined whether this is a generated column
Specified by:

getColumns in interface 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

tableNamePattern - - a table name pattern; must match the table name as it is stored in the database For all tables this should be "%"

columnNamePattern - - a column name pattern; must match the column name as it is stored in the database

Returns:

ResultSet - each row is a column description

Throws:

SQLException - if a database error occurs

See Also:

getSearchStringEscape()

getColumnPrivileges
```
public ResultSet getColumnPrivileges(String catalog,
                                     String schemaPattern,
                                     String tableNamePattern,
                                     String columnNamePattern)
                              throws SQLException
```
Get a description of the access rights for a table's columns. MonetDB doesn't have this level of access rights.
Only privileges matching the column name criteria are returned. They are ordered by COLUMN_NAME and PRIVILEGE.
Each privilige description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. COLUMN_NAME String => column name
5. GRANTOR => grantor of access (may be null)
6. GRANTEE String => grantee of access
7. PRIVILEGE String => name of access (SELECT, INSERT, UPDATE, REFRENCES, ...)
8. IS_GRANTABLE String => "YES" if grantee is permitted to grant to others; "NO" if not; null if unknown
Specified by:

getColumnPrivileges in interface DatabaseMetaData

Parameters:

catalog - a catalog name; "" retrieves those without a catalog

schemaPattern - a schema name; "" retrieves those without a schema

tableNamePattern - a table name

columnNamePattern - a column name pattern

Returns:

ResultSet each row is a column privilege description

Throws:

SQLException - if a database error occurs

See Also:

getSearchStringEscape()

getTablePrivileges
```
public ResultSet getTablePrivileges(String catalog,
                                    String schemaPattern,
                                    String tableNamePattern)
                             throws SQLException
```
Get a description of the access rights for each table available in a catalog.
Only privileges matching the schema and table name criteria are returned. They are ordered by TABLE_SCHEM, TABLE_NAME, and PRIVILEGE.
Each privilege description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. GRANTOR => grantor of access (may be null)
5. GRANTEE String => grantee of access
6. PRIVILEGE String => name of access (SELECT, INSERT, UPDATE, REFRENCES, ...)
7. IS_GRANTABLE String => "YES" if grantee is permitted to grant to others; "NO" if not; null if unknown
Specified by:

getTablePrivileges in interface 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

Returns:

ResultSet each row is a table privilege description

Throws:

SQLException - if a database error occurs

See Also:

getSearchStringEscape()

getBestRowIdentifier
```
public ResultSet getBestRowIdentifier(String catalog,
                                      String schema,
                                      String table,
                                      int scope,
                                      boolean nullable)
                               throws SQLException
```
Get a description of a table's optimal set of columns that uniquely identifies a row. They are ordered by SCOPE.
Each column description has the following columns:
1. SCOPE short => actual scope of result
  - bestRowTemporary - very temporary, while using row
  - bestRowTransaction - valid for remainder of current transaction
  - bestRowSession - valid for remainder of current session
2. COLUMN_NAME String => column name
3. DATA_TYPE int => SQL data type from java.sql.Types
4. TYPE_NAME String => Data source dependent type name
5. COLUMN_SIZE int => precision
6. BUFFER_LENGTH int => not used
7. DECIMAL_DIGITS short => scale
8. PSEUDO_COLUMN short => is this a pseudo column like an Oracle ROWID
  - bestRowUnknown - may or may not be pseudo column
  - bestRowNotPseudo - is NOT a pseudo column
  - bestRowPseudo - is a pseudo column
Specified by:

getBestRowIdentifier in interface 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:

SQLException - if a database error occurs

getVersionColumns
```
public ResultSet getVersionColumns(String catalog,
                                   String schema,
                                   String table)
                            throws SQLException
```
Get a description of a table's columns that are automatically updated when any value in a row is updated. They are unordered.
Each column description has the following columns:
1. SCOPE short => is not used
2. COLUMN_NAME String => column name
3. DATA_TYPE int => SQL data type from java.sql.Types
4. TYPE_NAME String => Data source dependent type name
5. COLUMN_SIZE int => precision
6. BUFFER_LENGTH int => length of column value in bytes
7. DECIMAL_DIGITS short => scale
8. PSEUDO_COLUMN short => is this a pseudo column like an Oracle ROWID
  - versionColumnUnknown - may or may not be pseudo column
  - versionColumnNotPseudo - is NOT a pseudo column
  - versionColumnPseudo - is a pseudo column
Specified by:

getVersionColumns in interface 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:

ResultSet each row is a column description

Throws:

SQLException - if a database error occurs

getPrimaryKeys
```
public ResultSet getPrimaryKeys(String catalog,
                                String schema,
                                String table)
                         throws SQLException
```
Get a description of a table's primary key columns. They are ordered by COLUMN_NAME.
Each column description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. COLUMN_NAME String => column name
5. KEY_SEQ short => sequence number within primary key
6. PK_NAME String => primary key name (may be null)
Specified by:

getPrimaryKeys in interface 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:

ResultSet each row is a primary key column description

Throws:

SQLException - if a database error occurs

getImportedKeys
```
public ResultSet getImportedKeys(String catalog,
                                 String schema,
                                 String table)
                          throws SQLException
```
Get a description of the primary key columns that are referenced by a table's foreign key columns (the primary keys imported by a table). They are ordered by PKTABLE_CAT, PKTABLE_SCHEM, PKTABLE_NAME, and KEY_SEQ.
Each primary key column description has the following columns:
1. PKTABLE_CAT String => primary key table catalog being imported (may be null)
2. PKTABLE_SCHEM String => primary key table schema being imported (may be null)
3. PKTABLE_NAME String => primary key table name being imported
4. PKCOLUMN_NAME String => primary key column name being imported
5. FKTABLE_CAT String => foreign key table catalog (may be null)
6. FKTABLE_SCHEM String => foreign key table schema (may be null)
7. FKTABLE_NAME String => foreign key table name
8. FKCOLUMN_NAME String => foreign key column name
9. KEY_SEQ short => sequence number within foreign key (a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key).
10. UPDATE_RULE short => What happens to foreign key when primary is updated:
  - importedKeyNoAction - do not allow update of primary key if it has been imported
  - importedKeyCascade - change imported key to agree with primary key update
  - importedKeyRestrict - do not allow update of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been updated
11. DELETE_RULE short => What happens to the foreign key when primary is deleted.
  - importedKeyNoAction - do not allow delete of primary key if it has been imported
  - importedKeyCascade - delete rows that import a deleted key
  - importedKeyRestrict - do not allow delete of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been deleted
12. FK_NAME String => foreign key name (may be null)
13. PK_NAME String => primary key name (may be null)
14. DEFERRABILITY short => can the evaluation of foreign key constraints be deferred until commit
  - importedKeyInitiallyDeferred - see SQL92 for definition
  - importedKeyInitiallyImmediate - see SQL92 for definition
  - importedKeyNotDeferrable - see SQL92 for definition
Specified by:

getImportedKeys in interface 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:

ResultSet each row is a primary key column description

Throws:

SQLException - if a database error occurs

See Also:

getExportedKeys(java.lang.String, java.lang.String, java.lang.String)

getExportedKeys
```
public ResultSet getExportedKeys(String catalog,
                                 String schema,
                                 String table)
                          throws SQLException
```
Get a description of a foreign key columns that reference a table's primary key columns (the foreign keys exported by a table). They are ordered by FKTABLE_CAT, FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ.
Each foreign key column description has the following columns:
1. PKTABLE_CAT String => primary key table catalog (may be null)
2. PKTABLE_SCHEM String => primary key table schema (may be null)
3. PKTABLE_NAME String => primary key table name
4. PKCOLUMN_NAME String => primary key column name
5. FKTABLE_CAT String => foreign key table catalog (may be null) being exported (may be null)
6. FKTABLE_SCHEM String => foreign key table schema (may be null) being exported (may be null)
7. FKTABLE_NAME String => foreign key table name being exported
8. FKCOLUMN_NAME String => foreign key column name being exported
9. KEY_SEQ short => sequence number within foreign key (a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key).
10. UPDATE_RULE short => What happens to foreign key when primary is updated:
  - importedKeyNoAction - do not allow update of primary key if it has been imported
  - importedKeyCascade - change imported key to agree with primary key update
  - importedKeyRestrict - do not allow update of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been updated
11. DELETE_RULE short => What happens to the foreign key when primary is deleted.
  - importedKeyNoAction - do not allow delete of primary key if it has been imported
  - importedKeyCascade - delete rows that import a deleted key
  - importedKeyRestrict - do not allow delete of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been deleted
12. FK_NAME String => foreign key identifier (may be null)
13. PK_NAME String => primary key identifier (may be null)
14. DEFERRABILITY short => can the evaluation of foreign key constraints be deferred until commit
  - importedKeyInitiallyDeferred - see SQL92 for definition
  - importedKeyInitiallyImmediate - see SQL92 for definition
  - importedKeyNotDeferrable - see SQL92 for definition
Specified by:

getExportedKeys in interface 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:

ResultSet each row is a foreign key column description

Throws:

SQLException - if a database error occurs

See Also:

getImportedKeys(java.lang.String, java.lang.String, java.lang.String)

getCrossReference
```
public ResultSet getCrossReference(String pcatalog,
                                   String pschema,
                                   String ptable,
                                   String fcatalog,
                                   String fschema,
                                   String ftable)
                            throws SQLException
```
Get a description of the foreign key columns in the foreign key table that reference the primary key columns of the primary key table. (describe how one table imports another's key) This should normally return a single foreign key/primary key pair (most tables only import a foreign key from a table once.) They are ordered by FKTABLE_CAT, FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ.
Each foreign key column description has the following columns:
1. PKTABLE_CAT String => primary key table catalog (may be null)
2. PKTABLE_SCHEM String => primary key table schema (may be null)
3. PKTABLE_NAME String => primary key table name
4. PKCOLUMN_NAME String => primary key column name
5. FKTABLE_CAT String => foreign key table catalog (may be null) being exported (may be null)
6. FKTABLE_SCHEM String => foreign key table schema (may be null) being exported (may be null)
7. FKTABLE_NAME String => foreign key table name being exported
8. FKCOLUMN_NAME String => foreign key column name being exported
9. KEY_SEQ short => sequence number within foreign key (a value of 1 represents the first column of the foreign key, a value of 2 would represent the second column within the foreign key).
10. UPDATE_RULE short => What happens to foreign key when primary is updated:
  - importedKeyNoAction - do not allow update of primary key if it has been imported
  - importedKeyCascade - change imported key to agree with primary key update
  - importedKeyRestrict - do not allow update of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been updated
11. DELETE_RULE short => What happens to the foreign key when primary is deleted.
  - importedKeyNoAction - do not allow delete of primary key if it has been imported
  - importedKeyCascade - delete rows that import a deleted key
  - importedKeyRestrict - do not allow delete of primary key if it has been imported
  - importedKeySetNull - change imported key to NULL if its primary key has been deleted
12. FK_NAME String => foreign key identifier (may be null)
13. PK_NAME String => primary key identifier (may be null)
14. DEFERRABILITY short => can the evaluation of foreign key constraints be deferred until commit
  - importedKeyInitiallyDeferred - see SQL92 for definition
  - importedKeyInitiallyImmediate - see SQL92 for definition
  - importedKeyNotDeferrable - see SQL92 for definition
Specified by:

getCrossReference in interface DatabaseMetaData

Parameters:

pcatalog - primary key catalog name; "" retrieves those without a catalog

pschema - primary key schema name pattern; "" retrieves those without a schema

ptable - primary key table name

fcatalog - foreign key catalog name; "" retrieves those without a catalog

fschema - foreign key schema name pattern; "" retrieves those without a schema

ftable - koreign key table name

Returns:

ResultSet each row is a foreign key column description

Throws:

SQLException - if a database error occurs

See Also:

getImportedKeys(java.lang.String, java.lang.String, java.lang.String)

getTypeInfo
```
public ResultSet getTypeInfo()
                      throws SQLException
```
Get a description of all the SQL data types supported by this database. They are ordered by DATA_TYPE and then by how closely the data type maps to the corresponding JDBC SQL type. If the database supports SQL distinct types, then getTypeInfo() will return a single row with a TYPE_NAME of DISTINCT and a DATA_TYPE of Types.DISTINCT. If the database supports SQL structured types, then getTypeInfo() will return a single row with a TYPE_NAME of STRUCT and a DATA_TYPE of Types.STRUCT. If SQL distinct or structured types are supported, then information on the individual types may be obtained from the getUDTs() method.
Each type description has the following columns:
1. TYPE_NAME String => Type name
2. DATA_TYPE int => SQL data type from java.sql.Types
3. PRECISION int => maximum precision
4. LITERAL_PREFIX String => prefix used to quote a literal (may be null)
5. LITERAL_SUFFIX String => suffix used to quote a literal (may be null)
6. CREATE_PARAMS String => parameters used in creating the type (may be null)
7. NULLABLE short => can you use NULL for this type?
  - typeNoNulls - does not allow NULL values
  - typeNullable - allows NULL values
  - typeNullableUnknown - nullability unknown
8. CASE_SENSITIVE boolean=> is it case sensitive?
9. SEARCHABLE short => can you use "WHERE" based on this type:
  - typePredNone - No support
  - typePredChar - Only supported with WHERE .. LIKE
  - typePredBasic - Supported except for WHERE .. LIKE
  - typeSearchable - Supported for all WHERE ..
10. UNSIGNED_ATTRIBUTE boolean => is it unsigned?
11. FIXED_PREC_SCALE boolean => can it be a money value?
12. AUTO_INCREMENT boolean => can it be used for an auto-increment value?
13. LOCAL_TYPE_NAME String => localized version of type name (may be null)
14. MINIMUM_SCALE short => minimum scale supported
15. MAXIMUM_SCALE short => maximum scale supported
16. SQL_DATA_TYPE int => unused
17. SQL_DATETIME_SUB int => unused
18. NUM_PREC_RADIX int => usually 2 or 10
Specified by:

getTypeInfo in interface DatabaseMetaData

Returns:

ResultSet each row is a SQL type description

Throws:

SQLException - if the developer made a Boo-Boo

getIndexInfo
```
public ResultSet getIndexInfo(String catalog,
                              String schema,
                              String table,
                              boolean unique,
                              boolean approximate)
                       throws SQLException
```
Retrieves a description of the given table's indices and statistics. They are ordered by NON_UNIQUE, TYPE, INDEX_NAME, and ORDINAL_POSITION.
Each index column description has the following columns:
1. TABLE_CAT String => table catalog (may be null)
2. TABLE_SCHEM String => table schema (may be null)
3. TABLE_NAME String => table name
4. NON_UNIQUE boolean => Can index values be non-unique? false when TYPE is tableIndexStatistic
5. INDEX_QUALIFIER String => index catalog (may be null); null when TYPE is tableIndexStatistic
6. INDEX_NAME String => index name; null when TYPE is tableIndexStatistic
7. TYPE short => index type:
  - tableIndexStatistic - this identifies table statistics that are returned in conjuction with a table's index descriptions
  - tableIndexClustered - this is a clustered index
  - tableIndexHashed - this is a hashed index
  - tableIndexOther - this is some other style of index
8. ORDINAL_POSITION short => column sequence number within index; zero when TYPE is tableIndexStatistic
9. COLUMN_NAME String => column name; null when TYPE is tableIndexStatistic
10. ASC_OR_DESC String => column sort sequence, "A" => ascending "D" => descending, may be null if sort sequence is not supported; null when TYPE is tableIndexStatistic
11. CARDINALITY int => When TYPE is tableIndexStatisic then this is the number of rows in the table; otherwise it is the number of unique values in the index.
12. PAGES int => When TYPE is tableIndexStatisic then this is the number of pages used for the table, otherwise it is the number of pages used for the current index.
13. FILTER_CONDITION String => Filter condition, if any. (may be null)
Specified by:

getIndexInfo in interface 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:

ResultSet each row is an index column description

Throws:

SQLException - if a database occurs

supportsResultSetType
```
public boolean supportsResultSetType(int type)
                              throws SQLException
```
Does the database support the given result set type?

Specified by:

supportsResultSetType in interface DatabaseMetaData

Parameters:

type - - defined in java.sql.ResultSet

Returns:

true if so; false otherwise

Throws:

SQLException - - if a database access error occurs

supportsResultSetConcurrency
```
public boolean supportsResultSetConcurrency(int type,
                                            int concurrency)
                                     throws SQLException
```
Does the database support the concurrency type in combination with the given result set type?

Specified by:

supportsResultSetConcurrency in interface DatabaseMetaData

Parameters:

type - - defined in java.sql.ResultSet

concurrency - - type defined in java.sql.ResultSet

Returns:

true if so; false otherwise

Throws:

SQLException - - if a database access error occurs

ownUpdatesAreVisible
```
public boolean ownUpdatesAreVisible(int type)
```
Specified by:

ownUpdatesAreVisible in interface DatabaseMetaData

ownDeletesAreVisible
```
public boolean ownDeletesAreVisible(int type)
```
Specified by:

ownDeletesAreVisible in interface DatabaseMetaData

ownInsertsAreVisible
```
public boolean ownInsertsAreVisible(int type)
```
Specified by:

ownInsertsAreVisible in interface DatabaseMetaData

othersUpdatesAreVisible
```
public boolean othersUpdatesAreVisible(int type)
```
Specified by:

othersUpdatesAreVisible in interface DatabaseMetaData

othersDeletesAreVisible
```
public boolean othersDeletesAreVisible(int i)
```
Specified by:

othersDeletesAreVisible in interface DatabaseMetaData

othersInsertsAreVisible
```
public boolean othersInsertsAreVisible(int type)
```
Specified by:

othersInsertsAreVisible in interface DatabaseMetaData

updatesAreDetected
```
public boolean updatesAreDetected(int type)
```
Specified by:

updatesAreDetected in interface DatabaseMetaData

deletesAreDetected
```
public boolean deletesAreDetected(int i)
```
Specified by:

deletesAreDetected in interface DatabaseMetaData

insertsAreDetected
```
public boolean insertsAreDetected(int type)
```
Specified by:

insertsAreDetected in interface DatabaseMetaData

supportsBatchUpdates
```
public boolean supportsBatchUpdates()
```
Indicates whether the driver supports batch updates.

Specified by:

supportsBatchUpdates in interface DatabaseMetaData

getUDTs
```
public ResultSet getUDTs(String catalog,
                         String schemaPattern,
                         String typeNamePattern,
                         int[] types)
                  throws SQLException
```
Retrieves a description of the user-defined types (UDTs) defined in a particular schema. Schema-specific UDTs may have type JAVA_OBJECT, STRUCT, or DISTINCT. Only types matching the catalog, schema, type name and type criteria are returned. They are ordered by DATA_TYPE, TYPE_CAT, TYPE_SCHEM and TYPE_NAME. The type name parameter may be a fully-qualified name. In this case, the catalog and schemaPattern parameters are ignored. Each type description has the following columns: 1 TYPE_CAT String => the type's catalog (may be null) 2 TYPE_SCHEM String => type's schema (may be null) 3 TYPE_NAME String => type name 4 CLASS_NAME String => Java class name 5 DATA_TYPE int => type value defined in java.sql.Types. One of JAVA_OBJECT, STRUCT, or DISTINCT 6 REMARKS String => explanatory comment on the type 7 BASE_TYPE short => type code of the source type of a DISTINCT type or the type that implements the user-generated reference type of the SELF_REFERENCING_COLUMN of a structured type as defined in java.sql.Types (null if DATA_TYPE is not DISTINCT or not STRUCT with REFERENCE_GENERATION = USER_DEFINED)

Specified by:

getUDTs in interface DatabaseMetaData

Throws:

SQLException

getConnection
```
public Connection getConnection()
```
Retrieves the connection that produced this metadata object.

Specified by:

getConnection in interface DatabaseMetaData

Returns:

the connection that produced this metadata object

rowChangesAreDetected

public boolean rowChangesAreDetected(int type)

rowChangesAreVisible

public boolean rowChangesAreVisible(int type)

supportsSavepoints
```
public boolean supportsSavepoints()
```
Retrieves whether this database supports savepoints.

Specified by:

supportsSavepoints in interface DatabaseMetaData

Returns:

true if savepoints are supported; false otherwise

supportsNamedParameters
```
public boolean supportsNamedParameters()
```
Retrieves whether this database supports named parameters to callable statements.

Specified by:

supportsNamedParameters in interface DatabaseMetaData

Returns:

true if named parameters are supported; false otherwise

supportsMultipleOpenResults
```
public boolean supportsMultipleOpenResults()
```
Retrieves whether it is possible to have multiple ResultSet objects returned from a CallableStatement object simultaneously.

Specified by:

supportsMultipleOpenResults in interface DatabaseMetaData

Returns:

true if a CallableStatement object can return multiple ResultSet objects simultaneously; false otherwise

supportsGetGeneratedKeys
```
public boolean supportsGetGeneratedKeys()
```
Retrieves whether auto-generated keys can be retrieved after a statement has been executed.

Specified by:

supportsGetGeneratedKeys in interface DatabaseMetaData

Returns:

true if auto-generated keys can be retrieved after a statement has executed; false otherwise

getSuperTypes
```
public ResultSet getSuperTypes(String catalog,
                               String schemaPattern,
                               String typeNamePattern)
                        throws SQLException
```
Retrieves a description of the user-defined type (UDT) hierarchies defined in a particular schema in this database. Only the immediate super type/ sub type relationship is modeled.
Only supertype information for UDTs matching the catalog, schema, and type name is returned. The type name parameter may be a fully-qualified name. When the UDT name supplied is a fully-qualified name, the catalog and schemaPattern parameters are ignored.
If a UDT does not have a direct super type, it is not listed here. A row of the ResultSet object returned by this method describes the designated UDT and a direct supertype. A row has the following columns:
1. TYPE_CAT String => the UDT's catalog (may be null)
2. TYPE_SCHEM String => UDT's schema (may be null)
3. TYPE_NAME String => type name of the UDT
4. SUPERTYPE_CAT String => the direct super type's catalog (may be null)
5. SUPERTYPE_SCHEM String => the direct super type's schema (may be null)
6. 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 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:

SQLException - if a database access error occurs

getSuperTables
```
public ResultSet getSuperTables(String catalog,
                                String schemaPattern,
                                String tableNamePattern)
                         throws SQLException
```
Retrieves a description of the table hierarchies defined in a particular schema in this database.
Only supertable information for tables matching the catalog, schema and table name are returned. The table name parameter may be a fully- qualified name, in which case, the catalog and schemaPattern parameters are ignored. If a table does not have a super table, it is not listed here. Supertables have to be defined in the same catalog and schema as the sub tables. Therefore, the type description does not need to include this information for the supertable.
Each type description has the following columns:
1. TABLE_CAT String => the type's catalog (may be null)
2. TABLE_SCHEM String => type's schema (may be null)
3. TABLE_NAME String => type name
4. 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 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:

SQLException - if a database access error occurs

getAttributes
```
public ResultSet getAttributes(String catalog,
                               String schemaPattern,
                               String typeNamePattern,
                               String attributeNamePattern)
                        throws SQLException
```
Retrieves a description of the given attribute of the given type for a user-defined type (UDT) that is available in the given schema and catalog.
Descriptions are returned only for attributes of UDTs matching the catalog, schema, type, and attribute name criteria. They are ordered by TYPE_SCHEM, TYPE_NAME and ORDINAL_POSITION. This description does not contain inherited attributes.
The ResultSet object that is returned has the following columns:
1. TYPE_CAT String => type catalog (may be null)
2. TYPE_SCHEM String => type schema (may be null)
3. TYPE_NAME String => type name
4. ATTR_NAME String => attribute name
5. DATA_TYPE int => attribute type SQL type from java.sql.Types
6. 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.
7. 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.
8. DECIMAL_DIGITS int => the number of fractional digits
9. NUM_PREC_RADIX int => Radix (typically either 10 or 2)
10. NULLABLE int => whether NULL is allowed
  - attributeNoNulls - might not allow NULL values
  - attributeNullable - definitely allows NULL values
  - attributeNullableUnknown - nullability unknown
11. REMARKS String => comment describing column (may be null)
12. ATTR_DEF String => default value (may be null)
13. SQL_DATA_TYPE int => unused
14. SQL_DATETIME_SUB int => unused
15. CHAR_OCTET_LENGTH int => for char types the maximum number of bytes in the column
16. ORDINAL_POSITION int => index of column in table (starting at 1)
17. 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.
18. SCOPE_CATALOG String => catalog of table that is the scope of a reference attribute (null if DATA_TYPE isn't REF)
19. SCOPE_SCHEMA String => schema of table that is the scope of a reference attribute (null if DATA_TYPE isn't REF)
20. SCOPE_TABLE String => table name that is the scope of a reference attribute (null if the DATA_TYPE isn't REF)
21. 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 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:

SQLException - if a database access error occurs

supportsResultSetHoldability
```
public boolean supportsResultSetHoldability(int holdability)
```
Retrieves whether this database supports the given result set holdability.

Specified by:

supportsResultSetHoldability in interface 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

See Also:

Connection

getResultSetHoldability
```
public int getResultSetHoldability()
```
Retrieves the default holdability of this ResultSet object.

Specified by:

getResultSetHoldability in interface DatabaseMetaData

Returns:

the default holdability; either ResultSet.HOLD_CURSORS_OVER_COMMIT or ResultSet.CLOSE_CURSORS_AT_COMMIT

getDatabaseMajorVersion
```
public int getDatabaseMajorVersion()
                            throws SQLException
```
Retrieves the major version number of the underlying database.

Specified by:

getDatabaseMajorVersion in interface DatabaseMetaData

Returns:

the underlying database's major version

Throws:

SQLException - if a database access error occurs

getDatabaseMinorVersion
```
public int getDatabaseMinorVersion()
                            throws SQLException
```
Retrieves the minor version number of the underlying database.

Specified by:

getDatabaseMinorVersion in interface DatabaseMetaData

Returns:

underlying database's minor version

Throws:

SQLException - if a database access error occurs

getJDBCMajorVersion
```
public int getJDBCMajorVersion()
```
Retrieves the major JDBC version number for this driver.

Specified by:

getJDBCMajorVersion in interface DatabaseMetaData

Returns:

JDBC version major number

getJDBCMinorVersion
```
public int getJDBCMinorVersion()
```
Retrieves the minor JDBC version number for this driver.

Specified by:

getJDBCMinorVersion in interface DatabaseMetaData

Returns:

JDBC version minor number

getSQLStateType
```
public int getSQLStateType()
```
Indicates whether the SQLSTATEs returned by SQLException.getSQLState is X/Open (now known as Open Group) SQL CLI or SQL:2003.

Specified by:

getSQLStateType in interface DatabaseMetaData

Returns:

the type of SQLSTATEs, one of: sqlStateXOpen or sqlStateSQL

locatorsUpdateCopy
```
public boolean locatorsUpdateCopy()
```
Indicates whether updates made to a LOB are made on a copy or directly to the LOB.

Specified by:

locatorsUpdateCopy in interface DatabaseMetaData

Returns:

true if updates are made to a copy of the LOB; false if updates are made directly to the LOB

supportsStatementPooling
```
public boolean supportsStatementPooling()
```
Retrieves whether this database supports statement pooling.

Specified by:

supportsStatementPooling in interface DatabaseMetaData

Returns:

true is so; false otherwise

getRowIdLifetime
```
public RowIdLifetime getRowIdLifetime()
```
Indicates whether or not this data source supports the SQL ROWID type, and if so the lifetime for which a RowId object remains valid.

Specified by:

getRowIdLifetime in interface DatabaseMetaData

Returns:

ROWID_UNSUPPORTED for now

getSchemas
```
public ResultSet getSchemas()
                     throws SQLException
```
Get the schema names available in this database. The results are ordered by schema name.
The schema column is:
1. TABLE_SCHEM String => schema name
2. TABLE_CATALOG String => catalog name (may be null)
Specified by:

getSchemas in interface DatabaseMetaData

Returns:

ResultSet each row has a single String column that is a schema name

Throws:

SQLException - if a database error occurs

supportsStoredFunctionsUsingCallSyntax
```
public boolean supportsStoredFunctionsUsingCallSyntax()
```
Retrieves whether this database supports invoking user-defined or vendor functions using the stored procedure escape syntax.

Specified by:

supportsStoredFunctionsUsingCallSyntax in interface DatabaseMetaData

Returns:

true if so; false otherwise

autoCommitFailureClosesAllResultSets
```
public boolean autoCommitFailureClosesAllResultSets()
```
Retrieves whether a SQLException while autoCommit is true inidcates that all open ResultSets are closed, even ones that are holdable. When a SQLException occurs while autocommit is true, it is vendor specific whether the JDBC driver responds with a commit operation, a rollback operation, or by doing neither a commit nor a rollback. A potential result of this difference is in whether or not holdable ResultSets are closed.

Specified by:

autoCommitFailureClosesAllResultSets in interface DatabaseMetaData

Returns:

true if so; false otherwise

getClientInfoProperties
```
public ResultSet getClientInfoProperties()
                                  throws SQLException
```
Retrieves a list of the client info properties that the driver supports. The result set contains the following columns 1. NAME String=> The name of the client info property 2. MAX_LEN int=> The maximum length of the value for the property 3. DEFAULT_VALUE String=> The default value of the property 4. DESCRIPTION String=> A description of the property. This will typically contain information as to where this property is stored in the database. The ResultSet is sorted by the NAME column

Specified by:

getClientInfoProperties in interface DatabaseMetaData

Returns:

A ResultSet object; each row is a supported client info property, none in case of MonetDB's current JDBC driver

Throws:

SQLException - if a database access error occurs

getFunctions
```
public ResultSet getFunctions(String catalog,
                              String schemaPattern,
                              String functionNamePattern)
                       throws SQLException
```
Retrieves a description of the system and user functions available in the given catalog. Only system and user function descriptions matching the schema and function name criteria are returned. They are ordered by FUNCTION_CAT, FUNCTION_SCHEM, FUNCTION_NAME and SPECIFIC_ NAME. Each function description has the the following columns: 1. FUNCTION_CAT String => function catalog (may be null) 2. FUNCTION_SCHEM String => function schema (may be null) 3. FUNCTION_NAME String => function name. This is the name used to invoke the function 4. REMARKS String => explanatory comment on the function 5. FUNCTION_TYPE short => kind of function: * functionResultUnknown - Cannot determine if a return value or table will be returned * functionNoTable- Does not return a table * functionReturnsTable - Returns a table 6. SPECIFIC_NAME String => the name which uniquely identifies this function within its schema. This is a user specified, or DBMS generated, name that may be different then the FUNCTION_NAME for example with overload functions A user may not have permission to execute any of the functions that are returned by getFunctions.

Specified by:

getFunctions in interface 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

functionNamePattern - a function name pattern; must match the function name as it is stored in the database

Returns:

ResultSet - each row is a function description

Throws:

SQLException - if a database access error occurs

getFunctionColumns
```
public ResultSet getFunctionColumns(String catalog,
                                    String schemaPattern,
                                    String functionNamePattern,
                                    String columnNamePattern)
                             throws SQLException
```
Retrieves a description of the given catalog's system or user function parameters and return type. Only descriptions matching the schema, function and parameter name criteria are returned. They are ordered by FUNCTION_CAT, FUNCTION_SCHEM, FUNCTION_NAME and SPECIFIC_ NAME. Within this, the return value, if any, is first. Next are the parameter descriptions in call order. The column descriptions follow in column number order. 1. FUNCTION_CAT String => function catalog (may be null) 2. FUNCTION_SCHEM String => function schema (may be null) 3. FUNCTION_NAME String => function name. This is the name used to invoke the function 4. COLUMN_NAME String => column/parameter name 5. COLUMN_TYPE Short => kind of column/parameter: functionColumnUnknown - nobody knows functionColumnIn - IN parameter functionColumnInOut - INOUT parameter functionColumnOut - OUT parameter functionColumnReturn - function return value functionColumnResult - Indicates that the parameter or column is a column in the ResultSet 6. DATA_TYPE int => SQL type from java.sql.Types 7. TYPE_NAME String => SQL type name, for a UDT type the type name is fully qualified 8. PRECISION int => precision 9. LENGTH int => length in bytes of data 10. SCALE short => scale - null is returned for data types where SCALE is not applicable. 11. RADIX short => radix 12. NULLABLE short => can it contain NULL. functionNoNulls - does not allow NULL values functionNullable - allows NULL values functionNullableUnknown - nullability unknown 13. REMARKS String => comment describing column/parameter 14. CHAR_OCTET_LENGTH int => the maximum length of binary and character based parameters or columns. For any other datatype the returned value is a NULL 15. ORDINAL_POSITION int => the ordinal position, starting from 1, for the input and output parameters. A value of 0 is returned if this row describes the function's return value. For result set columns, it is the ordinal position of the column in the result set starting from 1. 16. IS_NULLABLE String => ISO rules are used to determine the nullability for a parameter or column. YES --- if the parameter or column can include NULLs NO --- if the parameter or column cannot include NULLs empty string --- if the nullability for the parameter or column is unknown 17. SPECIFIC_NAME String => the name which uniquely identifies this function within its schema. This is a user specified, or DBMS generated, name that may be different then the FUNCTION_NAME for example with overload functions

Specified by:

getFunctionColumns in interface 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

functionNamePattern - a procedure name pattern; must match the function name as it is stored in the database

columnNamePattern - a parameter name pattern; must match the parameter or column name as it is stored in the database

Returns:

ResultSet - each row describes a user function parameter, column or return type

Throws:

SQLException - - if a database access error occurs

getPseudoColumns
```
public ResultSet getPseudoColumns(String catalog,
                                  String schemaPattern,
                                  String tableNamePattern,
                                  String columnNamePattern)
                           throws SQLException
```
Retrieves a description of the pseudo or hidden columns available in a given table within the specified catalog and schema. Pseudo or hidden columns may not always be stored within a table and are not visible in a ResultSet unless they are specified in the query's outermost SELECT list. Pseudo or hidden columns may not necessarily be able to be modified. If there are no pseudo or hidden columns, an empty ResultSet is returned. Only column descriptions matching the catalog, schema, table and column name criteria are returned. They are ordered by TABLE_CAT,TABLE_SCHEM, TABLE_NAME and COLUMN_NAME. Each column description has the following columns: 1. TABLE_CAT String => table catalog (may be null) 2. TABLE_SCHEM String => table schema (may be null) 3. TABLE_NAME String => table name 4. COLUMN_NAME String => column name 5. DATA_TYPE int => SQL type from java.sql.Types 6. COLUMN_SIZE int => column size. 7. DECIMAL_DIGITS int => the number of fractional digits. Null is returned for data types where DECIMAL_DIGITS is not applicable. 8. NUM_PREC_RADIX int => Radix (typically either 10 or 2) 9. COLUMN_USAGE String => The allowed usage for the column. The value returned will correspond to the enum name returned by PseudoColumnUsage.name() 10. REMARKS String => comment describing column (may be null) 11. CHAR_OCTET_LENGTH int => for char types the maximum number of bytes in the column 12. IS_NULLABLE String => ISO rules are used to determine the nullability for a column. YES --- if the column can include NULLs NO --- if the column cannot include NULLs empty string --- if the nullability for the column is unknown

Specified by:

getPseudoColumns in interface DatabaseMetaData

Parameters:

catalog - a catalog name

schemaPattern - a schema name pattern

tableNamePattern - a table name pattern

columnNamePattern - a column name pattern

Returns:

ResultSet where each row is a column description

Throws:

SQLException - if a database access error occurs

generatedKeyAlwaysReturned
```
public boolean generatedKeyAlwaysReturned()
                                   throws SQLException
```
Retrieves whether a generated key will always be returned if the column name(s) or index(es) specified for the auto generated key column(s) are valid and the statement succeeds. The key that is returned may or may not be based on the column(s) for the auto generated key.

Specified by:

generatedKeyAlwaysReturned in interface DatabaseMetaData

Returns:

true if so, false otherwise

Throws:

SQLException - - if a database access error occurs

Class MonetDatabaseMetaData

Field Summary

Fields inherited from interface java.sql.DatabaseMetaData

Constructor Summary

Method Summary

Methods inherited from class nl.cwi.monetdb.jdbc.MonetWrapper

Methods inherited from class java.lang.Object

Methods inherited from interface java.sql.DatabaseMetaData

Methods inherited from interface java.sql.Wrapper

Constructor Detail

MonetDatabaseMetaData

Method Detail

allProceduresAreCallable

allTablesAreSelectable

getURL

getUserName

isReadOnly

nullsAreSortedHigh

nullsAreSortedLow

nullsAreSortedAtStart

nullsAreSortedAtEnd

getDatabaseProductName

getDatabaseProductVersion

getDriverName

getDriverVersion

getDriverMajorVersion

getDriverMinorVersion

usesLocalFiles

usesLocalFilePerTable

supportsMixedCaseIdentifiers

storesUpperCaseIdentifiers

storesLowerCaseIdentifiers

storesMixedCaseIdentifiers

supportsMixedCaseQuotedIdentifiers

storesUpperCaseQuotedIdentifiers

storesLowerCaseQuotedIdentifiers

storesMixedCaseQuotedIdentifiers

getIdentifierQuoteString

getSQLKeywords

getNumericFunctions

getStringFunctions

getSystemFunctions

getTimeDateFunctions

getSearchStringEscape

getExtraNameCharacters

supportsAlterTableWithAddColumn

supportsAlterTableWithDropColumn

supportsColumnAliasing

nullPlusNonNullIsNull

supportsConvert

supportsConvert

supportsTableCorrelationNames

supportsDifferentTableCorrelationNames

supportsExpressionsInOrderBy

supportsOrderByUnrelated

supportsGroupBy

supportsGroupByUnrelated

supportsGroupByBeyondSelect

supportsLikeEscapeClause

supportsMultipleResultSets

supportsMultipleTransactions

supportsNonNullableColumns

supportsMinimumSQLGrammar

supportsCoreSQLGrammar

supportsExtendedSQLGrammar

supportsANSI92EntryLevelSQL

supportsANSI92IntermediateSQL

supportsANSI92FullSQL

supportsIntegrityEnhancementFacility

supportsOuterJoins

supportsFullOuterJoins

supportsLimitedOuterJoins

getSchemaTerm

getProcedureTerm

getCatalogTerm

isCatalogAtStart

getCatalogSeparator

supportsSchemasInDataManipulation

supportsSchemasInProcedureCalls

supportsSchemasInTableDefinitions