Skip to content
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

EntityManager clear behaviour #220

Open
jamescarter opened this issue Jan 3, 2014 · 0 comments
Open

EntityManager clear behaviour #220

jamescarter opened this issue Jan 3, 2014 · 0 comments
Assignees
Labels
Milestone

Comments

@jamescarter
Copy link

Batoo seems to rollback the transaction when calling EntityManager.clear(), while Hibernate and EclipseLink do not (the transaction will stay open until explicitly committed or rolledback).

I noticed this when attempting to optimise the import speed. When calling ((EntityManagerImpl)em).getSession().clear(); instead, the performance import between all 3 JPA implementations seems to be in the same ballpark. When not calling clear() to perform bulk imports, Batoo is much quicker

@asimarslan asimarslan added the bug label Oct 26, 2014
@asimarslan asimarslan added this to the 2.0.1.3 milestone Oct 26, 2014
@asimarslan asimarslan self-assigned this Oct 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants