From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Jan Wieck <wieck@debis.com>
Cc: PostgreSQL Development <pgsql-hackers@postgresql.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: Foreign keys breaks tables permissions
Date: Sun, 21 May 2000 13:12:34 -0400
Message-ID: <9733.958929154@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.21.0005201947120.423-100000@localhost.localdomain>
References: <Pine.LNX.4.21.0005201947120.423-100000@localhost.localdomain>
Peter Eisentraut <peter_e@gmx.net> writes:
> Tom Lane writes:
>> This is perhaps the least undesirable of the choices we have, but it's
>> still a security hole.
> The reason this concerns me is that requiring update rights on the
> referenced table eliminates much the benefit of foreign keys from an
> administration point of view: If the primary keys can be updated freely,
> they no longer constrain the data in the referencing table effectively.
> I suppose we'll have to live with that for now but I'd suggest that it be
> put on the TODO list somewhere.
What we need to do about it is implement the separate REFERENCES right
as specified by SQL92, and then fix FK support to require that right
rather than UPDATE...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, wieck@debis.com, pgsql-hackers@postgresql.org
Subject: Re: Foreign keys breaks tables permissions
In-Reply-To: <9733.958929154@sss.pgh.pa.us>
References: <Pine.LNX.4.21.0005201947120.423-100000@localhost.localdomain> <9733.958929154@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox