Java Database Connectivity
{'<entity_0>': 'application programming interface', '<entity_1>': 'Java Database Connectivity', '<entity_2>': 'Java Virtual Machine', '<entity_3>': 'Java', '<entity_4>': 'JDBC'}
[['Java Database Connectivity', 'instance of', 'application programming interface'], ['Java Database Connectivity', 'platform', 'Java Virtual Machine'], ['Java Database Connectivity', 'programming language', 'Java'], ['Java Database Connectivity', 'alternative', 'JDBC']]
<entity_1> (<entity_4>) is an <entity_0> (API) for the programming language <entity_3>, which defines how a client may access a database. A <entity_4>-to-ODBC bridge enables connections to any ODBC-accessible data source in the <entity_2> (JVM) host environment. Sun Microsystems released <entity_4> as part of <entity_3> Development Kit (JDK) 1.1 on February 19, 1997. The <entity_4> classes are contained in the <entity_3> package java.sql and javax.sql. Starting with version 3.1, <entity_4> has been developed under the <entity_3> Community Process. JSR 54 specifies <entity_4> 3.0 (included in J2SE 1.4), JSR 114 specifies the <entity_4> Rowset additions, and JSR 221 is the specification of <entity_4> 4.0 (included in <entity_3> SE 6). <entity_4> 4.1, is specified by a maintenance release 1 of JSR 221 and is included in <entity_3> SE 7. <entity_4> 4.2, is specified by a maintenance release 2 of JSR 221 and is included in <entity_3> SE 8. The latest version, <entity_4> 4.3, is specified by a maintenance release 3 of JSR 221 and is included in <entity_3> SE 9. <entity_4> ('<entity_1>') allows multiple implementations to exist and be used by the same application. The API provides a mechanism for dynamically loading the correct <entity_3> packages and registering them with the <entity_4> Driver Manager. When a <entity_3> application needs a database connection, one of the DriverManager.getConnection() methods is used to create a <entity_4> connection. <entity_4> drivers are client-side adapters (installed on the client machine, not on the server) that convert requests from <entity_3> programs to a protocol that the DBMS can understand. These drivers fall into one of the following types: Note also a type called an internal <entity_4> driver - a driver embedded with JRE in <entity_3>-enabled SQL databases.
['application programming interface', 'Database abstraction layer', 'software']