From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | SQL Standard Feature T211 |
Date: | 2017-03-09 23:39:32 |
Message-ID: | CACjxUsM+RZRo-TcD8Hu6eqO_uyY6vr6FNh6Zmc3CJW-pcXDqcg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[separate thread from transition table patch, since a different
audience might be interested]
Four things are required to claim support for Feature T211, "Basic
trigger capability":
- support for the CREATE TRIGGER statement
- the ability to declare and reference transition tables for AFTER
triggers
- support for the DROP TRIGGER statement
- support for TRIGGER in the GRANT and REVOKE statements
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? Does anyone know of
anything else that would need to be done?
--
Kevin Grittner
From | Date | Subject | |
---|---|---|---|
Next Message | Tels | 2017-03-09 23:40:39 | Re: Declarative partitioning optimization for large amount of partitions |
Previous Message | Robert Haas | 2017-03-09 23:20:49 | Re: [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line |