-
Notifications
You must be signed in to change notification settings - Fork 3
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
implement vendor specific update systems #91
Labels
Comments
OpenJPA has such a system as well. |
s4ke
added a commit
that referenced
this issue
Jul 27, 2015
s4ke
added a commit
that referenced
this issue
Jul 28, 2015
s4ke
added a commit
that referenced
this issue
Jul 28, 2015
we need to implement UpdateConsumer logic for these as well. |
tests for flush only (no transaction active) have to be implemented as well. |
we need to test this in a JTA environment as well. |
s4ke
added a commit
that referenced
this issue
Jul 28, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For EclipseLink we can use SessionEventAdapters (for Transaction callbacks) and DescriptorEvents (for change events).
For Hibernate we can just use the same system Hibernate Search ORM has.
The text was updated successfully, but these errors were encountered: