Conterminous referential paths?

Conterminous referential paths?

Post by Maijala Teem » Tue, 06 Jul 1999 04:00:00

        In most textbooks dealing with relational model there's only
example relationships where referential paths constructs a tree and not a
mesh of relations. Is there some drawbacks in using structure where there
is many conterminous referential paths between tables? It is clear that if
there is cyclic relationships between tables there might be problems, but
how about acyclic relationships?

        Example, if we are having following relations (starting with
primary key):

        COMPANY(CompanyID, Name)
        EMPLOYEE(EmpID, CompanyID, Name)
        PROJECT(ProjectID, CompanyID, Name)
        PARTICIPATES(EmpID, ProjectID)

        Every employee works for company, company has many projects and
employees are participating in many projects within the company. So there
is two paths from company to employee. Could this kind of approach create
some problems with referential integrity or is this right way to do



1. direct-path inserts and referential integrity

The Oracle documentation says "During direct-path insert operations, ...
referential integrity constraints are ignored."  However, in order to do
a direct-path insert "The target table cannot have any ... referential
integrity constraints defined on it."  What could the first statement
possibly mean if you can't have referential integrity constraints
defined to begin with?


2. Advanced Transaction Models

3. Replmerg uses a unc path when an ftp path has been specified

4. Select * Server1.Table and Server2.Table?

5. Replmerg uses UNC path despite explicit use of ftp path

6. Unidata/SB+ Programmer(s) in MIAMI/FL Perm. pos

7. Paths and App.Path

8. SQL Query across two databases

9. app-path and mdb-path

10. Getting Long File Path from short Path / File Name

11. A local DDF path and a remote Data path does not work on SP3 (NT)

12. setting referential integrity in sql 7.0

13. Referential Integrity VS Cascade Deletes