> >> So is there no other way to do it but to verify the integrity using triggers >> and drop the referential constraints? > > Well, you could do something using a before delete trigger on the > referencing table that returns NULL to avoid the delete as well, but > making it only prevent the deletions caused by the referential constraints > might be difficult. >
That's right, It's easier to verify the existence of the master before inserting something in the details than controlling the way something gets deleted. After all, is only a PERFORM * FROM.... WHERE NEW..... IF NOT FOUND THEN RISE EXCEPTION 'that doesn't exists';... _________________________________________________________________ Plug&Play te trae en exclusiva los mejores conciertos de la red http://club.prodigymsn.com/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
