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 doing
Try 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 raise a SQLException if it is the right
driver to connect to the given URL, but has trouble connecting to
The java.util.Properties argument can be used to passed arbitrary
string tag/value pairs as connection arguments.
Normally at least "user" and "password" properties should be
included in the Properties.
url - The URL of the database to connect to
info - a list of arbitrary string tag/value pairs as
connection arguments; normally at least a "user" and
"password" property should be included
The getPropertyInfo method is intended to allow a generic GUI tool to
discover what properties it should prompt a human for in order to get
enough information to connect to a database. Note that depending on
the values the human has supplied so far, additional values may become
necessary, so it may be necessary to iterate though several calls
url - The URL of the database to connect to.
info - A proposed list of tag/value pairs that will be sent on
An array of DriverPropertyInfo objects describing possible
properties. This array may be an empty array if no properties
Report whether the Driver is a genuine JDBC COMPLIANT (tm) driver.
A driver may only report "true" here if it passes the JDBC compliance
tests, otherwise it is required to return false.
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.