I am using the 'where' attribute in the <set> element quite successfully. However, for reasons of maintainability I would like to be able to externalise the content of the where clause so that I don't end up with a mapping file that, potentially, contains a large ugly 'where' attribute. I could then, at runtime, lookup the mapping and modify the 'where' clause programatically.
I looked at the Hibernate JavaDoc and it seems like I should be able to get to the mapping structure and, at the very least, display the where clause. When I attempt to do so however, using the following code, I just get a null value.
That problem aside, even if I could get at the where clause, it doesn't appear to be possible to modify it, i.e. there is no setter. Suggestions?

I realise that an alternative approach would be to use the query API to explicitly perform a query but I would very much like to fully leverage the lazy loading capabilities and stay away from unnecessary use of the query API when I don't strictly need to use it. As I said, the mapping file works perfectly as it is.

Thanks,

Scott.

Sample code:
PersistentClass pc = _config.getClassMapping(Order.class);
log.debug(pc.getName() + ", where = " + pc.getWhere());
PersistentClass pc = _config.getClassMapping(Item.class);
log.debug(pc.getName() + ", where = " + pc.getWhere());

Output:
ListMappings - Order, where = null
ListMappings - Item, where = null

Mapping:
<hibernate-mapping>
<class
name="Order"
table="ORDER"
proxy="Order">
<id name="id" column="ID">
<generator class="assigned"/>
</id>
<set name="licenseItems"
lazy="true"
where="PART_NUMBER IN ('555-6666', '111-2222')">
<key column="HEADER_ID"/>
<one-to-many class="Item"/>
</set>
</class>
</hibernate-mapping>

It is Collection.getWhere().

I don't really know if this is an error or just wrong usage, but you are digging around really deep inside the Configuration Object. Probably it would be easier if you just parse the Mapping File yourself, manipulate the where attribute in the DOM tree and then pass the tree to configure().

I'm also looking at a way to change the Where clause of a lazy collection at runtime.

Is it advisable to change the Where cluase using Collection.setWhere()? If so, will it permanently change the Where clause for the lazy collection till the SessionFactory is alive or only for that transaction?

Thanks

Hi Shansud,

I saw your posting java.lang.ClassCastException in blob persistence posted on Wed Sep 17, 2003 8:08 pm .

I am sorry for discussing about this topic here. I wanted to know if you got that problem fixed? If so, how did you solve it?

I also have the same problem. I have also used the same code (UserType).

I appreciate your response

Thanks