Hibernate mappings define a feature to allow a secondary table (`<join/>` in hbm terms) to be defined as not joined via : `<join ... fetch="select"/>`. This actually creates a subsequent select to load the data from the secondary table.
I am trying to figure out how to best incorporate this into the paradigm for JDBC statement execution in 6.0. My first thought was "do we need to keep this?". Does anyone know of a real usage of this feature? In theory it could be useful to some degree along with bytecode enhanced interception for lazy-loading individual attributes. But even then, I'm not sure how practically useful that is. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev