Hi!
I'm not sure if I understand you problem. But does it make sense to declare a
foreign key for primary key in the same table? Normally you declare the foreign
key in COUPON and make a reference to MEMBER. Maybe Torque doesn't like this
double key-definition in MEMBER. But I'm not sure
Ah, okay, a coupon has only one member. Is it possible to have a member that
has multiple coupons? Or is it a 1:1 relation? If so, you could make a circle
reference from member to coupon. If it is 1:n relation (I think so), then you
should add a third table COUPON_MEMBER_RELATION with
In BaseCcsCouponPeer should be a doSelectJoinCcsMember() method. The other way
around is not implemented. So you need to program it yourself, I think. The
member doesn't know about the coupons, so it isn't possible to build
automatically a doSelectJoinCcsCoupons. Additionally in MemberPeer you
