From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nils Gösche <cartan(at)cartan(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Feature Proposal: Constant Values in Columns or Foreign Keys |
Date: | 2012-04-17 23:01:55 |
Message-ID: | 18148.1334703715@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?UTF-8?Q?Nils_G=C3=B6sche?= <cartan(at)cartan(dot)de> writes:
> Bartosz Dmytrak wrote:
>> how about inheritance in postgres?
> I know about Postgres' inheritance feature, but would prefer a more standard relational solution.
[ blink... ] That seems like a pretty silly argument for proposing
something that is *more* nonstandard.
> I was quite surprised to find that this wasn't possible. Is there any good reason why not?
It's contrary to SQL standard is why not. And it's not just a matter of
being outside the spec, as inheritance is; this is messing with the
details of something that is defined in the standard. As an example,
I would wonder how such an FK is supposed to be represented in the
spec-defined information schema views. Other interesting questions
include what would happen to the supposed constant during actions such
as ON DELETE SET NULL or ON UPDATE CASCADE, which normally would result
in a change in the referencing row.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-04-17 23:11:46 | Re: LOCK TABLE is not allowed in a non-volatile function |
Previous Message | Nils Gösche | 2012-04-17 22:06:11 | Re: Feature Proposal: Constant Values in Columns or Foreign Keys |