I have written a custom TQL that handles my problem and all is great, so this is not a question I *need* the answer to, but I'm still quite curious WHY this is happening. Any thoughts on why calling getPostsArray() first breaks the functionality to add a tag?
On Sep 26, 7:53 am, whostheJBoss <[email protected]> wrote: > Ok, another update... if I set proxied="false" on: > > <onetomany name="posts" lazy="true" proxied="true"> > <link to="posts.post" column="userID"/> > <collection type="array"> > </collection> > </onetomany> > > Then it works! I can call getPostsArray() first and still add tags. > So, having the onetomany posts object on users.user proxied causes the > odd behavior. I don't think this should be happening. > > Yes, it works, but this means my call to getPostsArray() gives me an > array of all of my actual posts.post objects instead of the proxied > object, which I need. The posts.post objects are far too heavy when > retrieving 100 (or in the case of my application, 500) objects. I need > the proxy. > > Shouldn't I be able to call getPostsArray() and get proxied objects > without this preventing me from adding tags.tag objects to the > manytomany relationship? > > Seems like I should... > > I'd like to know what is is in the mechanics of making the parent's > (users.user) relationship with the parent (posts.post) of the > manytomany (tags.tag) proxied that breaks the adding of the manytomany > on the child object (posts.post) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
