On Sun, Dec 4, 2011 at 7:41 PM, Phoenix Kiula phoenix.ki...@gmail.com wrote:
On Sun, Dec 4, 2011 at 7:14 PM, Alban Hertroys haram...@gmail.com wrote:
On 4 Dec 2011, at 11:19, Phoenix Kiula wrote:
INSERTs in the parent table don't need to check for any reference from the
child table,
-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Phoenix Kiula
Sent: Tuesday, December 06, 2011 11:46 AM
To: Alban Hertroys
Cc: PG-General Mailing List
Subject: Re: [GENERAL] Foreign keys question (performance)
On Sun
On 12/06/2011 08:45 AM, Phoenix Kiula wrote:
On Sun, Dec 4, 2011 at 7:41 PM, Phoenix Kiulaphoenix.ki...@gmail.com wrote:
On Sun, Dec 4, 2011 at 7:14 PM, Alban Hertroysharam...@gmail.com wrote:
On 4 Dec 2011, at 11:19, Phoenix Kiula wrote:
I have a problem.
Here's my table designs. The
Hi.
I have a foreign key as such:
ALTER TABLE child_table
ADD CONSTRAINT fk_child
FOREIGN KEY (stringid) REFERENCES parent_table (stringid) MATCH FULL
ON DELETE CASCADE ;
Questions:
1. Is MATCH FULL adding any value here? If the foreign key is just
on an id column, what purpose does it
On 4 Dec 2011, at 11:19, Phoenix Kiula wrote:
Hi.
I have a foreign key as such:
ALTER TABLE child_table
ADD CONSTRAINT fk_child
FOREIGN KEY (stringid) REFERENCES parent_table (stringid) MATCH FULL
ON DELETE CASCADE ;
Questions:
1. Is MATCH FULL adding any value here? If the
On Sun, Dec 4, 2011 at 7:14 PM, Alban Hertroys haram...@gmail.com wrote:
On 4 Dec 2011, at 11:19, Phoenix Kiula wrote:
INSERTs in the parent table don't need to check for any reference from the
child table, since they're new; there can't be a reference. UPDATEs and
DELETEs do though,
