| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SQL Standard Feature T211 |
| Date: | 2017-03-10 19:11:53 |
| Message-ID: | 225a37c3-5dc1-6717-bf74-f51d75b0b285@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/9/17 18:39, Kevin Grittner wrote:
> With the addition of transition tables we have all four, although
> I'm not sure whether the CREATE TRIGGER statement conforms closely
> enough to claim the feature. The two basic issues I can think of
> are:
> - we don't allow the OLD and NEW transition variable names to be
> specified -- using hard-coded values instead
> - we don't support the standard <triggered SQL statement> formats,
> instead supporting only our EXECUTE PROCEDURE syntax
>
> Do we leave T211, "Basic trigger capability" on our "unsupported"
> list until those two points are addressed?
Those seem pretty big ones.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-03-10 19:17:43 | Re: Adding support for Default partition in partitioning |
| Previous Message | Peter Eisentraut | 2017-03-10 19:09:39 | Re: Need a builtin way to run all tests faster manner |