>> You mean her data just disappears? Doesn't sound very reasonable to me. > > In reference cases, we can consider she looks the tables via something > like VIEWs implicitly. The "VIEW" can hide several tuple, but it does > not break any reference consistency in the raw level.
I don't understand what this means. Suppose we have two tables: CREATE TABLE parent (a integer, primary key (a)); CREATE TABLE child (a integer references parent, b integer); Consider these queries: 1. SELECT * FROM child 2. SELECT * FROM child JOIN parent ON child.a = parent.a In query (1), I wouldn't expect the foreign key on child to matter at all. In query (2), of course, the tuples in parent are no longer visible, so I expect things to get filtered. I'm not sure whether this is what you're proposing or not. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
