| From: | JanWieck(at)t-online(dot)de (Jan Wieck) |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'Tatsuo Ishii'" <t-ishii(at)sra(dot)co(dot)jp>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: Proposal: TRUNCATE TABLE table RESTRICT |
| Date: | 2000-06-09 11:04:27 |
| Message-ID: | 200006091104.NAA04376@hot.jw.home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas SB wrote:
>
> Truncate should probably check if all referencing tables are empty
> and fail if not. Truncate should imho not lead to a violated constraint
> situation.
> Strictly speaking the current situation is more or less a bug.
>
Not anything is possible with RI, so the DB schema might use
regular triggers and/or rules as well.
Why not reject TRUNCATE at all if the relation has
rules/triggers? IMHO the only safe way.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-06-09 11:21:48 | Re: freefuncs.c is never called from anywhere!?] |
| Previous Message | Jan Wieck | 2000-06-09 10:39:51 | Re: Implementing STDDEV and VARIANCE |