-
Notifications
You must be signed in to change notification settings - Fork 356
Cannot save entity only have id and collections [DATAJDBC-557] #777
New issue
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? Sign in to your account
Comments
schauder
added a commit
that referenced
this issue
Nov 29, 2021
schauder
added a commit
that referenced
this issue
Nov 29, 2021
Moved SelectRenderContext and InsertRenderContext to dialect. Moved RenderContextFactory to render. See #777
This was referenced Nov 29, 2021
schauder
added a commit
that referenced
this issue
Dec 1, 2021
Simplified the code structure. Ensured backward compatibility by recreating some methods often immediately deprecating them. Moved new classes to the places where they belong, so that the package ...core.sql.render depends on ...core.dialect and not the other way round. This causes dependency cycles because dependencies in the other direction already exists. This will be properly fixed by #1105. For now the offending classes are ignored by the DependencyTests. See #777 See #1105 Polishing
schauder
added a commit
that referenced
this issue
Dec 1, 2021
Thanks for your work. I polished and merged it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
lseeker opened DATAJDBC-557 and commented
Exception on save entity have only ID property and collections like this.
Repository.save() generates bad SQL and throws exception.
On insert:
and on update:
Affects: 2.0 GA (Neumann), 2.1 M1 (2020.0.0)
Referenced from: pull request #224
The text was updated successfully, but these errors were encountered: