Returns the result of a query as a data frame.
dbGetQuery()
comes with a default implementation
(which should work with most backends) that calls
dbSendQuery()
, then dbFetch()
, ensuring that
the result is always freed by dbClearResult()
.
For retrieving chunked/paged results or for passing query parameters,
see dbSendQuery()
, in particular the "The data retrieval flow" section.
For retrieving results as an Arrow object, see dbGetQueryArrow()
.
Methods in other packages
This documentation page describes the generics. Refer to the documentation pages linked below for the documentation for the methods that are implemented in various backend packages.
DatabaseConnector::dbGetQuery("DatabaseConnectorConnection", "character")
dittodb::dbGetQuery("DBIMockRPostgreSQLConnection", "character")
RPostgreSQL::dbGetQuery("PostgreSQLConnection", "character")
sparklyr::dbGetQuery("spark_connection", "ANY")
Arguments
- conn
A DBIConnection object, as returned by
dbConnect()
.- statement
a character string containing SQL.
- ...
Other parameters passed on to methods.
Value
dbGetQuery()
always returns a data.frame, with
as many rows as records were fetched and as many
columns as fields in the result set,
even if the result is a single value
or has one
or zero rows.
Details
This method is for SELECT
queries only
(incl. other SQL statements that return a SELECT
-alike result,
e.g., execution of a stored procedure or data manipulation queries
like INSERT INTO ... RETURNING ...
).
To execute a stored procedure that does not return a result set,
use dbExecute()
.
Some backends may
support data manipulation statements through this method for compatibility
reasons. However, callers are strongly advised to use
dbExecute()
for data manipulation statements.
Implementation notes
Subclasses should override this method only if they provide some sort of performance optimization.
Failure modes
An error is raised when issuing a query over a closed
or invalid connection,
if the syntax of the query is invalid,
or if the query is not a non-NA
string.
If the n
argument is not an atomic whole number
greater or equal to -1 or Inf, an error is raised,
but a subsequent call to dbGetQuery()
with proper n
argument succeeds.
Additional arguments
The following arguments are not part of the dbGetQuery()
generic
(to improve compatibility across backends)
but are part of the DBI specification:
n
(default: -1)params
(default:NULL
)immediate
(default:NULL
)
They must be provided as named arguments. See the "Specification" and "Value" sections for details on their usage.
Specification
A column named row_names
is treated like any other column.
The n
argument specifies the number of rows to be fetched.
If omitted, fetching multi-row queries with one
or more columns returns the entire result.
A value of Inf for the n
argument is supported
and also returns the full result.
If more rows than available are fetched (by passing a too large value for
n
), the result is returned in full without warning.
If zero rows are requested, the columns of the data frame are still fully
typed.
Fetching fewer rows than available is permitted,
no warning is issued.
The param
argument allows passing query parameters, see dbBind()
for details.
Specification for the immediate
argument
The immediate
argument supports distinguishing between "direct"
and "prepared" APIs offered by many database drivers.
Passing immediate = TRUE
leads to immediate execution of the
query or statement, via the "direct" API (if supported by the driver).
The default NULL
means that the backend should choose whatever API
makes the most sense for the database, and (if relevant) tries the
other API if the first attempt fails. A successful second attempt
should result in a message that suggests passing the correct
immediate
argument.
Examples for possible behaviors:
DBI backend defaults to
immediate = TRUE
internallyA query without parameters is passed: query is executed
A query with parameters is passed:
params
not given: rejected immediately by the database because of a syntax error in the query, the backend triesimmediate = FALSE
(and gives a message)params
given: query is executed usingimmediate = FALSE
DBI backend defaults to
immediate = FALSE
internallyA query without parameters is passed:
simple query: query is executed
"special" query (such as setting a config options): fails, the backend tries
immediate = TRUE
(and gives a message)
A query with parameters is passed:
params
not given: waiting for parameters viadbBind()
params
given: query is executed
See also
For updates: dbSendStatement()
and dbExecute()
.
Other DBIConnection generics:
DBIConnection-class
,
dbAppendTable()
,
dbAppendTableArrow()
,
dbCreateTable()
,
dbCreateTableArrow()
,
dbDataType()
,
dbDisconnect()
,
dbExecute()
,
dbExistsTable()
,
dbGetException()
,
dbGetInfo()
,
dbGetQueryArrow()
,
dbIsReadOnly()
,
dbIsValid()
,
dbListFields()
,
dbListObjects()
,
dbListResults()
,
dbListTables()
,
dbQuoteIdentifier()
,
dbReadTable()
,
dbReadTableArrow()
,
dbRemoveTable()
,
dbSendQuery()
,
dbSendQueryArrow()
,
dbSendStatement()
,
dbUnquoteIdentifier()
,
dbWriteTable()
,
dbWriteTableArrow()
Other data retrieval generics:
dbBind()
,
dbClearResult()
,
dbFetch()
,
dbFetchArrow()
,
dbFetchArrowChunk()
,
dbGetQueryArrow()
,
dbHasCompleted()
,
dbSendQuery()
,
dbSendQueryArrow()
Examples
con <- dbConnect(RSQLite::SQLite(), ":memory:")
dbWriteTable(con, "mtcars", mtcars)
dbGetQuery(con, "SELECT * FROM mtcars")
#> mpg cyl disp hp drat wt qsec vs am gear carb
#> 1 21.0 6 160.0 110 3.90 2.620 16.46 0 1 4 4
#> 2 21.0 6 160.0 110 3.90 2.875 17.02 0 1 4 4
#> 3 22.8 4 108.0 93 3.85 2.320 18.61 1 1 4 1
#> 4 21.4 6 258.0 110 3.08 3.215 19.44 1 0 3 1
#> 5 18.7 8 360.0 175 3.15 3.440 17.02 0 0 3 2
#> 6 18.1 6 225.0 105 2.76 3.460 20.22 1 0 3 1
#> 7 14.3 8 360.0 245 3.21 3.570 15.84 0 0 3 4
#> 8 24.4 4 146.7 62 3.69 3.190 20.00 1 0 4 2
#> 9 22.8 4 140.8 95 3.92 3.150 22.90 1 0 4 2
#> 10 19.2 6 167.6 123 3.92 3.440 18.30 1 0 4 4
#> 11 17.8 6 167.6 123 3.92 3.440 18.90 1 0 4 4
#> 12 16.4 8 275.8 180 3.07 4.070 17.40 0 0 3 3
#> 13 17.3 8 275.8 180 3.07 3.730 17.60 0 0 3 3
#> 14 15.2 8 275.8 180 3.07 3.780 18.00 0 0 3 3
#> 15 10.4 8 472.0 205 2.93 5.250 17.98 0 0 3 4
#> 16 10.4 8 460.0 215 3.00 5.424 17.82 0 0 3 4
#> 17 14.7 8 440.0 230 3.23 5.345 17.42 0 0 3 4
#> 18 32.4 4 78.7 66 4.08 2.200 19.47 1 1 4 1
#> 19 30.4 4 75.7 52 4.93 1.615 18.52 1 1 4 2
#> 20 33.9 4 71.1 65 4.22 1.835 19.90 1 1 4 1
#> 21 21.5 4 120.1 97 3.70 2.465 20.01 1 0 3 1
#> 22 15.5 8 318.0 150 2.76 3.520 16.87 0 0 3 2
#> 23 15.2 8 304.0 150 3.15 3.435 17.30 0 0 3 2
#> 24 13.3 8 350.0 245 3.73 3.840 15.41 0 0 3 4
#> 25 19.2 8 400.0 175 3.08 3.845 17.05 0 0 3 2
#> 26 27.3 4 79.0 66 4.08 1.935 18.90 1 1 4 1
#> 27 26.0 4 120.3 91 4.43 2.140 16.70 0 1 5 2
#> 28 30.4 4 95.1 113 3.77 1.513 16.90 1 1 5 2
#> 29 15.8 8 351.0 264 4.22 3.170 14.50 0 1 5 4
#> 30 19.7 6 145.0 175 3.62 2.770 15.50 0 1 5 6
#> 31 15.0 8 301.0 335 3.54 3.570 14.60 0 1 5 8
#> 32 21.4 4 121.0 109 4.11 2.780 18.60 1 1 4 2
dbGetQuery(con, "SELECT * FROM mtcars", n = 6)
#> mpg cyl disp hp drat wt qsec vs am gear carb
#> 1 21.0 6 160 110 3.90 2.620 16.46 0 1 4 4
#> 2 21.0 6 160 110 3.90 2.875 17.02 0 1 4 4
#> 3 22.8 4 108 93 3.85 2.320 18.61 1 1 4 1
#> 4 21.4 6 258 110 3.08 3.215 19.44 1 0 3 1
#> 5 18.7 8 360 175 3.15 3.440 17.02 0 0 3 2
#> 6 18.1 6 225 105 2.76 3.460 20.22 1 0 3 1
# Pass values using the param argument:
# (This query runs eight times, once for each different
# parameter. The resulting rows are combined into a single
# data frame.)
dbGetQuery(
con,
"SELECT COUNT(*) FROM mtcars WHERE cyl = ?",
params = list(1:8)
)
#> COUNT(*)
#> 1 0
#> 2 0
#> 3 0
#> 4 11
#> 5 0
#> 6 7
#> 7 0
#> 8 14
dbDisconnect(con)