[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2150?page=all ]
Max Rydahl Andersen closed HHH-2150:
------------------------------------
Resolution: Rejected
sorry but this is not a bug and you have more then enough options with projection,
fetchMode, resulttransformer, lazy properties etc. to get just exactly what you
want/need.
There are too many columns in the select statement with the Criteria
API
------------------------------------------------------------------------
Key: HHH-2150
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2150
Project: Hibernate3
Type: Improvement
Components: query-criteria
Versions: 3.2.0.ga
Environment: Hibernate 3.2.0.cr2
PostgreSQL 8.1.3
Reporter: Slawek Trybus
Using Criteria API brings on enclosing all columns from joined tables in generated select
statement. It has big efficiency impact on DB especially if there are many joined tables
(with many columns each) in a query.
There is columns' limitation possible with the Projections API usage, but it makes
received objects not fully fledged Hibernate entity objects.
It would be good to have posibility to limit amount of columns in select statement to
ones connected to entity we are interested in.
There is available short discusion about this issue in the forum:
http://forum.hibernate.org/viewtopic.php?t=965818
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira