The Java SQL framework allows for multiple database drivers.
Each driver should supply a class that implements the Driver interface.
The DriverManager will try to load as many drivers as it can find and then for any given connection request, it will ask each driver in turn to try to connect to the target URL.
It is strongly recommended that each Driver class should be small and standalone so that the Driver class can be loaded and queried without bringing in vast quantities of supporting code.
When a Driver class is loaded, it should create an instance of itself and register it with the DriverManager. This means that a user can load and register a driver by calling:
Class.forName("foo.bah.Driver")
A JDBC driver may create a DriverAction implementation in order to receive notifications when DriverManager#deregisterDriver has been called.
DriverManager, Connection, DriverAction
| Modifier and Type | Method and Description |
|---|---|
| public boolean | Returns: true if this driver understands the given URL;
false otherwisethe URL of the database url)Retrieves whether the driver thinks that it can open a connection to the given URL. |
| public Connection | Returns: aConnection object that represents a
connection to the URLthe URL of the database to which to connect url, Properties a list of arbitrary string tag/value pairs as
connection arguments. Normally at least a "user" and
"password" property should be included. info)Attempts to make a database connection to the given URL. |
| public int | Returns: this driver's major version numberRetrieves the driver's major version number. |
| public int | |
| public Logger | Returns: the parent Logger for this driverReturn the parent Logger of all the Loggers used by this driver. |
| public DriverPropertyInfo[] | Returns: an array ofDriverPropertyInfo objects describing
possible properties. This array may be an empty array if
no properties are required.the URL of the database to which to connect url, Properties a proposed list of tag/value pairs that will be sent on
connect open info)Gets information about the possible properties for this driver. |
| public boolean | Returns: true if this driver is JDBC Compliant; false
otherwiseReports whether this driver is a genuine JDBC Compliant driver. |
| acceptsURL | back to summary |
|---|---|
| public boolean acceptsURL(String url) throws SQLException Retrieves whether the driver thinks that it can open a connection
to the given URL. Typically drivers will return
| |
| connect | back to summary |
|---|---|
| public Connection connect(String url, Properties info) throws SQLException Attempts to make a database connection to the given URL. The driver should return "null" if it realizes it is the wrong kind of driver to connect to the given URL. This will be common, as when the JDBC driver manager is asked to connect to a given URL it passes the URL to each loaded driver in turn. The driver should throw an The Note If a property is specified as part of the
| |
| getMajorVersion | back to summary |
|---|---|
| public int getMajorVersion() Retrieves the driver's major version number. Initially this should be 1.
| |
| getMinorVersion | back to summary |
|---|---|
| public int getMinorVersion() Gets the driver's minor version number. Initially this should be 0.
| |
| getParentLogger | back to summary |
|---|---|
| public Logger getParentLogger() throws SQLFeatureNotSupportedException Return the parent Logger of all the Loggers used by this driver. This should be the Logger farthest from the root Logger that is still an ancestor of all of the Loggers used by this driver. Configuring this Logger will affect all of the log messages generated by the driver. In the worst case, this may be the root Logger.
| |
| getPropertyInfo | back to summary |
|---|---|
| public DriverPropertyInfo[] getPropertyInfo(String url, Properties info) throws SQLException Gets information about the possible properties for this driver.
The
| |
| jdbcCompliant | back to summary |
|---|---|
| public boolean jdbcCompliant() Reports whether this driver is a genuine JDBC
Compliant driver.
A driver may only report JDBC compliance requires full support for the JDBC API and full support for SQL 92 Entry Level. It is expected that JDBC compliant drivers will be available for all the major commercial databases. This method is not intended to encourage the development of non-JDBC compliant drivers, but is a recognition of the fact that some vendors are interested in using the JDBC API and framework for lightweight databases that do not support full database functionality, or for special databases such as document information retrieval where a SQL implementation may not be feasible.
| |