Hi All,

I've scoured the forums & FAQs and I believe I know the answer to this, but I haven't seen it stated explicitly.

I'm trying to use Query by Example on entities that have primitive type properties. Since these can't be null, it seems the Hibernate engine adds those to the SQL as part of the where clause, even though I don't want them to be involved in the query.

This issue seems to be related somewhat to the use of primitive types to map nullable numeric database fields -- the null doesn't translate.

So it seems in this case that the only real solution (assuming QBE is the requirement) is to use Object types instead of primitives.

Is this a fair assessment? Is there any other workaround that would let me keep the primitive types? Is there any way to specify a default value of non-id properties?

Thanks a 10^6,

Chris

take out those primitives!

:-)

You can use the Example.excludeXXX() or a custom Example.PropertySelector to customize what properties are included/excluded