This one time, at band camp, Patric Bechtel said:
PB>On Tue, 22 Oct 2002 22:22:15 -1000, Yasuhiko Yoshikawa(Sakakibara) wrote:
PB>
PB>>Hello list,
PB>>
PB>>I have other objects persisted with no problem. Only difference between
PB>>the class of the objects persisted right and the one with problem
PB>>(Customer) is that the problem class has 2 references to a class
PB>>(Address).
PB>>(One is for billing address and the other is for shipping address.)
PB>>
PB>>I start to think that this might be the cause of the problem...
PB>>
PB>>Is it supported in the Castor to have a Class to have 2 or more
PB>>references to another class? Or do I need special treatment for these
PB>>cases.
PB>>
PB>>
PB>
PB>Yes and no. To be honest, don't try it. In an earlier mail I asked about
PB>a similiar case, in which the removal of one of these relationships
PB>removed ALL occurences in ALL relations of that object. So, removing
PB>the billing address would remove, if the shipping address is the same,
PB>that one, too. That's a very weird bug; but in my research I found out
PB>WHERE the problem arises, but I don't think it's really fixable.
PB>My proposal would be to solve the above problem (shipping/billing etc)
PB>with a role-object, which does an interconnect between the customer,
PB>and address and a role (a class of it's own).
PB>So you can add as many roles to adresses to customers as you want to... :-)
Sergej, Yasuhiko,
Yasuhiko is correct, I believe, in his assumption. This problem is
most likely due to the use of two Address objects. Also, Patric is
correct. Castor cannot handle this situation straight away. The only way
to get this to work is through an elaborate workaround like what Patric
suggests above.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
