I appreciate your response. Good to know that MEMBER OF is respected. Now I am confused as to why the warning is being issued at all as I am not using collection properties to my knowledge.
Here is a good example from StackOverflow which illustrates the problem: http://stackoverflow.com/questions/33338186/how-to-remove-hibernate-deprecation-warning-message
I'll insert the stackoverflow query herein for simplicity:
Code:
List<Book> books = session.createQuery(
"from Book b where :x member of b.bookCategories")
.setParameter("x", crimeStory)
.list();
How is it that this query produces the collection properties warning? How can we avoid this warning but still use MEMBER OF syntax which I prefer to the INNER JOIN syntax?
Thanks in advance,
Steve
mihalcea_vlad wrote:
It's not the MEMBER OF which got deprecated, it's the collection properties that were dropped in favor of functions.
MEMBER OF is JPA 2.0 compliant, so it shouldn't be depreciated.
This is the issue:
https://hibernate.atlassian.net/browse/HHH-10070