Re: Feature Request: Better handling of foreign keys in DELETE statements

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Marti Raudsepp <marti(at)juffo(dot)org>
Cc: Daniel Migowski <dmigowski(at)ikoffice(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Feature Request: Better handling of foreign keys in DELETE statements
Date: 2011-12-19 16:58:52
Message-ID: CAFj8pRD86G2cPkgpMVbGspN6hS2uU=ucCQqeWiZk-zbvcQe3zA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2011/12/19 Marti Raudsepp <marti(at)juffo(dot)org>:
> On Mon, Dec 19, 2011 at 18:14, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>> you can disable check per session if you need
>> ALTER TABLE ... DISABLE TRIGGER ALL;
>
> This is NOT a per-session command, this applies to all connections and
> queries, and may allow incorrect data into the table. Don't do this!
> (And it doesn't address the question anyway)
>

you have true,

sorry

Regards

Pavel

> Regards,
> Marti

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alan Hodgson 2011-12-19 17:30:50 Re: indexes and tables
Previous Message Adrian Klaver 2011-12-19 16:57:49 Re: Changing Passwords as Encrypted not Clear-Text