| From: | "Neil Conway" <neilc(at)samurai(dot)com> |
|---|---|
| To: | "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: FOR EACH STATEMENT triggers |
| Date: | 2003-04-30 06:56:47 |
| Message-ID: | 1899.24.114.1.243.1051685807.squirrel@mailbox.samurai.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andreas Pflug said:
> It appears that statement triggers are implemented this way right now in
> CVS tip. Unfortunately, this means that there's no way to figure out the
> record set that is covered by the triggering action, which I consider
> being fundamental for a usable implementation.
I agree that this would be useful -- I didn't get around to implementing
it when I did the rest of the statement-trigger work.
> Is there any more work on statement triggers planned or going on right
> now?
I don't have any work on them planned. If you or anyone else would like to
take a shot at implementing this functionality, go right ahead. Otherwise,
I might get a chance to do some work on this in August or September.
Cheers,
Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2003-04-30 08:11:15 | Re: [HACKERS] pg_namespace -> pg_schema? |
| Previous Message | Tom Lane | 2003-04-30 03:47:42 | Re: current breakage with PGCLIENTENCODING |