Skip to content
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.

Sign up for GitHub

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

Jump to bottom

support emoji (utf8mb4) #7

Closed
krlmlr opened this issue Jul 5, 2017 · 4 comments
Closed

support emoji (utf8mb4) #7

krlmlr opened this issue Jul 5, 2017 · 4 comments
Milestone
1.0

Comments

@krlmlr
Copy link
Member

krlmlr commented Jul 5, 2017

Issue by graingert
Wednesday Mar 25, 2015 at 10:47 GMT
Originally opened as r-dbi/RMySQL#60

From the sqlalchemy docs:

The encoding used for Unicode has traditionally been 'utf8'. However, for MySQL versions 5.5.3 on forward, a new MySQL-specific encoding 'utf8mb4' has been introduced. The rationale for this new encoding is due to the fact that MySQL’s utf-8 encoding only supports codepoints up to three bytes instead of four. Therefore, when communicating with a MySQL database that includes codepoints more than three bytes in size, this new charset is preferred, if supported by both the database as well as the client DBAPI
@krlmlr krlmlr added this to the 1.0 milestone Jul 5, 2017
@krlmlr
Copy link
Member Author

krlmlr commented Jul 5, 2017

Comment by hadley
Wednesday Mar 25, 2015 at 13:02 GMT

So utf8mb4 is "real" utf-8?

@krlmlr
Copy link
Member Author

krlmlr commented Jul 5, 2017

Comment by graingert
Wednesday Mar 25, 2015 at 14:03 GMT

Yeah, utf8mb4 is UTF-8 as described by https://tools.ietf.org/html/rfc3629

The original description of UTF-8 allowed for up to 6-byte characters

@krlmlr krlmlr closed this as completed in a16ce45 Sep 13, 2017
@krlmlr
Copy link
Member Author

krlmlr commented Sep 13, 2017

@graingert: Thanks!

krlmlr added a commit that referenced this issue Sep 24, 2017
@krlmlr
Merge tag 'v0.11-7'
56707ab 
- 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).
krlmlr added a commit that referenced this issue Oct 4, 2017
@krlmlr
Merge tag 'v1.0-2'
5238273 
Initial release, compliant to the DBI specification.

- Test almost all test cases of the DBI specification.
- Fully support parametrized queries (#22, #27, #39).
- Queries not supported by the prepared statement protocol still can be run via `dbExecute()` or `dbSendStatement()`, the function `mariadbExecQuery()` has been removed (#28).
- Spec-compliant transactions (#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).
- Correct handling of DATETIME and TIME columns (#52, @noahwilliamsson). Support timestamp values with sub-second precision on output, and with year beyond 2038 (#56).
- The connection now uses the "utf8mb4" charset by default (#7).
- New default `row.names = FALSE`.
- New SSL-related arguments to `dbConnect()`: `ssl.key`, `ssl.cert`, `ssl.ca`, `ssl.capath`, `ssl.cipher` (#131, #148, @adamchainz).
- CI for Linux, Windows, and OS X (#25).
- Support for Connector/C from both MariaDB and MySQL.
@github-actions
Copy link
Contributor

github-actions bot commented Dec 8, 2020

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.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@krlmlr