dbplyr breaking changes

• v2.3.4 \u2192 v2.4.0breaking

  Using `compute(temporary = FALSE)` without providing a name is now deprecated (@mgirlich, #1154).

• v2.3.4 \u2192 v2.4.0breaking

  `ntile()`'s first argument has been renamed from `order_by` to `x` to match the interface of `dplyr::ntile()` (@mgirlich, #1242).

• v2.3.4 \u2192 v2.4.0breaking

  `simulate_vars()` and `simulate_vars_is_typed()` were removed as they weren't used and tidyselect now offers `tidyselect_data_proxy()` and `tidyselect_data_has_predicates()` (@mgirllich, #1199).

• v2.3.4 \u2192 v2.4.0breaking

  `sql_not_supported()` now expects a function name without parentheses.

• v2.3.4 \u2192 v2.4.0breaking

  `sql_query_append()`, `sql_query_insert()`, `sql_query_update()`, `sql_query_upsert()`, and `sql_query_delete()` changed their arguments to make them more consistent to the other `sql_query_*()` functions:

• v2.3.0 \u2192 v2.3.1breaking

  `window_order()` now only accepts bare symbols or symbols wrapped in `desc()`. This breaking change is necessary to allow `select()` to drop and rename variables used in `window_order()` (@mgirlich, #1103).

• v1.3.0 \u2192 v1.4.0breaking

  ``Error: `con` must not be NULL``: If you see this error, it probably means that you have probably 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).

• v1.3.0 \u2192 v1.4.0breaking

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

Get this data programmatically \u2014 free, no authentication.