Mark Paluch opened DATAJDBC-343 and commented
Rendered INSERT and UPDATE statements contain table prefixes in their assignments:
UPDATE legoset SET legoset.name = $1
This fails on Postgres and may work on other databases. We should not render the table prefix unless we get Dialect-awareness.
Postgres error:
UPDATE legoset SET legoset.name = $1, legoset.manual = $2 WHERE legoset.id = $3
Error: column "legoset" of relation "legoset" does not exist
Referenced from: commits 7a738ee