Skip to content

DATAJPA-1261 - Revert DATAJPA-931. #249

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
Closed

Conversation

schauder
Copy link
Contributor

@schauder schauder commented Feb 5, 2018

This reverts the functional change made by DATAJPA-931.
This means merge will be called again, even if the entity for which save was called is already attached to the session.
Tests stay in place to verify the new old behavior.

This reverts the functional change made by DATAJPA-931.
This means merge will be called again, even if the entity for which save was called is already attached to the session.
Tests stay in place to verify the new old behavior.
odrotbohm pushed a commit that referenced this pull request Feb 5, 2018
…lementation of CrudRepository.save(…).

This reverts the functional change made by DATAJPA-931. This means merge will be called again, even if the entity for which save was called is already attached to the session. Tests stay in place to verify the new old behavior.

Related ticket: DATAJPA-931.
Original pull request: #249.
odrotbohm pushed a commit that referenced this pull request Feb 5, 2018
…lementation of CrudRepository.save(…).

This reverts the functional change made by DATAJPA-931. This means merge will be called again, even if the entity for which save was called is already attached to the session. Tests stay in place to verify the new old behavior.

Related ticket: DATAJPA-931.
Original pull request: #249.
@odrotbohm odrotbohm closed this Feb 5, 2018
@odrotbohm odrotbohm deleted the issue/DATAJPA-1261 branch February 5, 2018 12:02
@stsypanov
Copy link
Contributor

Could anyone explain in brief why this change was reverted in 2.0.X? Any ticket?

@madness-inc
Copy link

madness-inc commented Feb 7, 2018

The original ticket can be found here:
https://jira.spring.io/browse/DATAJPA-931
This is the related commit:
8265daf

But I agree that it was not stated why it was reverted.

@stsypanov
Copy link
Contributor

Thanks, I'll ask this question there.

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.

4 participants