FetchGroup(FetchPlan.GROUP_DEFAULT); // otherwise
> Person.name will be fetched as part
>
> //of the default group
>
>
> Of course, it is not necessary to define the fetch groups with same
> moniker. But t
*only* with city.
>
> A SQL similar to following should be generated:
> select t0.name, t0.city from Person t0
>
>
> StevenK wrote:
>>
>> We created an entity that contained some embedded fields and some
>> non-embedded fields (string, ints, etc). All fields are
nstraints, or other complications that
>> anyone is aware of?
> Nothing specific comes to mind. Are you seeing any anomaly w.r.t. embedded
> fields in a fetch plan?
>
>
> StevenK wrote:
>>
>> I am trying to optomize a query by using fetch groups. One of the fields
I am trying to optomize a query by using fetch groups. One of the fields I'd
like to include in the group is an embedded entity. When I turn sql tracing
on, run my query, and then display the value of the fields that were
returned, I can see that the non-embedded fields in my entry display witho
