< prev index next >

src/java.sql/share/classes/java/sql/DatabaseMetaData.java

Print this page
rev 60127 : 8249205: Remove unnecessary trademark symbols


  14  * version 2 for more details (a copy is included in the LICENSE file that
  15  * accompanied this code).
  16  *
  17  * You should have received a copy of the GNU General Public License version
  18  * 2 along with this work; if not, write to the Free Software Foundation,
  19  * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
  20  *
  21  * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
  22  * or visit www.oracle.com if you need additional information or have any
  23  * questions.
  24  */
  25 
  26 
  27 package java.sql;
  28 
  29 /**
  30  * Comprehensive information about the database as a whole.
  31  * <P>
  32  * This interface is implemented by driver vendors to let users know the capabilities
  33  * of a Database Management System (DBMS) in combination with
  34  * the driver based on JDBC&trade; technology
  35  * ("JDBC driver") that is used with it.  Different relational DBMSs often support
  36  * different features, implement features in different ways, and use different
  37  * data types.  In addition, a driver may implement a feature on top of what the
  38  * DBMS offers.  Information returned by methods in this interface applies
  39  * to the capabilities of a particular driver and a particular DBMS working
  40  * together. Note that as used in this documentation, the term "database" is
  41  * used generically to refer to both the driver and DBMS.
  42  * <P>
  43  * A user for this interface is commonly a tool that needs to discover how to
  44  * deal with the underlying DBMS.  This is especially true for applications
  45  * that are intended to be used with more than one DBMS. For example, a tool might use the method
  46  * <code>getTypeInfo</code> to find out what data types can be used in a
  47  * <code>CREATE TABLE</code> statement.  Or a user might call the method
  48  * <code>supportsCorrelatedSubqueries</code> to see if it is possible to use
  49  * a correlated subquery or <code>supportsBatchUpdates</code> to see if it is
  50  * possible to use batch updates.
  51  * <P>
  52  * Some <code>DatabaseMetaData</code> methods return lists of information
  53  * in the form of <code>ResultSet</code> objects.
  54  * Regular <code>ResultSet</code> methods, such as




  14  * version 2 for more details (a copy is included in the LICENSE file that
  15  * accompanied this code).
  16  *
  17  * You should have received a copy of the GNU General Public License version
  18  * 2 along with this work; if not, write to the Free Software Foundation,
  19  * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
  20  *
  21  * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
  22  * or visit www.oracle.com if you need additional information or have any
  23  * questions.
  24  */
  25 
  26 
  27 package java.sql;
  28 
  29 /**
  30  * Comprehensive information about the database as a whole.
  31  * <P>
  32  * This interface is implemented by driver vendors to let users know the capabilities
  33  * of a Database Management System (DBMS) in combination with
  34  * the driver based on JDBC technology
  35  * ("JDBC driver") that is used with it.  Different relational DBMSs often support
  36  * different features, implement features in different ways, and use different
  37  * data types.  In addition, a driver may implement a feature on top of what the
  38  * DBMS offers.  Information returned by methods in this interface applies
  39  * to the capabilities of a particular driver and a particular DBMS working
  40  * together. Note that as used in this documentation, the term "database" is
  41  * used generically to refer to both the driver and DBMS.
  42  * <P>
  43  * A user for this interface is commonly a tool that needs to discover how to
  44  * deal with the underlying DBMS.  This is especially true for applications
  45  * that are intended to be used with more than one DBMS. For example, a tool might use the method
  46  * <code>getTypeInfo</code> to find out what data types can be used in a
  47  * <code>CREATE TABLE</code> statement.  Or a user might call the method
  48  * <code>supportsCorrelatedSubqueries</code> to see if it is possible to use
  49  * a correlated subquery or <code>supportsBatchUpdates</code> to see if it is
  50  * possible to use batch updates.
  51  * <P>
  52  * Some <code>DatabaseMetaData</code> methods return lists of information
  53  * in the form of <code>ResultSet</code> objects.
  54  * Regular <code>ResultSet</code> methods, such as


< prev index next >