That would be cool, but FetchProfile needs to be defined statically where EntityGraph could be built upon a list of attributes coming from an external request (e.g. HTTP/RESTful API).

To sum this issue up, I think that collection attributes in EntityGraph should be SELECT queried and not JOIN, to:

• prevent exceptions when multiple collections are involved in the same graph;
• avoid in-memeory pagination, which kills every query with entity graphs over large tables.

This would come as simple as:

1. in AbstractEntityGraphVisitationStrategy
   Unable to find source-code formatter for language: diff. Available languages are: actionscript, html, java, javascript, none, sql, xhtml, xml

   --- a/hibernate-core/src/main/java/org/hibernate/loader/plan/build/internal/AbstractEntityGraphVisitationStrategy.java
   +++ b/hibernate-core/src/main/java/org/hibernate/loader/plan/build/internal/AbstractEntityGraphVisitationStrategy.java
   @@ -65,7 +65,7 @@ public abstract class AbstractEntityGraphVisitationStrategy
            * NOTE: this may be changed in the near further, though ATM I have no idea how this will be changed to :)
            * -- stliu
            */
   -       protected static final FetchStrategy DEFAULT_EAGER = new FetchStrategy( FetchTiming.IMMEDIATE, FetchStyle.JOIN );
   +       protected static final FetchStrategy DEFAULT_EAGER = new FetchStrategy( FetchTiming.IMMEDIATE, FetchStyle.SELECT );
   

2. in EntityGraphQueryHint I really don't know how, since I think it's late to make strategy decisions in there and it should be handled before (here I summon @Brett Meyer to have his opinion).