Re: Assembling "top features" list for beta announcement

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Thomas Kellerer <spam_eater(at)gmx(dot)net>
Cc: PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Assembling "top features" list for beta announcement
Date: 2017-04-08 01:41:00
Message-ID: CACjxUsNSLLMQpCL3AcmZj8AfFd7fb=uw+Oajb+BAkfzg6OUKig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy

On Fri, Apr 7, 2017 at 5:35 PM, Thomas Kellerer <spam_eater(at)gmx(dot)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

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Eric Ridge 2017-04-08 06:45:28 Is the Postgres Association part of smile.amazon.com?
Previous Message Peter Eisentraut 2017-04-08 01:04:47 Re: Assembling "top features" list for beta announcement