More on inheritance and foreign keys

From: Albert Cervera Areny <albertca(at)hotpop(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: More on inheritance and foreign keys
Date: 2006-06-08 06:38:10
Message-ID: 200606072342.31045.albertca@hotpop.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
after starting this thread
http://archives.postgresql.org/pgsql-hackers/2006-05/msg00222.php, I thought
I'd finally go for making foreign keys my own way instead of trying to patch
PostgreSQL. However, I've realized that managing foreign keys with my own
PL/SQL or C function isn't possible as I need DEFERRED checks which are
currently only available for foreign keys.

The solution to the foreign key problem seems easy if I modify PostgreSQL
implementation and take off the ONLY word from the SELECT query, but it's not
an option for me, as I'm developing a library, not an application. I'd like
many people could use it.

Would it be acceptable if one could add the INHERIT word when creating
foreign keys, in order to change the SELECT behaviour? Are there other
solutions to this problem?

Thanks.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Glaesemann 2006-06-08 07:59:46 Re: More on inheritance and foreign keys
Previous Message Koichi Suzuki 2006-06-08 05:31:53 Re: How to avoid transaction ID wrap