Path: news.easynews.com!easynews!crtntx1-snh1.gtei.net!lsanca1-snf1!news.gtei.net!newsfeed2.earthlink.net!newsfeed.earthlink.net!newsmaster1.prod.itd.earthlink.net!newsread1.prod.itd.earthlink.net.POSTED!not-for-mail
From: "Tim Mueller" <timmueller@earthlink.net>
Newsgroups: comp.databases.theory
Subject: Erwin reverse engineering question
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID: <_SwH7.32518$S4.2916053@newsread1.prod.itd.earthlink.net>
Date: Sun, 11 Nov 2001 15:33:14 GMT
NNTP-Posting-Host: 63.28.34.143
X-Complaints-To: abuse@earthlink.net
X-Trace: newsread1.prod.itd.earthlink.net 1005492794 63.28.34.143 (Sun, 11 Nov 2001 07:33:14 PST)
NNTP-Posting-Date: Sun, 11 Nov 2001 07:33:14 PST
Organization: EarthLink Inc. -- http://www.EarthLink.net
Xref: easynews comp.databases.theory:18937
X-Received-Date: Sun, 11 Nov 2001 09:17:49 MST (news.easynews.com)

As part of a system migration project, I need to reverse engineer a fairly
simple schema in an existing Oracle database.  There are about half a dozen
primary tables, say 10 lookup value tables (the sort of thing that would be
used for value assitance in a drop down) and a couple of M:M tables.

The problem I'm having is that the original designer/programmer wasn't
consistent in his column names for the foreign keys.  For example, there is
a lookup table called LOCATION that has three columns, CODE, NAME,
SHORT_NAME.  In the tables that have a relationship with the LOCATION table,
the foreign key column is named LOC_CODE, because there are several other
xxx_CODE columns there as well.

This makes ERwin gag when trying to create the foreign key relationships,
and it's compounded by the fact that often the parent table itself has a
primary key column called CODE.

Anybody have any suggestions on how to define the FK relationships to ERwin,
short of renamng columns?  Changing the names will craze the programmers who
need to refer to the model later.

Thanks.



