I'm having trouble using Restrictions.isNotNull on one end of a one-to-one association. The association looks like this on one side:

<many-to-one name="station" column="STATION_ID" class="Station" cascade="all" unique="true" not-null="true"/>

...and this on the other:

<one-to-one name="office" class="Office" property-ref="station"/>

It is on the latter I'm trying to filter/search using QBC. The part relating to this association looks like this:

sortByThese = Restrictions.and( sortByThese, Restrictions.isNotNull( "office" ) );

However, it doesn't filter at all, and I get the full set of Station objects. There is nothing wrong with the surrounding code, as when I exchange "office" for a property of the Station class then it works like a charm.

Am I going about this the wrong way? ...can I not use isNotNull on an association? If not, does anyone have a suggestion for how to do it?

Ciao,

I don't understand exactly your domain model and the classes envolved, but I think that if there is like you said a one-to-one relation between the two of them, then you should map in both of the classes the referenced property like a one-to-one relation.

Bellow I inserted a example of how I map the one-to-one ralation in two tables that I used and works in NHibernate:

Let's say you have two tables: Person where you have some Personal Information and another table with Details. In the Person class you have a reference to a Detail object, that can also be NULL in some casses, and both Person and Detail tables have the same primary key. When I map, I put in both of the mapping files the relation as one-to-one like this:

In Person:



In Detail:



And on the Person class you have a property of type Detail (that can be NULL) and on the Detail you have a property of type Person.

I hope this will give you a clear ideea of the use of one-to-one relation.

And when you want to get only the Persons that have a Detail you can use this code:



If you want all Persons with or without Detail you simply have to change the JoinType to LeftOuterJoin.

Good luck my friend! Hope this helps!

Thanks for the reply.


I don't know. The association is done "by the book" (Hibernate in Action, Manning), and I know from others parts of my application that it works. It just seems that Restrictions.isNotNull doesn't go very well with associations.


But, if you do it like that, how do you identify which Person object goes with which Detail object? Surely you need a foreign key somewhere.

You match the Person primary key with the Detail primary key. The Detail primary-key if it is composed only from one field shouldn't be auto-incremented.

Or you can keep your mapping and try this:



And the Add method creates an AND between all the expresions you add.

See if this works.

I replaced it with an SQLRestriction and managed to get it to work.

There are two types of one-to-one associations as we have seen in this post:

1. The primay key is the link. Both sides can be mapped with <one-to-one> as suggested by tomaandtoma.
2. There is a foreign key in one of the tables. This side is mapped with <many-to-one unique="true" ...> and the other side is mapped with <one-to-one property-ref=...> as shown by the original post.

I am not very familiar with Criteria queries, but if I have done the exact same thing with HQL both with IS NULL and NOT IS NULL filters and it does work. The one thing to be aware of is that you have to do an explicit LEFT JOIN otherwise Hibernate uses an INNER JOIN which also acts like a kind of filter. But this usually means that you don't get any results at all so I don't understand why you are getting too many stations. Can you post the SQL that is generated?

When I filtered on only that association I got the following SQL sentence:



...which fits well with the fact that I'm getting everything, but how the Criterion in question becomes "this_.ID is not null" is a mystery to me.

Are you joining the offices to the criteria? If you need to filter on associations you need to call either Criteria.createAlias() or Criteria.createCriteria().

I just ran into this at Hibernate Core 3.6.6.Final. I added a Restrictions.isNull to a one-to-one association after adding an alias to the criteria, using CriteriaSpecification.LEFT_JOIN, expecting to get all of the entities with null association property. Instead, the id of the ROOT entity was filtered to null, returning zero results (id is never null).

As a simple workaround, I changed our code to use alias.id as the restriction property, instead of only the association property name as found on the root entity, and that works as expected. Our code was tested and working when written the other way at a previous release of Hibernate, so this must have been a regression.