These methods are deprecated, please consult the documentation of the individual backends for the construction of driver instances.
dbDriver()
is a helper method used to create an new driver object
given the name of a database or the corresponding R package. It works
through convention: all DBI-extending packages should provide an exported
object with the same name as the package. dbDriver()
just looks for
this object in the right places: if you know what database you are connecting
to, you should call the function directly.
dbUnloadDriver()
is not implemented for modern backends.
# S4 method for DatabaseConnectorDriver
dbUnloadDriver(drv, ...)
an object that inherits from DBIDriver
as created by
dbDriver
.
any other arguments are passed to the driver drvName
.
In the case of dbDriver
, an driver object whose class extends
DBIDriver
. This object may be used to create connections to the
actual DBMS engine.
In the case of dbUnloadDriver
, a logical indicating whether the
operation succeeded or not.
The client part of the database communication is
initialized (typically dynamically loading C code, etc.) but note that
connecting to the database engine itself needs to be done through calls to
dbConnect
.
Other DBIDriver generics:
DBIDriver-class
,
dbCanConnect()
,
dbConnect()
,
dbDataType()
,
dbGetInfo()
,
dbIsReadOnly()
,
dbIsValid()
,
dbListConnections()
Other DBIDriver generics:
DBIDriver-class
,
dbCanConnect()
,
dbConnect()
,
dbDataType()
,
dbGetInfo()
,
dbIsReadOnly()
,
dbIsValid()
,
dbListConnections()