You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The disadvantage here is that quill will still compile and generate invalid sql if we forget to do a asStringCol and do a toString. We may not discover the issue until runtime.
Version: (e.g.
4.6.0
)Module: (e.g.
quill-sql
)Database: (e.g.
mysql
)Expected behavior
When
toString
is called on a selected value using the MySQL dialect, it should produce mysql compatible sql, for examplecast(x as CHAR)
Actual behavior
When
toString
is called on a selected value using the MySQL dialect, it produces invalid sql, for examplecast(x as VARCHAR)
.Steps to reproduce the behavior
https://scastie.scala-lang.org/vonCXkfhS2GhqWCU0k5cZw
Workaround
Here are a few of the workarounds:
The disadvantage here is that quill will still compile and generate invalid sql if we forget to do a
asStringCol
and do atoString
. We may not discover the issue until runtime.@getquill/maintainers
The text was updated successfully, but these errors were encountered: