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 would be good to find a way to optimise query creation in nrich-search module. Currently each query will always check all properties being searched against entity. It would be better to analyse just once all the possible mappings between class holding restrictions and JPA entity and then cache and reuse those mappings depending on the property values.
Current behaviour
Wanted behaviour
Possible workarounds
The text was updated successfully, but these errors were encountered:
Basic information
1.2.1
nrich-search
Additional information
Enhancement description
It would be good to find a way to optimise query creation in nrich-search module. Currently each query will always check all properties being searched against entity. It would be better to analyse just once all the possible mappings between class holding restrictions and JPA entity and then cache and reuse those mappings depending on the property values.
Current behaviour
Wanted behaviour
Possible workarounds
The text was updated successfully, but these errors were encountered: