On 02/02/15 10:11 AM, Tom Lane wrote:
> If you did "select * from only primate" you would see that there is no
> such row in the parent table, which is what the foreign key is being
> enforced against.
Thanks. That does a lot to clarify it.
-Will
--
Sent via pgsql-general mailing list (pgsq
William Gordon Rutherdale writes:
> So this statement:
> INSERT INTO banana_stash(primate_id, qty) VALUES (1, 17);
> Resulted in this error:
> ERROR: insert or update on table "banana_stash" violates foreign key
> constraint "banana_stash_primate_id_fkey"
> DETAIL: Key (primate_id)=(1) is not pr
On 02/02/15 12:11 AM, David G Johnston wrote:
> William Gordon Rutherdale wrote
>> My problem: could someone please explain the semantics and why this
>> behaviour makes sense -- or is it a design error or bug?
> I didn't read your post in depth but I suspect you have not read and
> understood th
William Gordon Rutherdale wrote
> I have encountered a problem with references when using INHERITS (on
> Postgres 9.1/9.2). Could someone please explain why this occurs.
>
> My problem: could someone please explain the semantics and why this
> behaviour makes sense -- or is it a design error or
Hi.
I have encountered a problem with references when using INHERITS (on
Postgres 9.1/9.2). Could someone please explain why this occurs.
Consider this example.
CREATE TABLE primate
(
id SERIAL PRIMARY KEY,
name TEXT,
tale TEXT
);
CREATE TABLE chimp
(
human_friend TEXT
) INHERITS
