We have some columns names "floor" and "hash". This used to work fine until 3.5.0 Beta 2. This and later releases fail when a query involves a join with two tables and both each contain a column named either "floor" or "hash" with an "ambiguous column" error.
3.5.0 Beta 1 and previous releases work fine. Something must have changed in Beta 2 that is causing some kind of recognition of SQL function names, but I can't seem to pinpoint any issue related to this in the changelong.
I'm pretty sure this would also happen with other column names such as "ceil", "abs", etc. which although they might be SQL function names they are not reserved keywords, and thus they are valid column names.
Error verified with Oracle, MySQL and H2 database engines.
I'm sure this is duplicate of
Column "count" on PostgreSQL with 3.5.0-Final caused the same issue. Changing the column name to "\"count\"" worked around the issue:
Please attach a runnable test case (Java + mapping) that reproduces this issue.
Bulk closing stale resolved issues