That’s fine, but there’s no way for me to specify utf8mb4 as either the

characterEncoding

or the

characterSetResults

. Exposed blows up with an

ExceptionInInitializedError

. If

characterSetResults=utf8mb4

is specified on the connect string, the underlying exception is

java.sql.SQLException: Can't map utf8mb4 given for characterSetResults to a supported MySQL encoding.

, and if I do

characterEncoding=utf8mb4

, it is

java.sql.SQLException: Unsupported character encoding 'utf8mb4'

.