Skip to content

Conversation

@karge-itestra
Copy link
Contributor

@karge-itestra karge-itestra commented Jan 26, 2021

@karge-itestra
Copy link
Contributor Author

I have added an additional test case showing that an entity entry that is created by em.persist() is created with isExistsInDatabase() == false instead of evaluating whether the entity is already in the database. This happens although the entity manager determines correctly that there was a delete statement that has not been flushed yet (so the entity must exist in the database)

Base automatically changed from master to main March 19, 2021 16:00
@hibernate-github-bot
Copy link

hibernate-github-bot bot commented Mar 19, 2021

Thanks for your pull request!

This pull request does not follow the contribution rules. Could you have a look?

❌ All commit messages should start with a JIRA issue key matching pattern HHH-\d+
    ↳ Offending commits: [39b18b2, befffca, 3b0affb, cd767c3, 4126397, 4425ea0, 669d60f, 03cf943, e7dc900]

› This message was automatically generated.

entity entry after detach and re-save wrongly created
with flag "existsInDatabase" false
@gavinking gavinking changed the base branch from 5.6 to main November 23, 2024 08:28
@gavinking
Copy link
Member

The tests proposed here contained several user misunderstandings, but I did find something interesting, so moving to #9316.

@gavinking gavinking closed this Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants