Skip to content

dbplyr 2.5.0

CRAN release: 2024-03-19

Improved tools for qualified table names

  • Specification of table names with schema/catalogs has been overhauled to make it simpler. This includes the following features and fixes:

    • The simplest way to refer to a qualified table is now to wrap it in I(), e.g. I("schema_name.table_name").

    • Use of sql() and ident_q() inside in_catalog() and in_schema() is once again supported (#1388).

    • It’s ok to use ident_q() once again (#1413) and you should no longer see unsuppressable warnings about using in_schema() (#1408).

    • The names of the arguments to Id() no longer matter, only their order (#1416). Additionally, thanks to changes to the DBI package, you no longer need to name each argument.

    • If you accidentally pass a named vector to any of the database identifer functions, those names will be automatically stripped (#1404).

    • tbl_sql(check_from) is now deprecated.

  • dbplyr now exports some tools to work with the internal table_path class which is useful for certain backends that need to work with this data structure (#1300).

Improved SQL

  • New translations for clock functions add_years(), add_days(), date_build(), get_year(), get_month(), get_day(), and base::difftime() on SQL server, Redshift, Snowflake, and Postgres.

  • select() will keep computed columns used to arrange() subqueries that are eliminated by a subsequent select (@ejneer, #1437).

  • semi_join() will no longer inline away an aggregate filter (i.e. HAVING clause) that was followed by a select() (@ejneer, #1474)

  • Improved function translations:

    • Functions qualified with the base namespace are now also translated, e.g. base::paste0(x, "_1") is now translated (@mgirlich, #1022).

    • -1 + x now generates a translation instead erroring (#1420).

    • x$name never attempts to evaluate name (#1368).

    • You can once again use NULL on the LHS of an infix operator in order to generate SQL with unusual syntax (#1345).

    • Namespaced calls now error if the function doesn’t exist, or a translation is not available (#1426).

    • lead() translation coerces n to an integer.

  • Databricks: now supports creating non-temporary tables too (#1418).

  • Oracle:

  • Snowflake (@nathanhaigh, #1406)

    • Added support for str_starts() and str_ends() via REGEXP_INSTR()

    • Refactored str_detect() to use REGEXP_INSTR() so now supports regular expressions.

    • Refactored grepl() to use REGEXP_INSTR() so now supports case-insensitive matching through grepl(..., = TRUE)

  • SQL server:

  • MySQL: as.integer() gets correct translation (@krlmlr, #1375).

Minor improvements and bug fixes

  • Deprecation status of functions deprecated in previous versions (at least 2 years old) have been advanced. In particular, src_sql() is now defunct, as is the use of partial_eval() with character data.

  • Database errors now show the generated SQL, which hopefully will make it faster to track down problems (#1401).

  • When dbplyr creates an index on a table in a schema (e.g. schema.table), it now only includes the table name in the index name, not the schema name.

  • The class of remote sources now includes all S4 class names, not just the first (#918).

  • compute() passes additional arguments all the way to sql_query_save()-methods (@rsund).

  • db_sql_render() correctly passes on ... when re-calling with sql_options set (#1394).

  • reframe() now gives an informative error that it isn’t supported (#1148).

  • rows_patch(in_place = FALSE) now works when more than one column should be patched (@gorcha, #1443).

  • New simulate_mariadb() (@krlmlr, #1375).

  • sql_translator() now checks for duplicated definitions (@krlmlr, #1374).

dbplyr 2.4.0

CRAN release: 2023-10-26

Breaking changes

Improved SQL

Minor improvements and bug fixes

Backend specific improvements

dbplyr 2.3.4

CRAN release: 2023-09-26

  • Hot patch release to resolve R CMD check failures.

dbplyr 2.3.3

CRAN release: 2023-07-07

  • Hot patch to fix R CMD check issues

dbplyr 2.3.2

CRAN release: 2023-03-21

  • Hot patch to fix R CMD check issues

dbplyr 2.3.1

CRAN release: 2023-02-24

Breaking changes

Improved error messages

  • quantile() and median() now error for SQL Server when used in summarise() and for PostgreSQL when used in mutate() as they can’t be properly translated (@mgirlich, #1110).

  • Added an informative error for unsupported join arguments unmatched and multiple (@mgirlich).

  • Using predicates, e.g. where(is.integer), in across() now produces an error as they never worked anyway (@mgirlich, #1169).

  • Catch unsupported argument pivot_wider(id_expand = TRUE) and pivot_longer(cols_vary) (@mgirlich, #1109).

Bug fixes in SQL generation

Minor improvements and bug fixes

dbplyr 2.3.0

CRAN release: 2023-01-16

New features

SQL optimisation

Improved error messages

  • Many errors have been improved and now show the function where the error happened instead of a helper function (@mgirlich, #907).

  • Errors produced by the database, e.g. in collect() or rows_*(), now show the verb where the error happened (@mgirlich).

  • window_order() now produces a better error message when applied to a data frame (@mgirlich, #947).

  • Using a named across() now gives a clear error message (@mgirlich, #761).

Minor improvements and bug fixes

Backend specific improvements

dbplyr 2.2.1

CRAN release: 2022-06-27

dbplyr 2.2.0

CRAN release: 2022-06-05

New features

Improvements to SQL generation

Minor improvements and bug fixes

dbplyr 2.1.1

CRAN release: 2021-04-06

dbplyr 2.1.0

CRAN release: 2021-02-03

New features

  • Thanks to @mgirlich, dbplyr gains support for key verbs from tidyr: pivot_longer() (#532), pivot_wider() (#543), expand() (#538), complete() (#538), replace_na() (#538), fill() (#566).

  • @mgirlich is now a dbplyr author in recognition of his significant and sustained contributions.

  • across() implementation has been rewritten to support more inputs: it now translates formulas (#525), works with SQL functions that don’t have R translations (#534), and work with NULL (#554)

  • summarise() now supports argument .groups (@mgirlich, #584).

SQL translation

Minor improvements and bug fixes

dbplyr 2.0.0

CRAN release: 2020-11-03

dplyr 1.0.0 compatibility

SQL generation

  • Documentation has been radically improved with new topics for each major verb and each backend giving more details about the SQL translation.

  • intersect(), union() and setdiff() gain an all argument to add the ALL argument (#414).

  • Join functions gains a na_matches argument that allows you to control whether or not NA (NULL) values match other NA values. The default is "never", which is the usual behaviour in databases. You can set na_matches = "na" to match R’s usual join behaviour (#180). Additional arguments error (instead of being silently swallowed) (#382).

  • Joins now only use aliases where needed to disambiguate columns; this should make generated queries more readable.

  • Subqueries no longer include an ORDER BY clause. This is not part of the SQL spec, and has very limited support across databases. Now such queries generate a warning suggesting that you move your arrange() call later in the pipeline (#276). (There’s one exception: ORDER BY is still generated if LIMIT is present; this tends to affect the returns rows but not necessarily their order).

  • Subquery names are now scoped within the query. This makes query text deterministic which helps some query optimisers/cachers (#336).

  • sql_optimise() now can partially optimise a pipeline; due to an unfortunate bug it previously gave up too easily.

  • in_schema() quotes each input individually (#287) (use sql() to opt out of quoting, if needed). And DBI::Id() should work anywhere that in_schema() does.

SQL translation

  • Experimental new SAP HANA backend (#233). Requires the latest version of odbc.

  • All backends:

  • blob vectors can now be used with !! and !!! operators, for example in filter() (@okhoma, #433)

  • MySQL uses standard SQL for index creation.

  • MS SQL translation does better a distinguishing between bit and boolean (#377, #318). if and ifelse once again generate IIF, creating simpler expressions. as.*() function uses TRY_CAST() instead of CAST() for version 11+ (2012+) (@DavidPatShuiFong, #380).

  • odbc no longer translates count(); this was an accidental inclusion.

  • Oracle translation now depends on Oracle 12c, and uses a “row-limiting” clause for head(). It gains translations for today() and now(), and improved as.Date() translation (@rlh1994, #267).

  • PostgreSQL: new translations for lubridate period functions years(), months(), days(), and floor_date() (@bkkkk, #333) and stringr functions str_squish(), str_remove(), and str_remove_all() (@shosaco).

  • New RedShift translations when used with RPostgres::Redshift().

  • SQLite gains translations for lubridate functions today(), now(), year(), month(), day(), hour(), minute(), second(),yday() (#262), and correct translation for median() (#357).


If you are the author of a dbplyr backend, please see vignette("backend-2") for details.

Minor improvements and bug fixes

  • All old lazy eval shims have been removed. These have been deprecated for some time.

  • Date-time escaping methods for Athena and Presto have moved to the packages where they belong.

  • Attempting to embed a Shiny reactive in a query now gives a helpful error (#439).

  • copy_lahman() and copy_nycflights13() (and hence nycflights13_sqlite()) and friends now return DBI connections rather than the now deprecated src_dbi() (#440).

  • copy_to() can now overwrite when table is specified with schema (#489), and gains an in_transaction argument used to optionally suppress the transaction wrapper (#368).

  • distinct() no longer duplicates column if grouped (#354).

  • transmute() now correctly tracks variables it needs when creating subqueries (#313).

  • mutate() grouping variables no longer generates a downstream error (#396)

  • mutate() correctly generates subqueries when you re-use the same variable three or more times (#412).

  • window_order() overrides ordering, rather than appending to it.

dbplyr 1.4.4

CRAN release: 2020-05-27

dbplyr 1.4.3

CRAN release: 2020-04-19

dbplyr 1.4.2

CRAN release: 2019-06-17

  • Fix bug when partially evaluating unquoting quosure containing a single symbol (#317)

  • Fixes for rlang and dpylr compatibility.

dbplyr 1.4.1

CRAN release: 2019-06-05

Minor improvements to SQL generation

dbplyr 1.4.0

CRAN release: 2019-04-23

Breaking changes

  • Error: `con` must not be NULL: If you see this error, it probably means that you have forgotten to pass con down to a dbplyr function. Previously, dbplyr defaulted to using simulate_dbi() which introduced subtle escaping bugs. (It’s also possible I have forgotten to pass it somewhere that the dbplyr tests don’t pick up, so if you can’t figure it out, please let me know).

  • Subsetting ([[, $, and [) functions are no longer evaluated locally. This makes the translation more consistent and enables useful new idioms for modern databases (#200).

New features

SQL translations

  • New translations for some lubridate functions: today(), now(), year(), month(), day(), hour(), minute(), second(), quarter(), yday() (@colearendt, @derekmorr). Also added new translation for as.POSIXct().

  • New translations for stringr functions: str_c(), str_sub(), str_length(), str_to_upper(), str_to_lower(), and str_to_title() (@colearendt). Non-translated stringr functions throw a clear error.

  • New translations for bitwise operations: bitwNot(), bitwAnd(), bitwOr(), bitwXor(), bitwShiftL(), and bitwShiftR(). Unlike the base R functions, the translations do not coerce arguments to integers (@davidchall, #235).

  • New translation for x[y] to CASE WHEN y THEN x END. This enables sum(a[b == 0]) to work as you expect from R (#202). y needs to be a logical expression; if not you will likely get a type error from your database.

  • New translations for x$y and x[["y"]] to x.y, enabling you to index into nested fields in databases that provide them (#158).

  • The .data and .env pronouns of tidy evaluation are correctly translated (#132).

  • New translation for median() and quantile(). Works for all ANSI compliant databases (SQL Server, Postgres, MariaDB, Teradata) and has custom translations for Hive. Thanks to @edavidaja for researching the SQL variants! (#169)

  • na_if() is correct translated to NULLIF() (rather than NULL_IF) (#211).

  • n_distinct() translation throws an error when given more than one argument. (#101, #133).

  • New default translations for paste(), paste0(), and the hyperbolic functions (these previously were only available for ODBC databases).

  • Corrected translations of pmin() and pmax() to LEAST() and GREATEST() for ANSI compliant databases (#118), to MIN() and MAX() for SQLite, and to an error for SQL server.

  • New translation for switch() to the simple form of CASE WHEN (#192).

SQL simulation

SQL simulation makes it possible to see what dbplyr will translate SQL to, without having an active database connection, and is used for testing and generating reprexes.

  • SQL simulation has been overhauled. It now works reliably, is better documented, and always uses ANSI escaping (i.e. ` for field names and ' for strings).

  • tbl_lazy() now actually puts a dbplyr::src in the $src field. This shouldn’t affect any downstream code unless you were previously working around this weird difference between tbl_lazy and tbl_sql classes. It also includes the src class in its class, and when printed, shows the generated SQL (#111).

Database specific improvements

  • MySQL/MariaDB

    • Translations also applied to connections via the odbc package (@colearendt, #238)

    • Basic support for regular expressions via str_detect() and
      str_replace_all() (@colearendt, #168).

    • Improved translation for as.logical(x) to IF(x, TRUE, FALSE).

  • Oracle

  • Postgres

    • Basic support for regular expressions via str_detect() and
      str_replace_all() (@colearendt, #168).
  • SQLite

    • explain() translation now generates EXPLAIN QUERY PLAN which generates a higher-level, more human friendly explanation.
  • SQL server

    • Improved translation for as.logical(x) to CAST(x as BIT) (#250).

    • Translates paste(), paste0(), and str_c() to +.

    • copy_to() method applies temporary table name transformation earlier so that you can now overwrite temporary tables (#258).

    • db_write_table() method uses correct argument name for passing along field types (#251).

Minor improvements and bug fixes

  • Aggregation functions only warn once per session about the use of na.rm = TRUE (#216).

  • table names generated by random_table_name() have the prefix “dbplyr_”, which makes it easier to find them programmatically (@mattle24, #111)

  • Functions that are only available in a windowed (mutate()) query now throw an error when called in a aggregate (summarise()) query (#129)

  • arrange() understands the .by_group argument, making it possible sort by groups if desired. The default is FALSE (#115)

  • distinct() now handles computed variables like distinct(df, y = x + y) (#154).

  • escape(), sql_expr() and build_sql() no longer accept con = NULL as a shortcut for con = simulate_dbi(). This made it too easy to forget to pass con along, introducing extremely subtle escaping bugs. win_over() gains a con argument for the same reason.

  • New escape_ansi() always uses ANSI SQL 92 standard escaping (for use in examples and documentation).

  • mutate(df, x = NULL) drops x from the output, just like when working with local data frames (#194).

  • partial_eval() processes inlined functions (including rlang lambda functions). This makes dbplyr work with more forms of scoped verbs like df %>% summarise_all(~ mean(.)), df %>% summarise_all(list(mean)) (#134).

  • sql_aggregate() now takes an optional argument f_r for passing to check_na_rm(). This allows the warning to show the R function name rather than the SQL function name (@sverchkov, #153).

  • sql_infix() gains a pad argument for the rare operator that doesn’t need to be surrounded by spaces.

  • sql_prefix() no longer turns SQL functions into uppercase, allowing for correct translation of case-sensitive SQL functions (#181, @mtoto).

  • summarise() gives a clear error message if you refer to a variable created in that same summarise() (#114).

  • New sql_call2() which is to rlang::call2() as sql_expr() is to rlang::expr().

  • show_query() and explain() use cat() rather than message.

  • union(), union_all(), setdiff() and intersect() do a better job of matching columns across backends (#183).

dbplyr 1.3.0

CRAN release: 2019-01-09

  • Now supports for dplyr 0.8.0 (#190) and R 3.1.0

API changes

  • Calls of the form dplyr::foo() are now evaluated in the database, rather than locally (#197).

  • vars argument to tbl_sql() has been formally deprecated; it hasn’t actually done anything for a while (#3254).

  • src and tbl objects now include a class generated from the class of the underlying connection object. This makes it possible for dplyr backends to implement different behaviour at the dplyr level, when needed. (#2293)

SQL translation

Minor improvements and bug fixes

  • copy_to() will only remove existing table when overwrite = TRUE and the table already exists, eliminating a confusing “NOTICE” from PostgreSQL (#3197).

  • partial_eval() handles unevaluated formulas (#184).

  • pull.tbl_sql() now extracts correctly from grouped tables (#3562).

  • sql_render.op() now correctly forwards the con argument (@kevinykuo, #73).

dbplyr 1.2.2

CRAN release: 2018-07-25

  • R CMD check fixes

dbplyr 1.2.1

CRAN release: 2018-02-19

  • Forward compatibility fixes for rlang 0.2.0

dbplyr 1.2.0

CRAN release: 2018-01-03

New top-level translations

  • New translations for

  • dbplyr now supplies appropriate translations for the RMariaDB and RPostgres packages (#3154). We generally recommend using these packages in favour of the older RMySQL and RPostgreSQL packages as they are fully DBI compliant and tested with DBItest.

New features

  • copy_to() can now “copy” tbl_sql in the same src, providing another way to cache a query into a temporary table (#3064). You can also copy_to tbl_sqls from another source, and copy_to() will automatically collect then copy.

  • Initial support for stringr functions: str_length(), str_to_upper(), str_to_lower(), str_replace_all(), str_detect(), str_trim(). Regular expression support varies from database to database, but most simple regular expressions should be ok.

Tools for developers

Minor improvements and bug fixes

  • Multiple head() calls in a row now collapse to a single call. This avoids a printing problem with MS SQL (#3084).

  • escape() now works with integer64 values from the bit64 package (#3230)

  • if, ifelse(), and if_else() now correctly scope the false condition so that it only applies to non-NULL conditions (#3157)

  • ident() and ident_q() handle 0-length inputs better, and should be easier to use with S3 (#3212)

  • in_schema() should now work in more places, particularly in copy_to() (#3013, @baileych)

  • SQL generation for joins no longer gets stuck in a endless loop if you request an empty suffix (#3220).

  • mutate() has better logic for splitting a single mutate into multiple subqueries (#3095).

  • Improved paste() and paste0() support in MySQL, PostgreSQL (#3168), and RSQLite (#3176). MySQL and PostgreSQL gain support for str_flatten() which behaves like paste(x, collapse = "-") (but for technical reasons can’t be implemented as a straightforward translation of paste()).

  • same_src.tbl_sql() now performs correct comparison instead of always returning TRUE. This means that copy = TRUE once again allows you to perform cross-database joins (#3002).

  • select() queries no longer alias column names unnecessarily (#2968, @DavisVaughan).

  • select() and rename() are now powered by tidyselect, fixing a few renaming bugs (#3132, #2943, #2860).

  • summarise() once again performs partial evaluation before database submission (#3148).

  • test_src() makes it easier to access a single test source.

Database specific improvements

  • MS SQL

    • Better support for temporary tables (@Hong-Revo)

    • Different translations for filter/mutate contexts for: NULL evaluation (, is.null()), logical operators (!, &, &&, |, ||), and comparison operators (==, !=, <, >, >=, <=)

  • MySQL: copy_to() (via db_write_table()) correctly translates logical variables to integers (#3151).

  • odbc: improved n() translation in windowed context.

  • SQLite: improved na_if translation (@cwarden)

  • PostgreSQL: translation for grepl() added (@zozlak)

  • Oracle: changed VARVHAR to VARCHAR2 datatype (@washcycle, #66)

dbplyr 1.1.0

CRAN release: 2017-06-27

New features

Minor improvements and bug fixes

  • x %in% c(1) now generates the same SQL as x %in% 1 (#2898).

  • head(tbl, 0) is now supported (#2863).

  • select()ing zero columns gives a more information error message (#2863).

  • Variables created in a join are now disambiguated against other variables in the same table, not just variables in the other table (#2823).

  • PostgreSQL gains a better translation for round() (#60).

  • Added custom db_analyze_table() for MS SQL, Oracle, Hive and Impala (@edgararuiz)

  • Added support for sd() for aggregate and window functions (#2887) (@edgararuiz)

  • You can now use the magrittr pipe within expressions, e.g. mutate(mtcars, cyl %>% as.character()).

  • If a translation was supplied for a summarise function, but not for the equivalent windowed variant, the expression would be translated to NULL with a warning. Now sql_variant() checks that all aggregate functions have matching window functions so that correct translations or clean errors will be generated (#2887)

dbplyr 1.0.0

CRAN release: 2017-06-09

New features

  • tbl() and copy_to() now work directly with DBI connections (#2423, #2576), so there is no longer a need to generate a dplyr src.

    con <- DBI::dbConnect(RSQLite::SQLite(), ":memory:")
    copy_to(con, mtcars)
    mtcars2 <- tbl(con, "mtcars")
  • glimpse() now works with remote tables (#2665)

  • dplyr has gained a basic SQL optimiser, which collapses certain nested SELECT queries into a single query (#1979). This will improve query execution performance for databases with less sophisticated query optimisers, and fixes certain problems with ordering and limits in subqueries (#1979). A big thanks goes to @hhoeflin for figuring out this optimisation.

  • compute() and collapse() now preserve the “ordering” of rows. This only affects the computation of window functions, as the rest of SQL does not care about row order (#2281).

  • copy_to() gains an overwrite argument which allows you to overwrite an existing table. Use with care! (#2296)

  • New in_schema() function makes it easy to refer to tables in schema: in_schema("my_schema_name", "my_table_name").

Deprecated and defunct

  • query() is no longer exported. It hasn’t been useful for a while so this shouldn’t break any code.

Verb-level SQL generation

  • Partial evaluation occurs immediately when you execute a verb (like filter() or mutate()) rather than happening when the query is executed (#2370).

  • mutate.tbl_sql() will now generate as many subqueries as necessary so that you can refer to variables that you just created (like in mutate with regular dataframes) (#2481, #2483).

  • SQL joins have been improved:

    • SQL joins always use the ON ... syntax, avoiding USING ... even for natural joins. Improved handling of tables with columns of the same name (#1997, @javierluraschi). They now generate SQL more similar to what you’d write by hand, eliminating a layer or two of subqueries (#2333)

    • [API] They now follow the same rules for including duplicated key variables that the data frame methods do, namely that key variables are only kept from x, and never from y (#2410)

    • [API] The sql_join() generic now gains a vars argument which lists the variables taken from the left and right sides of the join. If you have a custom sql_join() method, you’ll need to update how your code generates joins, following the template in sql_join.generic().

    • full_join() throws a clear error when you attempt to use it with a MySQL backend (#2045)

    • right_join() and full_join() now return results consistent with local data frame sources when there are records in the right table with no match in the left table. right_join() returns values of by columns from the right table. full_join() returns coalesced values of by columns from the left and right tables (#2578, @ianmcook)

  • group_by() can now perform an inline mutate for database backends (#2422).

  • The SQL generation set operations (intersect(), setdiff(), union(), and union_all()) have been considerably improved.

    By default, the component SELECT are surrounded with parentheses, except on SQLite. The SQLite backend will now throw an error if you attempt a set operation on a query that contains a LIMIT, as that is not supported in SQLite (#2270).

    All set operations match column names across inputs, filling in non-matching variables with NULL (#2556).

  • rename() and group_by() now combine correctly (#1962)

  • tbl_lazy() and lazy_tbl() have been exported. These help you test generated SQL with out an active database connection.

  • ungroup() correctly resets grouping variables (#2704).

Vector-level SQL generation

  • New as.sql() safely coerces an input to SQL.

  • More translators for as.character(), as.integer() and as.double() (#2775).

  • New ident_q() makes it possible to specifier identifiers that do not need to be quoted.

  • Translation of inline scalars:

    • Logical values are now translated differently depending on the backend. The default is to use “true” and “false” which is the SQL-99 standard, but not widely support. SQLite translates to “0” and “1” (#2052).

    • Inf and -Inf are correctly escaped

    • Better test for whether or not a double is similar to an integer and hence needs a trailing 0.0 added (#2004).

    • Quoting defaults to DBI::dbEscapeString() and DBI::dbQuoteIdentifier() respectively.

  • :: and ::: are handled correctly (#2321)

  • x %in% 1 is now correctly translated to x IN (1) (#511).

  • ifelse() and if_else() use correct argument names in SQL translation (#2225).

  • ident() now returns an object with class c("ident", "character"). It no longer contains “sql” to indicate that this is not already escaped.

  • and is.null() gain extra parens in SQL translation to preserve correct precedence (#2302).

  • [API] log(x, b) is now correctly translated to the SQL log(b, x) (#2288). SQLite does not support the 2-argument log function so it is translated to log(x) / log(b).

  • nth(x, i) is now correctly translated to nth_value(x, i).

  • n_distinct() now accepts multiple variables (#2148).

  • [API] substr() is now translated to SQL, correcting for the difference in the third argument. In R, it’s the position of the last character, in SQL it’s the length of the string (#2536).

  • win_over() escapes expression using current database rules.


Minor bug fixes and improvements

  • collect() once again defaults to return all rows in the data (#1968). This makes it behave the same as and as_tibble().

  • collect() only regroups by variables present in the data (#2156)

  • collect() will automatically LIMIT the result to the n, the number of rows requested. This will provide the query planner with more information that it may be able to use to improve execution time (#2083).

  • common_by() gets a better error message for unexpected inputs (#2091)

  • copy_to() no longer checks that the table doesn’t exist before creation, instead preferring to fall back on the database for error messages. This should reduce both false positives and false negative (#1470)

  • copy_to() now succeeds for MySQL if a character column contains NA (#1975, #2256, #2263, #2381, @demorenoc, @eduardgrebe).

  • copy_to() now returns its output invisibly (since you’re often just calling for the side-effect).

  • distinct() reports improved variable information for SQL backends. This means that it is more likely to work in the middle of a pipeline (#2359).

  • Ungrouped do() on database backends now collects all data locally first (#2392).

  • Call dbFetch() instead of the deprecated fetch() (#2134). Use DBI::dbExecute() for non-query SQL commands (#1912)

  • explain() and show_query() now invisibly return the first argument, making them easier to use inside a pipeline.

  • print.tbl_sql() displays ordering (#2287) and prints table name, if known.

  • print(df, n = Inf) and head(df, n = Inf) now work with remote tables (#2580).

  • db_desc() and sql_translate_env() get defaults for DBIConnection.

  • Formatting now works by overriding the tbl_sum() generic instead of print(). This means that the output is more consistent with tibble, and that format() is now supported also for SQL sources (tidyverse/dbplyr#14).

Lazy ops

  • [API] The signature of op_base has changed to op_base(x, vars, class)

  • [API] translate_sql() and partial_eval() have been refined:

    • translate_sql() no longer takes a vars argument; instead call partial_eval() yourself.

    • Because it no longer needs the environment translate_sql()_ now works with a list of dots, rather than a lazy_dots.

    • partial_eval() now takes a character vector of variable names rather than a tbl.

    • This leads to a simplification of the op data structure: dots is now a list of expressions rather than a lazy_dots.

  • [API] op_vars() now returns a list of quoted expressions. This enables escaping to happen at the correct time (i.e. when the connection is known).