Liang Zhang

Weirdly, if I choose "ODBC ANSI Driver" when configuring data source on Windows, DBeaver will show Chinese characters as normal. However, ANSI is not recommended when data stores Unicode characters.

Also found this [SO](https://stackoverflow.com/a/71426424/5996475). So perhaps it is a documentation issue? But I do think it is better to support this behavior because base `startsWith()` supports this, and it is...

Ah, I am sorry. This might have been solved by #340. So when will there be a new release?

Here the same. No `css` detected? 

Here is the same issue. ```r conn Error in .local(conn, statement, ...) : #> could not run statement: The used command is not allowed with this MySQL version ``` `MySQL`...

I could confirm that the table to be written was actually created, only with no records of data but the field names. ```r library(DBI) con [1] "mtcars" "test" dbReadTable(con, "test")...

The reason might be that there is no manual dependent data building step, and the compiled data is corrupted for Windows?

Does this mean Ubuntu 22.04 is not supported yet? When using {pak} on Ubuntu 22.04 (WSL), using `pak::pkg_install()` and `pak::pak()` both results in following error: ``` r pak::pkg_install("tidyverse") #> #>...

Thanks for this package. Current workaround (or even a better solution) is to add this line to your setup chunk of "Rmd" file: ```r knitr::opts_knit$set(root.dir = here::here()) ``` This will...

Got it! How about implement it anyway, but document its possible performance loss?