dbClearResult | R Documentation |
Frees all resources (local and remote) associated with a result set.
This step is mandatory for all objects obtained by calling
dbSendQuery()
or dbSendStatement()
.
dbClearResult(res, ...)
res |
An object inheriting from DBIResult. |
... |
Other arguments passed on to methods. |
dbClearResult()
returns TRUE
, invisibly, for result sets obtained from
dbSendQuery()
,
dbSendStatement()
,
or dbSendQueryArrow()
,
This section gives a complete overview over the flow for the execution of queries that return tabular data as data frames.
Most of this flow, except repeated calling of dbBind()
or dbBindArrow()
,
is implemented by dbGetQuery()
, which should be sufficient
unless you want to access the results in a paged way
or you have a parameterized query that you want to reuse.
This flow requires an active connection established by dbConnect()
.
See also vignette("dbi-advanced")
for a walkthrough.
Use dbSendQuery()
to create a result set object of class
DBIResult.
Optionally, bind query parameters with dbBind()
or dbBindArrow()
.
This is required only if the query contains placeholders
such as ?
or $1
, depending on the database backend.
Optionally, use dbColumnInfo()
to retrieve the structure of the result set
without retrieving actual data.
Use dbFetch()
to get the entire result set, a page of results,
or the remaining rows.
Fetching zero rows is also possible to retrieve the structure of the result set
as a data frame.
This step can be called multiple times.
Only forward paging is supported, you need to cache previous pages
if you need to navigate backwards.
Use dbHasCompleted()
to tell when you're done.
This method returns TRUE
if no more rows are available for fetching.
Repeat the last four steps as necessary.
Use dbClearResult()
to clean up the result set object.
This step is mandatory even if no rows have been fetched
or if an error has occurred during the processing.
It is good practice to use on.exit()
or withr::defer()
to ensure that this step is always executed.
This section gives a complete overview over the flow
for the execution of SQL statements that have side effects
such as stored procedures, inserting or deleting data,
or setting database or connection options.
Most of this flow, except repeated calling of dbBindArrow()
,
is implemented by dbExecute()
, which should be sufficient
for non-parameterized queries.
This flow requires an active connection established by dbConnect()
.
See also vignette("dbi-advanced")
for a walkthrough.
Use dbSendStatement()
to create a result set object of class
DBIResult.
For some queries you need to pass immediate = TRUE
.
Optionally, bind query parameters withdbBind()
or dbBindArrow()
.
This is required only if the query contains placeholders
such as ?
or $1
, depending on the database backend.
Optionally, use dbGetRowsAffected()
to retrieve the number
of rows affected by the query.
Repeat the last two steps as necessary.
Use dbClearResult()
to clean up the result set object.
This step is mandatory even if no rows have been fetched
or if an error has occurred during the processing.
It is good practice to use on.exit()
or withr::defer()
to ensure that this step is always executed.
An attempt to close an already closed result set issues a warning
for dbSendQuery()
,
dbSendStatement()
,
and dbSendQueryArrow()
,
dbClearResult()
frees all resources associated with retrieving
the result of a query or update operation.
The DBI backend can expect a call to dbClearResult()
for each
dbSendQuery()
or dbSendStatement()
call.
Other DBIResult generics:
DBIResult-class
,
dbBind()
,
dbColumnInfo()
,
dbFetch()
,
dbGetInfo()
,
dbGetRowCount()
,
dbGetRowsAffected()
,
dbGetStatement()
,
dbHasCompleted()
,
dbIsReadOnly()
,
dbIsValid()
,
dbQuoteLiteral()
,
dbQuoteString()
Other DBIResultArrow generics:
DBIResultArrow-class
,
dbBind()
,
dbFetchArrow()
,
dbFetchArrowChunk()
,
dbHasCompleted()
,
dbIsValid()
Other data retrieval generics:
dbBind()
,
dbFetch()
,
dbFetchArrow()
,
dbFetchArrowChunk()
,
dbGetQuery()
,
dbGetQueryArrow()
,
dbHasCompleted()
,
dbSendQuery()
,
dbSendQueryArrow()
Other command execution generics:
dbBind()
,
dbExecute()
,
dbGetRowsAffected()
,
dbSendStatement()
con <- dbConnect(RSQLite::SQLite(), ":memory:")
rs <- dbSendQuery(con, "SELECT 1")
print(dbFetch(rs))
dbClearResult(rs)
dbDisconnect(con)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.