Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
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.
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
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.