Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message

From: Artiom Makarov <artiom(dot)makarov(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message
Date: 2011-06-02 15:21:03
Message-ID: BANLkTin5M=Y-saC+REkBZEfpibhm-ghDOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2011/6/2 Alexey Klyukin <alexk(at)commandprompt(dot)com>:

> What would you expect to happen for TRUNCATE .. CASCADE?
>
> One thing I find potentially surprising is that TRUNCATE CASCADE doesn't follow the semantics of 'ON DELETE' clause for the foreign key, i.e. it would truncate the dependent table even with ON DELETE RESTRICT foreign key. Do we need a similar 'ON TRUNCATE'  FK clause?
>

Yes, cascade truncating taked place without ON DELETE RESTRICT
checking. No matter.
Either TRUNCATE must show message with full objects tree - correct
behavior like DROP, or TRUNCATE CASCADE should not delete anything
(strict constraint checking).

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Marc Cousin 2011-06-02 15:28:49 Re: collation problem on 9.1-beta1
Previous Message Alexey Klyukin 2011-06-02 15:04:29 Re: BUG #6048: TRUNCATE vs TRUNCATE CASCADE: misleading message