[
https://issues.apache.org/jira/browse/TORQUE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13747836#comment-13747836
]
Thomas Fox commented on TORQUE-293:
-----------------------------------
In fact, Torque 3.3 generated a getAtoBJoinB(Criteria) and a
getAtoBJoinA(Criteria) in A.
In my opinion, it makes sense to do the following:
- generate a getAtoBJoinB(Criteria) in A
- fill all AtoB object retrieved by getAtoB ... methods with references to the
current A (thus removing the ned for the getAtoBJoinA method)
> The generated OM classes of object A contain a method getAtoBJoinA() where
> they should contain a method getAtoBJoinB()
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: TORQUE-293
> URL: https://issues.apache.org/jira/browse/TORQUE-293
> Project: Torque
> Issue Type: Bug
> Components: Templates
> Affects Versions: 4.0
> Reporter: Thomas Vandahl
> Assignee: Thomas Fox
>
> I use the getAJoinB() methods in the OM classes. I have the following table
> relation:
> A - AtoB - B
> Now in A there used to be a generated method getAtoBJoinB(Criteria) whereas
> in Torque4 there is only getAtoBJoinA(Criteria). This feature was very
> helpful when dealing with m:n relations. It allowed to access all Bs that
> belong to a certain A with one call. So to get all As that belong to a
> certain A is not very useful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
