Changes in version 0.3.2 (2023-01-09) - Throws an error if called from an incompatible version of tidyquery (#32) - Minor bugfixes and improvements Changes in version 0.3.1 (2021-01-17) - Queries can contain multibyte characters (#21) - Queries can have no whitespace around keywords (#27) - substring_index() translates when tidyverse = TRUE (#29) - embedded nuls warnings are silenced (#30) - Syntactically invalid column names are allowed in backticks (#31) - Minor bugfixes and improvements Changes in version 0.3.0 (2020-05-10) - ORDER BY clause can include NULLS FIRST and NULLS LAST (#12, @StevenHibble) - Translations of expressions in the ORDER BY clause now use -xtfrm() instead of the attribute decreasing to indicate descending order (@StevenHibble) - Parentheses can enclose table names and joins in the FROM clause (#23) - More Microsoft SQL Server functions now translate (#26, @StevenHibble) - Minor bugfixes and improvements Changes in version 0.2.0 (2020-01-16) - BETWEEN expressions with quotes in operands translate correctly (#13) - Line comments (--) and block comments (/* */) are removed from queries (#14) - coalesce() translates correctly when tidyverse = FALSE (#15, #17) - CASE expressions translate (#16, #18) - Table aliases can be used in queries (#19) - SQL-92-style (explicit) join queries translate (#20) - Continuous integration and coverage tests - Minor bugfixes and improvements Changes in version 0.1.1 (2019-09-05) - Output indicates when queries aggregate - List returned by parse_query() has attribute aggregate set to TRUE if query aggregates (#8) - When translating an aggregate query, sublist select returned by by parse_query() has logical vector attribute aggregate indicating whether each expression in the SELECT list aggregates (#9) - When translating an aggregate query with an ORDER BY clause, sublist order_by returned by by parse_query() has logical vector attribute aggregate indicating whether each expression in the ORDER BY clause aggregates (#11) - Translation of multiple CAST and BETWEEN expressions in a single expression no longer fails (#10) - Minor bugfixes and improvements Changes in version 0.1.0 (2019-09-03) - First CRAN release - Column names that match SQL function names are not converted to lowercase (#1) - Outputted expressions use vectorized logical operators (#2) - Successive occurrences of binary symbolic operators are replaced (#3) - Column names that match function names are not replaced (#4) - Vulnerabilities that permitted use of disallowed functions are resolved (#5, #7) - Column names can contain periods (#6)