Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) - Mailing list pgsql-hackers

From Harald Fuchs
Subject Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)
Date
Msg-id 87veryrske.fsf@srv.protecting.net
Whole thread Raw
In response to [OT] MySQL is bad, but THIS bad?  ("Mark Woodward" <pgsql@mohawksoft.com>)
List pgsql-hackers
In article <20060522150647.GE24404@svana.org>,
Martijn van Oosterhout <kleptog@svana.org> writes:

> On Mon, May 22, 2006 at 10:00:22AM -0500, Jim C. Nasby wrote:
>> > T-SQL has statement-level triggers, and they get used a lot (some big apps 
>> > ONLY put code in triggers). Statement-level triggers are very efficient for 
>> > maintaining aggregates; the closest PG has are rewrite rules.
>> 
>> Yeah, I wish PostgreSQL had them. I've got clients that could certainly
>> make use of them.

> What are you referring to that is not supported currently?

Probably he means that a complete implementation of statement-level
triggers should include a way to access the rows affected by the
trigger call.



pgsql-hackers by date:

Previous
From: "Dawid Kuroczko"
Date:
Subject: Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)