The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
tidyr::fill()
now works with PrestoConnection. (#233,
thanks to @copernican for reporting the issue and
@mgirlich for
providing upstream utility functions in dbplyr)RPresto
is now compatible with dbplyr
2.4.0. We updated the minimum version requirement of dbplyr
to be 2.3.3.compute()
uses simple table name rather than wrapped it
in as.sql()
.compute()
returns a “table doesn’t
exist” error when the computed table contains CTE. (#243)tbl()
and db_query_rows()
args to fix warnings by R CMD CHECK on S3 generic consistency raised by
CRAN. (#245)dbplyr
2.3.0 compatibility issues. (#237)kerberos_configs()
to generate
Kerberos header configs that can be passed to the
request.config
argument of dbConnect()
. (#202
and #221). Thanks to @suzzettedetorres for providing
this solution.dbplyr::in_schema()
and DBI::Id()
besides the
usual character table name. (#228)dbRenameTable()
function to rename table
name.dbListFields
now works with identifier name which in
turn supports the use of in_schema()
in tbl()
(#200)dbQuoteLiteral()
and dbAppendTable()
implementations.dbWriteTable()
implementation to use
dbCreateTable()
and dbAppendTable()
. It also
supports all default arguments now (#199)dbWriteTable()
gains a use.one.query
option to use a single CREATE TABLE AS
query.data.frame
to
tibble
to offer better printing and be more consistent with
other DBI-compatible datawarehouse packagesDate
classes
in R; TIMESTAMP types are translated to POSIXct
classes;
TIME types are translated to difftime
classes; INTERVAL
types are translated to Duration
classes)integer64
, integer
, numeric
, or
character
). (#61)vignette("primitive-types")
and
vignette("complex-types")
)dbExistsTable()
error when quoted identifier is
supplied as name
is fixed (#167)dplyr
and dbplyr
method
implementations. See backend-implementation.md
for the
details.
dbplyr::sql_query_save()
dplyr::db_list_tables()
dplyr::db_has_table()
dplyr::db_write_table()
dbplyr::db_copy_to()
dplyr::copy_to()
method for src_presto
and
PrestoConnection
dplyr::tbl()
method for
PrestoConnection
dbplyr::db_compute()
dplyr::compute()
PrestoConnection
gains a request.config
slot whereby users can set extra Curl configs (as returned by
httr::config()
to GET/POST requests. (#173)styler::style_pkg()
. A
notable change is to user double quotes everywhere instead of a
combination of single and double quotes. (#174)vignette("common-table-expressions")
) (#175)dbConnect()
now uses empty string “” (rather than UTC)
as the default session.timezone which translates to the Presto server
timezone.dbConnect()
and src_presto()
gain an
output.timezone
argument which can be used to control how
TIME WITH TZ
and TIMESTAMP
values are
represented in the output tibble.dbGetQuery()
and dbSendQuery()
gain a
quiet
argument which defaults to
getOption("rpresto.quiet")
which is NA
if not
set. (#191)dplyr
backend
implementation[[
translation from []
subscript
operator to ELEMENT_AT()
(#132)is.infinite()
is incorrectly
translated to IS_FINITE()
instead of
IS_INFINITE()
in SQL (#139)median()
and
quantile()
and suggested approx_quantile()
instead. (#120)dbClearResult
to the API change, we now need to
DELETE
/v1/query/<query_id>
.query.id
slot to PrestoResult
.[[
to allow indexing arrays and maps with
dplyr (#110).dbplyr
1.4.0.as.<data_type>
style casting for
dplyr (#97).SET/RESET SESSION
queries are now correctly respected
when used under dbGetQuery
. PrestoConnection
no longer has parameters
slot but dbConnect
remains backward compatible. Manual change to parameter is still
possible via conn@session$setParameter()
(#77)dbplyr
. This should be
backwards compatible back to dplyr 0.4.3 (#76)json
to data.frame
construction from pure R to Rcpp for 10x speed gains! (thanks @saurfang) (#57, #58)session.timezone
parameter to
dbConnect
and src_presto
which defaults to
UTC. This affects the timestamps returned for Presto data types
“TIMESTAMP”. We handle the ambiguity by assigning a time zone to
every POSIXct column returned. Note that if you are doing
as.character()
directly on these columns, the values you
obtain will be different from what happened before.LIMIT 0
queries specifically.src_presto
.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.