Thomas Vandahl wrote:
The getItemsJoinPurchaseOrder()-method also creates a new copy of
PurchaseOrder for every line of Item. This is something I wanted to
address in 4.0 anyway.
Just one additional comment:
Torque doesn't care much how many object copies of the same database
record exist in
Thomas Fischer wrote:
The only way to achieve this in general would be modifying the object.vm
template which generatates the get${relCol} method.
I would believe that the behaviour you describe would make sense
generally. Any opinions on that from other people ? By doing this one
would
The only way to achieve this in general would be modifying the object.vm
template which generatates the get${relCol} method.
I would believe that the behaviour you describe would make sense
generally. Any opinions on that from other people ? By doing this one
would increase coupling between
Hi Thomas,
as an user / programmer I would expect parent.getChildren().getParent() to
return the original parent object. Thus I would agree that it feels natural to
set the parent of the children upon retrieval of those children.
Regards,
Hidde.
- Thomas Fischer fisc...@seitenbau.net
