On Thu, Nov 13, 2008 at 4:53 AM, Ken Cummins <[EMAIL PROTECTED]> wrote: > > I *think* I understand now, but there's one problem: a compositeid > can't contain a onetomany relationship. Only manytoone, > parentonetomany, or property.
But there is no way a o2m could be a compositeID. The FK could never be on the table that way - its always on the child. > > Also, as a point of clarification, should there be foreign keys set up > in the database itself, or is using the compositing of Transfer > sufficient? Of course you should use foreign keys... you don't like referential integrity? ;) Mark -- E: [EMAIL PROTECTED] W: www.compoundtheory.com --~--~---------~--~----~------------~-------~--~----~ 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 transfer-dev@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
