Well, looks like adding

&useUnicode=true&characterEncoding=utf8&characterSetResults=utf8

to the connection string helps quite a bit. Thanks for pointing me in the right direction

You need to use utf8mb4 for full unicode support. If you can roundtrip

🤷‍♀️

then it works

Yeah, I initially tried utf8mb4 for both characterEncoding and characterSetResults, and got errors that they were not supported values in the connection string.

I can roundtrip and it works, at least for Polish.

I should probably try something more interesting, like Chinese or Arabic

Hmm ok. Its a bit hazy for me. We are using mariadb now which has its own quirks

And what do you know, using Chinese also seems to work.

So, looks like that was the right thing to do.

Both are quite old in unicode terms I think. Shrugging woman

🤷‍♀️

was the most complex one I have found

Yeah, ok, it craps out on Shrugging woman.

But if some hipsters enters that as their company name, screw ’em.

mysql uses a very broken 3 byte unicode encoding in utf8, thats why you should only use utf8mb4

In MySQL 5.7, for

characterEncoding

and

characterSetResults

, the valid parameters are either

utf8

or

UTF-8

, and what I’ve read leads me to think these have the exact same behavior.

Never assume with mysql 😄

I see that in the master branch you guys have added support for

onUpdate

cascade 🙂

That’s pretty great. Super keen to get my hands on that 🙂

Exposed 0.10.4 was released (https://bintray.com/kotlin/exposed/exposed/0.10.4) Features: * ON UPDATE reference constraint added * All dialects made public and open for extensibility * Transaction.addLogger() function introduced as replacement to logger.addLogger() approach * Strings will be validated against column max length before inserting to database (#300) * Overriding the fetch size for a Query (#327) Bug fixes: * Extended sql exception logging available only in debug mode * [PostgreSQL] Table with customEnumeration column doesn’t work with Entity/DAO API (#340) * Table with composite key created only with specific prop order (#343) allTableNames in VendorDialect returns only from current database (#339) * “ORA-00972: identifier is too long” on creating table with long name

How do you enable Exposed logs?

I have an slf4j logger which works, because I'm seeing Ktor logs, but I see no Exposed logs

I tried this but I still have no logs

transaction {
    addLogger(Slf4jSqlDebugLogger)
    callable()
}

You should enable a debug mode on Transaction or create your own SqlLogger implementation and register it

Would this work ?

transaction {
    debug = true
    addLogger(Slf4jSqlDebugLogger)
    callable()
}

You probably need an info logger instead

I just want to have anything get logged at first

For now there's absolutely nothing, I suspect there are error thrown that are hidden to me

debug should be enabled on the logging framework

It is, it's even in verbose mode

For what logger? Root?

Try to log to stdout: https://github.com/JetBrains/Exposed/wiki/Getting-Started#your-first-exposed-dao

Oh, I found my problem.

override fun isDebugEnabled() = Log.debug

should be

override fun isDebugEnabled() = Log.verbose || Log.debug