On Tue, 2 Apr 2002, Petru Paler wrote:
> 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.