R: Load and unload database drivers

dbDriver {DBI} | R Documentation

## Load and unload database drivers

### Description

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.

### Usage

    dbDriver(drvName, ...)

    dbUnloadDriver(drv, ...)

### Arguments

`drvName` | character name of the driver to instantiate.
`...` | any other arguments are passed to the driver `drvName`.
`drv` | an object that inherits from `DBIDriver` as created by `dbDriver`.

### Details

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`.

### Value

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.

### See Also

Other DBIDriver generics: `DBIDriver-class`, `dbConnect`, `dbDataType`, `dbGetInfo`, `dbIsValid`, `dbListConnections`

Other DBIDriver generics: `DBIDriver-class`, `dbConnect`, `dbDataType`, `dbGetInfo`, `dbIsValid`, `dbListConnections`

### Examples

    # Create a RSQLite driver with a string
    d <- dbDriver("SQLite")
    d

    # But better, access the object directly
    RSQLite::SQLite()

[Package DBI version 0.8 Index]