Foreign keys have the same columns as primary key

After upgrading from AppModeler 6.0 to 6.1 when I check my PDM I'm getting
the following warning messages on a lot of columns: Foreign Keys have the
same columns as primary key.  The suggested correction doesn't help much.
Can some one explain this warning to me?  It seems that when the primary key
of one table is a foreign key from another table this warning is poping up.
Any help appreciated.

Thanks,

--
James L. Knowlton
President and Programer/Analyst
Law Enforcement Automated Data Systems, Inc
Richmond, VA


begin 666 James L. Knowlton.vcf
M0D5'24XZ5D-!4D0-"E9%4E-)3TXZ,BXQ#0I..DMN;W=L=&]N.TIA;65S.TPN
M.SL-"D9..DIA;65S($PN($MN;W=L=&]N#0I/4D<Z3&%W($5N9F]R8V5M96YT
M($%U=&]M871E9"!$871A(%-Y<W1E;7,L($EN8RX-"E1)5$Q%.E!R97-I9&5N
M= T*5$5,.U=/4DL[5D])0T4Z*#@P-"D@.#8Q+3 R,C4-"E1%3#M73U)+.U9/
M24-%.B@X,#0I(#<S-"TR.3@U#0I414P[5T]22SM&05@Z*#@P-"D@-S,T+3(Y
M-S0-"E1%3#M(3TU%.T9!6#HH.# T*2 W.38M-SDT,@T*0412.U=/4DL[14Y#
M3T1)3D<]455/5$5$+5!224Y404),13H[.U N3RX@0F]X(#,W-C4@/3!$/3!!
M4V]U=&@@0W)A=&5R(%)O860[4&5T97)S8G5R9SM603LR,S@P-3M5;FET960@
M4W1A=&5S(&]F/0T*($%M97)I8V$-"DQ!0D5,.U=/4DL[14Y#3T1)3D<]455/
M5$5$+5!224Y404),13I0+D\N($)O>" S-S8U(#TP1#TP05-O=71H($-R871E
M<B!2;V%D/3!$/3!!4&5T97)S8G5R9RP@5D$@,C,X,#4],$0],$%5;FET960@
M/0T*4W1A=&5S(&]F($%M97)I8V$-"D%$4CM(3TU%.CL[.U)I8VAM;VYD.U9!
M.S(S,C,W.U5N:71E9"!3=&%T97,@;V8@06UE<FEC80T*3$%"14P[2$]-13M%
M3D-/1$E.1SU154]4140M4%))3E1!0DQ%.E)I8VAM;VYD+"!602 R,S(S-STP
M1#TP055N:71E9"!3=&%T97,@;V8@06UE<FEC80T*14U!24P[4%)%1CM)3E1%
M4DY%5#IK;F]W;'1O;FI ;&5A9',M:6YC+F-O;0T*4D56.C$Y.3@P.3(P5# S
2-3@S.5H-"D5.1#I60T%21 T*
`
end

0
James
9/20/1998 3:58:39 AM
sybase.powerdesigner.general 9408 articles. 1 followers. Follow

1 Replies
701 Views

Similar Articles

[PageSpeed] 34
Get it on Google Play
Get it on Apple App Store

Actually, there is a bug.  Apparently the developers introduced a minor bug
in the "Check model" function.  The warning is not correct, so should be
ignored.  It isn't a problem for database generation or anything else.  Just
ignore it for now.  Heck, you will even get this warning if the PK and FK
aren't the same.  Also remember that one-to-one relationships are valid for
optional information about something, rather than have the columns exist for
every item, make a new table that is optional one-to-one.  The PK on this
new table will match the PK on the other table, so the automatically
generated FK will match the PK.  This *should* prompt the warning message,
to advise you of the apparent duplication.

HTH,

--
Michael F. Nicewarner [TeamPS]
mailto:mike.nicewarner@ibpinc.com
http://www.datamodel.org

James L. Knowlton wrote in message ...
>After upgrading from AppModeler 6.0 to 6.1 when I check my PDM I'm getting
>the following warning messages on a lot of columns: Foreign Keys have the
>same columns as primary key.  The suggested correction doesn't help much.
>Can some one explain this warning to me?  It seems that when the primary
key
>of one table is a foreign key from another table this warning is poping up.
>Any help appreciated.
>
>Thanks,
>
>--
>James L. Knowlton
>President and Programer/Analyst
>Law Enforcement Automated Data Systems, Inc
>Richmond, VA
>
>
>


0
Michael
9/21/1998 2:38:02 PM
Reply: