Skip to content

DATAJDBC-143 - Removed domain type parameter form JdbcEntityOperations.save(). #69

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

Closed
wants to merge 2 commits into from

Conversation

schauder
Copy link
Contributor

Such a parameter would only make sense with inheritance and we don't support inheritance at all at the moment.
Anything we need in order to support inheritance should be added once we do support inheritance.

schauder added 2 commits May 22, 2018 14:09
…s.save().

Such a parameter would only make sense with inheritance and we don't support inheritance at all in the moment.
Anything we need in order to support inheritance should be added once we do support inheritance.
@schauder schauder force-pushed the issue/DATAJDBC-143 branch from a20e97e to c5edda3 Compare May 22, 2018 12:10
@gregturn gregturn closed this May 23, 2018
@gregturn gregturn deleted the issue/DATAJDBC-143 branch May 23, 2018 20:06
@gregturn
Copy link
Contributor

Resolved via 01478cc

mp911de added a commit that referenced this pull request Feb 21, 2022
We now allow object creation when not all columns are present by leveraging R2DBC RowMetadata. A column subset is necessary for projections.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants