Skip to content

Having a 4-byte UTF-8 character submitted while creating a new record throws mysql error and breaks transaction #312

Description

@ajpires

Was under the impression the backend could already take 4-byte UTF-8, but apparently https://www.compart.com/en/unicode/U+1D6FE broke it. Also caused ODR to create a partially filled record, which shouldn't happen either...

Metadata

Metadata

Assignees

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions