MySQL onConflictUpdate with column renames

[joelsonoda]

This template isn't a strict requirement to open issues, but please try to provide as much information as possible.

Version: 3.9.0-4.6.0
Module: quill-sql
Database: mysql

Expected behavior

onConflictUpdate should produce valid conflict tokens (for example, column = values(column)) when a querySchema with renames is defined (schemaMeta/tableQuery).

Actual behavior

onConflictUpdate produces conflict tokens that result in the columns not being updated when there are renames specified in the table schema. (for example, column = column

Steps to reproduce the behavior

When the mysql dialect is used, define either a tableQuery or schemaMeta with at least one column rename, then reference the renamed column in an OnConflict.

https://scastie.scala-lang.org/3JwFDGEbSh6Zs5Z07f7YUg

Workaround

• Match database column naming for case class properties so that no renames are required in querySchema
• use version 3.8 or under (for example: https://scastie.scala-lang.org/OgC3Iqh1SDa7sAA8fBNWkg)