| From: | Mischa Sandberg <mischa(at)ca(dot)sophos(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Porting MSSQL to PGSQL -- triggers |
| Date: | 2006-05-23 23:39:56 |
| Message-ID: | 44739D4C.2020800@ca.sophos.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> How expensive is this going to be, especially for huge numbers of rows?
>
> Certainly cheaper than firing a per-row trigger.
I'm curious: I've never written a MSSQL trigger that did NOT use the
INSERTED/DELETED pseudotables (aka NEW/OLD). I know STATEMENT-level triggers
have existed in PG for a while ... but what do people use them for???
--
Engineers think that equations approximate reality.
Physicists think that reality approximates the equations.
Mathematicians never make the connection.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sibel karaasma | 2006-05-24 08:39:59 | compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!! |
| Previous Message | Thomas Hallgren | 2006-05-23 07:23:53 | Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2006-05-23 23:58:43 | Re: Why is CVS server so slow? |
| Previous Message | Michael Glaesemann | 2006-05-23 23:37:53 | Re: SQL compliant interval implementation |