Hibernate 3.0

I am using a single POJO, and single mapping file, with a SQLQuery to return results from many different raw SQL queries. The raw SQL queries use projection to map virtual result columns into entity properties. This technique is working pretty well except that not all queries should return all of the properties. Some queries only specify result columns for some of the properties defined on my entity, while some of the other queries might want to populate a different subset of the properties. Using more than one mapping file or more than one POJO would damage the integrity of the model, because conceptually, all queries are returning instances of this one entity. Concretely:

mapping file:


<class
name="example.Position"
>

<id
name="id"
type="example.UUIDUserType"
/>

<property
name="cusip"
type="string"
/>

<property
name="price"
type="double"
/>

<property
name="marketValue"
type="double"
/>



query1= "
SELECT 1 as {position.id}, cusip as {position.cusip}, price as {position.price}, marketValue as {position.marketValue}
.... oodles of SQL spam..."

SQLQuery query = session.createSQLQuery(query1);

query.addEntity("position", Position.class);
List loadObjects = query.list();

works fine.

But now query2 projects over a completely different set of tables and is not able to produce a column for "price".

query2= "
SELECT 1 as {position.id}, cusip as {position.cusip}, marketValue as {position.marketValue}
.... oodles of SQL spam..."

In this case, Hibernate still tries to load a value for the price column (because, I guess, it's mapped) and fails.

Is there some way to tell Hibernate that retrieving values for some properties is optional? It seems like the fundamental problem is that Hibernate insists there must be a ResultSet column for each mapped property, but what I really want Hibernate to do is to retrieve values for those column which are present and to ignore the others. Avoiding the complexities of dynamically mapping would be wonderful.

thanks for any pointers.

Joe

Different entity-names but, same class name might work for you -
Here is an example of what we used.

here you should you probably use polymorphism=explicit to avoid getting the same entity loaded in multiple representations.

p.s. i don't think this is a good usage of entity-name...