| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP fix proposal for bug #6123 |
| Date: | 2011-07-22 21:51:49 |
| Message-ID: | 4E29AAA5020000250003F727@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> I believe that we can get DELETE behavior which is every bit as
> sensible as INSERT behavior with a very small change.
> I think the right thing is to throw an error if the old row for a
> BEFORE UPDATE is updated by the same transaction and the trigger
> function ultimately returns a non-NULL value.
And to make this a bit less hand-wavy, a rough patch attached. I
expect the error message could use some word-smithing, and it could
use comments; but it seemed like something concrete might speed
things along.
-Kevin
| Attachment | Content-Type | Size |
|---|---|---|
| bug6123-v1.patch | text/plain | 2.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-07-22 21:54:42 | Re: storing TZ along timestamps |
| Previous Message | Robert Haas | 2011-07-22 21:28:24 | Re: cataloguing NOT NULL constraints |