| From: | wieck(at)debis(dot)com (Jan Wieck) |
|---|---|
| To: | Jan Wieck <wieck(at)debis(dot)com> |
| Cc: | Hannu Krosing <hannu(at)tm(dot)ee>, Don Baccus <dhogaza(at)pacifier(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Re: ALTER TABLE DROP COLUMN |
| Date: | 2000-02-29 12:22:19 |
| Message-ID: | m12PlfQ-0003kkC@orion.SAPserv.Hamburg.dsh.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> fully SQL3. I just had an idea that might easily turn it to
> do the right thing.
ON <event> RESTRICT triggers are now executed after the
statement allways, ignoring any explicitly set deferred mode.
This is pretty close to Date's SQL3 interpretation, or IMHO
better. Date says that they are checked BEFORE each ROW, but
that would ignore the SET character of a statement. Now we
have correct semantics for all 4 possible referential
actions.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#========================================= wieck(at)debis(dot)com (Jan Wieck) #
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karel Zak - Zakkr | 2000-02-29 12:24:37 | Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE |
| Previous Message | Peter Eisentraut | 2000-02-29 11:14:06 | Re: [HACKERS] Re: [PATCHES] NO-CREATE-TABLE and NO-LOCK-TABLE |