Hibernate version: 3.0


Hello guys,

I'm getting the following error:



I do know it happens because it tried to fetch an ID that doesn't exist. But the thing it that I needed it to ignore it instead of giving me an error.

My HQL is:



In the "order by o.lote" is that it's finding this error. The thing is that I'm working on an already existing database and I know that i WILL find this error. I wanted to find a way to ignore it, 'cause I can't fix it.

Is there a way? Or this will stop me from using hibernate?

Why don't you send the result set to a list and check if the list is empty?

List lst = sesion.query("....").list();
if (lst.isEmpty()) ...

The thing is that the list is NOT empty. It does return me results, after all I'm selecting another object.

The object I'm selecting has a many-to-one relation with the object that is not present in the DB. That is, in my OrdemItens object (that is being selected) there's a property Lote (which is the one that's missing in some rows). In my OrdemItens table there's a field for the Lote pk.

All I wanna do is select OrdemItens and ignore if the relation is invalid.

Thanks.

I would remove te "order by" in the query and use a filter instead.
Look in the documentation about how to create a filter on a persistent object .

When you say using a filter, you mean criteria?
Will it fix my problem?

Isn't there some magic mapping option like "ignore-not-found=true" or something?

a filter can be applied to a persistent
collection (or array). It’s commonly used to further restrict or order a result.

use it on an already loaded Item and its collection. For example:
List results = session.createFilter( item.getBids(),
"order by this.amount asc" )
.list();

This is a concept different from criteria query you refer to.

Remove the order by from the query. After get the list, you can sort the list using Collections.sort().

there is a not-found="ignore" option that might be of use. personally i've never used it.

http://www.hibernate.org/hib_docs/v3/reference/en/html/mapping.html#mapping-declaration-manytoone

Thank you everyone.

I'll remove the order by and sort the collection later, and I'll also use the not-found="ignore" to guarantee

:)

Now I have the following HQL:



and my mapping for this association is:


Without the not-found="ignore", it gives me the same "No row with the given identifier exists" error. With it, it gives me no error and returns a list - but this list ignores the rows where there's no association (which is, where the field is null). All I want now is to get thiis rows too. Anyone has any idea?

This behavier is strange for me, because the documentations says that the behavier for not-found="ignore" is:

not-found (optional - defaults to exception): Specifies how foreign keys that reference missing rows will be handled: ignore will treat a missing row as a null association.

Try this for a test and check if the objects are returning.
session.createQuery("from OrdemItens");