|JDBC API / Core JDBC Classes, Interfaces, and Methods|
DatabaseMetaData result sets do not close the result sets of other statements, even when auto-commit is set to true.
DatabaseMetaData result sets are closed if a user performs any other action on a JDBC object that causes an automatic commit to occur. If you need the DatabaseMetaData result sets to be accessible while executing other actions that would cause automatic commits, turn off auto-commit with setAutoCommit(false).
GemFire XD supports Java procedures and allows you to call Java procedures within SQL statements. GemFire XD returns information about the parameters in the getProcedureColumns call and returns information for all Java procedures defined by CREATE PROCEDURE.
getProcedureColumns returns a ResultSet. Each row describes a single parameter or return value.
The JDBC API defines the following parameters for the getProcedureColumns method call.
Columns in the ResultSet returned by getProcedureColumns are as described by the API. Further details for some specific columns:
The java.sql.DatabaseMetaData.getBestRowIdentifier method looks for identifiers in the following order:
A primary key on the table.
A unique constraint or unique index on the table.
All of the columns in the table.
This order might not return a unique row.
Note: If the java.sql.DatabaseMetaData.getBestRowIdentifier method does not find a primary key, unique constraint, or unique index, the method must look for identifiers in all of the columns in the table. When the method looks for identifiers this way, the method will always find a set of columns that identify a row. However, a unique row might not be identified if there are duplicate rows in the table.