On 2 Жов, 16:39, Sergiy Galashyn <[email protected]> wrote:
> Is it something forbidden for such structure and I should use the o2m
> relationships instead for app.Page and app.User?
>
> Problem is that I can not link the app.User o2m collection to the
> Security object when using composite id.
>
> Like this:
>
> <onetomany name="security" lazy="true" proxied="true">
> <link to="app.Security" column="id_user"/>
> <collection type="array">
> <order property="securityToken" order="asc" />
> </collection>
> </onetomany>
>
Interesting thing here is that such o2m relationship started working
perfectly after I have removed proxied="true". Why?
For now I decided to leave it o2m.
But still, it'd be nice to find out about listing the objects with
m2o.
-Sergiy
--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer
You received this message because you are subscribed to the Google Groups
"transfer-dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
