Inheritance referential integrity problem 
Author Message
 Inheritance referential integrity problem

Quote:

> I'm using Postgresql's very nice inheritance support in a project, but I
> just stumbled upon a problem that I'm not sure how to fix (or whether it's
> my problem or postgresql's).

> ERROR:  <unnamed> referential integrity violation - key referenced from c
> not found in a

> Could someone enlighten me on what I'm missing? Why is the constraint not
> satisfied, since the key is clearly present in a? If that row is
> considered to belong to b, then why does it show up in a?

The references constraints currently reference only the particularly
named table and not any children.  Selects by default show rows in the
children tables (you can use ONLY to not get this behavior:
"select * from ONLY a;") It's one of the limitations of the current
implementation.

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://www.***.com/



Sun, 19 Sep 2004 04:39:21 GMT
 
 [ 1 post ] 

 Relevant Pages 

1. referential integrity with inheritance

2. Inheritance & Referential Integrity

3. Referential Integrity Problem in SQL 7

4. referential integrity problem

5. Cascading Referential Integrity Problems (Updates)

6. URGENT: referential integrity problem

7. Problem: Referential Integrity Constraints lost: Correction

8. Referential Integrity Problems

9. Problem with referential integrity within functions

10. Referential integrity error trapping problem with OLEDB and ADO

11. Problem with referential integrity and inherited tables

12. Referential Integrity problem - SQL 7


 
Powered by phpBB® Forum Software