It's fixed now. Of course it was a big deal! ;-) Aslak
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Brian > Cochran > Sent: 14. august 2002 02:16 > To: Middlegen User (E-mail) > Subject: [Middlegen-user] Relationship to Self > > > If I have an entity that has a relationship to itself, middlegen winds up > with a name colision in the role-name's. For example: > > CREATE TABLE NODE ( NODE_ID INT, PARENT_ID INT); > ALTER TABLE NODE ADD PRIMARY KEY(NODE_ID) > ALTER TABLE NODE ADD FOREIGN KEY(PARENT_ID) REFERENCES NODE; > > would fail because we would get role-name's that were identical on both > sides of the relationship. > > I don't know how often this finds its way into peoples stuff so > maybe not a > big deal :), but I figured I'd mention it anyway. > > Thanks a bunch, > Brian > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Dice - The leading online job board > for high-tech professionals. Search and apply for tech jobs today! > http://seeker.dice.com/seeker.epl?rel_code=31 > _______________________________________________ > middlegen-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/middlegen-user ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 _______________________________________________ middlegen-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/middlegen-user
