I'm doing some FK analysis of our tables by making a directed
graph representing FK dependencies and then traversing the
graph. In my code, I name everything using directed graph
terminology, but I'd like to have something a bit more
"user friendly" in the report.

In this scenario:
create table t1(a varchar2(20));
alter table t1 add constraint t1_fk foreign key(a) references t2(b);

t1.a must exist in t2.b. So,

t1 is the _______ of t2.
t2 is the _______ of t1.

Many TIA!
Mark

--
Mark Harrison
Pixar Animation Studios

On 3 nov, 04:50, m... (AT) pixar (DOT) com wrote:
You look as if you are mixing up logical design concepts with physical
design concepts.

In an E/R relationship you should use t2 "has" t1, t1 "belongs to" t2
or anything else that describes the relationship between entities.

The tables are commonly referred as "parent" and "child" when it comes
down to foreign keys.

HTH.

Cheers.

Carlos.

BTW: My child can't wait for "Cars 2", so hurry up! ;-)

On 3 nov, 04:50, m... (AT) pixar (DOT) com wrote:
You look as if you are mixing up logical design concepts with physical
design concepts.

In an E/R relationship you should use t2 "has" t1, t1 "belongs to" t2
or anything else that describes the relationship between entities.

The tables are commonly referred as "parent" and "child" when it comes
down to foreign keys.

HTH.

Cheers.

Carlos.

BTW: My child can't wait for "Cars 2", so hurry up! ;-)

On 3 nov, 04:50, m... (AT) pixar (DOT) com wrote:
You look as if you are mixing up logical design concepts with physical
design concepts.

In an E/R relationship you should use t2 "has" t1, t1 "belongs to" t2
or anything else that describes the relationship between entities.

The tables are commonly referred as "parent" and "child" when it comes
down to foreign keys.

HTH.

Cheers.

Carlos.

BTW: My child can't wait for "Cars 2", so hurry up! ;-)

On 3 nov, 04:50, m... (AT) pixar (DOT) com wrote:
You look as if you are mixing up logical design concepts with physical
design concepts.

In an E/R relationship you should use t2 "has" t1, t1 "belongs to" t2
or anything else that describes the relationship between entities.

The tables are commonly referred as "parent" and "child" when it comes
down to foreign keys.

HTH.

Cheers.

Carlos.

BTW: My child can't wait for "Cars 2", so hurry up! ;-)

mh (AT) pixar (DOT) com wrote:
Long, long ago, I used to use terms like
"each and every order contains one or more order lines"
"each order line is on an order"

This completely describes the (fully mandatory) relation
between orders and order lines.

"each person may drive a car"
"any car may be driven by a person"

This would describe the fully optional relations between persons
and cars (in contrast with what American teenagers think)

Generally: when t1 references t2, t1 is called the child of t2.
A possible error by Oracle is "no parent record found" when
inserting into t1
--

Regards,
Frank van Bortel

mh (AT) pixar (DOT) com wrote:
Long, long ago, I used to use terms like
"each and every order contains one or more order lines"
"each order line is on an order"

This completely describes the (fully mandatory) relation
between orders and order lines.

"each person may drive a car"
"any car may be driven by a person"

This would describe the fully optional relations between persons
and cars (in contrast with what American teenagers think)

Generally: when t1 references t2, t1 is called the child of t2.
A possible error by Oracle is "no parent record found" when
inserting into t1
--

Regards,
Frank van Bortel

mh (AT) pixar (DOT) com wrote:
Long, long ago, I used to use terms like
"each and every order contains one or more order lines"
"each order line is on an order"

This completely describes the (fully mandatory) relation
between orders and order lines.

"each person may drive a car"
"any car may be driven by a person"

This would describe the fully optional relations between persons
and cars (in contrast with what American teenagers think)

Generally: when t1 references t2, t1 is called the child of t2.
A possible error by Oracle is "no parent record found" when
inserting into t1
--

Regards,
Frank van Bortel

mh (AT) pixar (DOT) com wrote:
Long, long ago, I used to use terms like
"each and every order contains one or more order lines"
"each order line is on an order"

This completely describes the (fully mandatory) relation
between orders and order lines.

"each person may drive a car"
"any car may be driven by a person"

This would describe the fully optional relations between persons
and cars (in contrast with what American teenagers think)

Generally: when t1 references t2, t1 is called the child of t2.
A possible error by Oracle is "no parent record found" when
inserting into t1
--

Regards,
Frank van Bortel