Ignore Hibernate @Where annotation

Question

I have an Entity which has an association to another Entity annotated with @Where, like so

public class EntityA {

    @OneToMany
    @Where(...)
    private List<EntityB> entityBList;

}

Recently the inevitable has happened, I need to load EntityB's that don't conform to the @Where clause. I could remove the @Where annotation, but it is used a lot, so ideally I don't want to do that. Apart from loading the list of EntityB's manually, with another query, what are my options? Can I tell Hibernate to ignore the @Where annotation?

I need it for 99% of the queries, but there is one for which I do not need it. — Zecrates, Feb 23 '10 at 07:51

score 26 · Answer 1 · answered Jul 09 '18 at 17:04

26

I just had the same question. I solved the problem like this:

@Query(value="SELECT * FROM EntityA", nativeQuery=true)
public ignoreWhereMethod(){}

The SQL in the @Query annotation must point the table's name and the fields' names (not entity's name).

answered Jul 09 '18 at 17:04

Yuri Hassle Araújo

260
3
4

This should be the accepted answer, it doesn't force to delete the annotation on entity and works perfectly fine. – chomp Nov 12 '18 at 15:11
This worked for me as well, This should be the accepted answer. – Lahiru Mar 08 '22 at 08:02

score 14 · Accepted Answer · answered Jul 29 '10 at 10:27

14

After lots of research it appears that this is simply impossible. I'd strongly suggest avoiding @Where, as it is hard to predict beforehand if you'll ever need those associations or not.

answered Jul 29 '10 at 10:27

Zecrates

2,952
6
33
50

2

please delete this comment, as it is false. – royashcenazi Jul 14 '19 at 15:19
See this: https://stackoverflow.com/questions/24659984/hibernate-how-to-ignore-where-annotation#24660159 – Björn Jan 10 '20 at 10:22

score 9 · Answer 3 · answered Nov 01 '11 at 02:59

9

I know its an old question but in case anyone look for an answer...
I had the same dilemma, you don't want to mess your code with "is_deleted= false" every where you select,

simple solution is to use native SQL:

lst = sessionFactory.getCurrentSession().
createSQLQuery("select {entb.*}  from EntityB entb where  is_deleted=1")                            
           .addEntity("entb", EntityB.class)
           .list();

answered Nov 01 '11 at 02:59

JavaSheriff

7,074
20
89
159

Do you know if it is the same solution when someone uses @Query annotation and JPQL? – J. Abel Oct 15 '19 at 03:11
It is the same, see solution from @yuri-hassle-araújo – t0r0X Apr 14 '20 at 14:21

Gabriel · Answer 4 · 2010-03-26T12:14:40.810

6

You can map another property with same data like this:

public class EntityA {

    @OneToMany
    @JoinColumn(name='theColumnName', insertable=false, updateable=false)
    private List<EntityB> entityBListReadOnly;

}

Important to set as updateable false and insertable falso to avoid consistency problems in your data!

edited Mar 26 '10 at 12:14

answered Mar 26 '10 at 11:31

Gabriel

101
1
5

score 1 · Answer 5 · answered Jan 10 '20 at 10:21

1

Another solution is filter, as explained in this question. Hibernate how to ignore @Where annotation

I will be trying this myself because the combination of @where and @NamedNativeQueries is a very cumbersome solution in our situation. But I do not know yet if @Filter is any better.

answered Jan 10 '20 at 10:21

Björn

471
10
15

this question is from 2010 please seek modern solutions – JavaSheriff Apr 14 '20 at 14:23
1

I would love to find modern solutions but alas I am not capable. Finally I had to step down to the `@where` and `@NamedNativeQueries` solutions mentioned by myself. But you are perfectly right that this is not ideal. I am open to proposals :-) – Björn Nov 20 '20 at 20:36

Ignore Hibernate @Where annotation

5 Answers5

Linked