Hello! In one case I have experienced the same behaviour.. even I had auto-retrieve true. I have M..N association.. and when I read the object from db (asociations were retrieved succesfully as CollProxies), then edit some of its *simple* attributes (did not touch the CollProxies) and store the object back, my associations were lost, when I used collection proxies (if I have iterated over Collection proxy = data was loaded, then stored, associations were NOT lost..). I switched coll. proxies off and this behaviour disapeared. But it's not the final solution. Also retrieveAllReferences didn't help me in this case.. it didn't work at all. I would like to know more about it. $kala.
----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 10, 2002 8:20 AM Subject: maybe i found a bug > hi! > for performance reasons, and because proxies don't work for me (in client > / server) i implemented my own lazy-loading (in my code, not ojb). to > enable the whole thing, i set auto-retrieve to false on lots of collection > and reference descriptors. the whole thing works quite fine, but when i > store the object, the not-retrieved references will be set to null. for m > this seems to be a bug, because it's not required to really have those > references loaded. > > please tell, if this is a bug or not, because if it is, i'll fix that. if > this is not a bug, please tell me a solution. > > juergen > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
