Erwin reverse engineering question
Date: Sun, 11 Nov 2001 15:33:14 GMT
Message-ID: <_SwH7.32518$S4.2916053_at_newsread1.prod.itd.earthlink.net>
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. Received on Sun Nov 11 2001 - 16:33:14 CET