Hi All,

Hibernate version: 3.2.1


I am trying to fetch records using Hibernate Criteria API.

For example:
Criteria criteria = getSession().createCriteria(Definition.class)

Where Definition pojo object has multiple associations and the sql that is generated has more than 200 columns. From a performance point of view I need to exclude a single disclosure column of type blob from the select statement. Please note that this blob column mapping cannot be removed from the HBM file as it is required in few other cases.

Though there is a way to implement this using projection list, but its very tough to specify all 199 columns in projection list. So instead of adding columns to projection is there a way to exclude one or two columns.

Please let me know if there is any work around..

Note: In case the column exclusion is not supported in the current hibernate version it would help if its available in the future releases.


Thanks,
Hiisi

As far as I read the documentation a fetch type might be specified on basic properties: http://www.hibernate.org/hib_docs/annot ... g-property

@Basic(fetch = FetchType.LAZY)

In theory this should avoid fetching the property unless you call the getter.

Did not use this before, so please post your results.

HTH
Thomas

As far as I know, there is no way, to exclude a column using criteria.

But thhart's suggestion could help you. You could set this one excluded column as lazy, so that it is not read in a "normal" criteria.

In the few cases where you need this column you could explicitly load it using another HQL-Query ("select * from ...") or just let hibernate load it lazily if possible (that means, if you call the getter within an open session).

Hi,

Thank you so much for the replies. Both replies gave me some input to work on my problem. Looks like we need to use ant task to do run time instrumentation for the single property lazy fetching to work. I am on the process of trying.... :-)

Regards,
Hiisi