Hello again Pinaki et al,
We've run into a problem with FetchGroups which to me appears to be due
to an API Design limitation. Example, simplified Entity pseudo code:
abstract class Base { String code; }
@Inheritance(strategy = InheritanceType.TABLE_PER_CLASS)
class A extends Base { B b; }
@Inheritance(strategy = InheritanceType.TABLE_PER_CLASS)
class B extends Base { }
We would like to Fetch A's with their asssociate B's and the code in the
B, but not in the A... see where I'm going? ;-) -- So addField(A.class,
"b"); and addField(Base.class, "code"); (NOT addField(B.class,
"code")... see doc). The resulting SQL will JOIN A and B, but include
the 'code' from both A and B!
Is there any other (internal?) API to configure the FetchPlan more
precisely? Do you agree this is a limitation in the current API, and
would you be open to address this in a future version (createa a JIRA?)
?
Thanks a lot,
Michael
--
View this message in context:
http://n2.nabble.com/Fetch-Group-questions-tp534861p681237.html
____________________________________________________________
This email and any files transmitted with it are CONFIDENTIAL and intended
solely for the use of the individual or entity to which they are addressed.
Any unauthorized copying, disclosure, or distribution of the material within
this email is strictly forbidden.
Any views or opinions presented within this e-mail are solely those of the
author and do not necessarily represent those of Odyssey Financial
Technologies SA unless otherwise specifically stated.
An electronic message is not binding on its sender. Any message referring to
a binding engagement must be confirmed in writing and duly signed.
If you have received this email in error, please notify the sender immediately
and delete the original.
