Re: [pgsql-advocacy] Assembling "top features" list for beta announcement - Mailing list pgsql-advocacy

From Kevin Grittner
Subject Re: [pgsql-advocacy] Assembling "top features" list for beta announcement
Date
Msg-id CACjxUsNSLLMQpCL3AcmZj8AfFd7fb=uw+Oajb+BAkfzg6OUKig@mail.gmail.com
Whole thread Raw
In response to Re: [pgsql-advocacy] Assembling "top features" list for beta announcement  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-advocacy
On Fri, Apr 7, 2017 at 5:35 PM, Thomas Kellerer <spam_eater@gmx.net> wrote:
> Kevin Grittner schrieb am 08.04.2017 um 00:01:
>>
>> I don't think it merits top 2-4 features, but transition tables for
>> AFTER triggers is a SQL standard feature that I think most products
>> have had and we have not ... until v10.
>
> I think only SQL Server and DB2 have that.

SAP SQL Anywhere also supports it and Sybase ASE supports the
capability, but with fixed names for the transition tables (inserted
and deleted).

> Oracle has no such thing for their statement level trigger (it can be
> implemented using a compound trigger and a temporary table)
>
> MySQL has no statement level triggers

SAP MaxDB and SQLite are in the same camp as MySQL in this regard --
no support for it.

--
Kevin Grittner


pgsql-advocacy by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [pgsql-advocacy] Assembling "top features" list for betaannouncement
Next
From: Eric Ridge
Date:
Subject: [pgsql-advocacy] Is the Postgres Association part of smile.amazon.com?