-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't select non-Latin1 character literals #15
Milestone
Comments
Comment by jghigginson78 I haven't used R for a while but used to use the following command after connecting with dbConnect. |
krlmlr
added a commit
that referenced
this issue
Sep 24, 2017
- Improve documentation for location of option files, with reference (#18). - Fully support parametrized queries (#22, #27, #39). - Use snake_case in C++ code. - Make transactions compliant to the spec (#38, #49). - 64-bit integers are now supported through the `bit64` package. Unfortunately, this also means that numeric literals (as in `SELECT 1`) are returned as 64-bit integers (#12). - Support timestamp values with sub-second precision on output. - The connection now uses the "utf8mb4" charset by default (#7). - The `port` and `client.flag` arguments to `dbConnect()` are coerced to integer (#4). - Date values with the year beyond 2038 are supported (#56). - Improve DBI compliance (#1, #5, #10, #15, #17, #40). - Correct handling of DATETIME and TIME columns (#52, @noahwilliamsson).
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue and link to this old issue if necessary. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue by krlmlr
Saturday Oct 10, 2015 at 19:20 GMT
Originally opened as r-dbi/RMySQL#93
Test name: "data_character", "roundtrip_character".
Possible cause: From the console, I get:
In R, I get:
Note the difference in
character_set_connection
.The text was updated successfully, but these errors were encountered: