You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that just having EV implementations generated by the annotation processor breaks some flows, e.g. when an existing entity view is updated with a view that has @EntityViewInheritance set up.
Currently, the newly added test fails on "The update operation did not return the expected update count". By disabling the static implementation scanning (setting com.blazebit.persistence.view.static_implementation_scanning_disabled to true, uncomment the line in createEntityViewManager) the issue disappears. Also, the issue doesn't happen when the annotation processor is not used at all.
Environment
BP version: 1.6.8
The text was updated successfully, but these errors were encountered:
Description
It seems that just having EV implementations generated by the annotation processor breaks some flows, e.g. when an existing entity view is updated with a view that has
@EntityViewInheritance
set up.Steps to reproduce
See created test case: #1682
Currently, the newly added test fails on "The update operation did not return the expected update count". By disabling the static implementation scanning (setting
com.blazebit.persistence.view.static_implementation_scanning_disabled
to true, uncomment the line increateEntityViewManager
) the issue disappears. Also, the issue doesn't happen when the annotation processor is not used at all.Environment
BP version: 1.6.8
The text was updated successfully, but these errors were encountered: