Alternatively, instead of using JPA annotations (I'm not sure if that is
actually idiomatic JPA usage), you could alias your projected columns to
TABLE_A.NAME.as("name_a") or TABLE_A.NAME.as("nameA") to get the wanted
I have read the contents of issues/5961, but it seems has a lower priority
But I think it would be better to implements this, since it may be a common
to resolve duplicate name problems in Jooq.
I cannot use column alias to implement this, since I need a dynamic query
not a static one.
I will try to write a custom RecordMapper to implement this.
On Monday, August 26, 2019 at 6:14:52 PM UTC+9, Lukas Eder wrote:
The "Invalid SQL: " message happens because MockFileDatabase does not find
any matching SQL statement in your file that would match the one you ran.
The SQL string that you (via jOOQ) sent to the MockFileDatabase is printed
there, now you will have to check your file for the statement you intended
to match here.
In your file, you used inline values / constant
... but what's being sent to the server is a bind variable
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to [hidden email].